On-Premise w/ Docker, version 20.7.0.dev0 c13b2f6
Opening any issue detail in UI displays the "There was an error loading a component." error, and event is pushed into the internal project. Can't display the internal event in the UI, but the notification mail contains following information:
TypeError: t.generationByIdentifier is not a function. (In 't.generationByIdentifier(n)', 't.generationByIdentifier' is undefined)
at deviceNameMapper (./app/components/deviceName.tsx:12:35)
at None (./app/components/group/tagDistributionMeter.jsx:72:19)
at map ([native code])
at context (./app/components/group/tagDistributionMeter.jsx:70:21)
at iu ([native code])
...
(13 additional frame(s) were not displayed)

I just ran across this in the hosted version. Help?
I've tested in both Chrome and Safari.
I'm seeing this in the chrome devtools…
Access to XMLHttpRequest at 'https://reload.getsentry.net/event/' from origin 'https://sentry.io' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
have the same issue too

Sentry 20.10.178833d9 /Docker
Can you share logs from your sentry web instance?
Can you share logs from your sentry web instance?
@kooroshh looks like your sentry web instance gets killed pretty frequently by SIGILL. Which version of Docker are you using?
@kooroshh looks like your sentry web instance gets killed pretty frequently by
SIGILL. Which version of Docker are you using?
@BYK Docker version 19.03.13, build 4484c46d9d On (Ubuntu 20.04.1 LTS)
@kooroshh do you have any custom Docker config? Also can you share your CPU?
Docker version 19.03.12, build 48a66213fe
@kooroshh do you have any custom Docker config? Also can you share your CPU?
@BYK
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 79
model name : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
stepping : 1
microcode : 0xb000036
cpu MHz : 2099.998
cache size : 20480 KB
physical id : 0
siblings : 1
core id : 0
cpu cores : 1
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 20
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon nopl xtopology tsc_reliable nonstop_tsc cpuid pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch cpuid_fault invpcid_single pti ssbd ibrs ibpb stibp fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 invpcid rtm rdseed adx smap xsaveopt arat md_clear flush_l1d arch_capabilities
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs taa itlb_multihit
bogomips : 4199.99
clflush size : 64
cache_alignment : 64
address sizes : 43 bits physical, 48 bits virtual
power management:
it's all default configuration just installed the On-Premise using the default installer
here is a screenshot of sentry-internal

@kooroshh do you have any custom Docker config? Also can you share your CPU?
@BYK
vendor_id : GenuineIntel cpu family : 6 model : 79 model name : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz stepping : 1 microcode : 0xb000036 cpu MHz : 2099.998 cache size : 20480 KB physical id : 0 siblings : 1 core id : 0 cpu cores : 1 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 20 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon nopl xtopology tsc_reliable nonstop_tsc cpuid pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch cpuid_fault invpcid_single pti ssbd ibrs ibpb stibp fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 invpcid rtm rdseed adx smap xsaveopt arat md_clear flush_l1d arch_capabilities bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs taa itlb_multihit bogomips : 4199.99 clflush size : 64 cache_alignment : 64 address sizes : 43 bits physical, 48 bits virtual power management:it's all default configuration just installed the On-Premise using the default installer
here is a screenshot of sentry-internal
UPDATE
ok i think I've found the problem , the problem is the nginx reverse proxy which doesn't allow to load/exec some scripts (Probably Content Security Policy)
using the internal port , everything works fine
@kooroshh alright then, closing out. That said I'd still investigate those SIGILLs (signal 4 termination).