JS error causing stuck on loading screen after login about self-hosted HOT 5 CLOSED

upstream sentry {
        server SERVER_IP:9000; # Redirect traffic to Sentry server
    }

server {
        modsecurity on;
        modsecurity_rules_file /etc/nginx/modsec/sentry.conf;
        root /var/www/html;
        server_name sentry.example.com;
        client_max_body_size 200M;
        location / {
                proxy_pass https://sentry; # Forward Traffic to upstream servers
                proxy_ssl_certificate /etc/nginx/certs/server.crt; # Location to specify crt file
                proxy_ssl_certificate_key /etc/nginx/certs/server.key; # Location to specify key file
                proxy_ssl_trusted_certificate /etc/nginx/certs/ca.crt; # Location of CA for authentication
                proxy_set_header Host $http_host; # Host header is not changed
                proxy_set_header Upgrade $http_upgrade; # Host header Upgrade
                proxy_set_header X-Forwarded-Proto https; # Request scheme HTTPS
                proxy_set_header X-Forwarded-Ssl on; # Request SSL
                proxy_buffering off; # Turn off Buffering
        }


    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/sentry.example.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/sentry.example.com/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
    access_log /var/log/nginx/sentry-access.log;
    error_log /var/log/nginx/sentry-error.log;
}



server {
    if ($host = sentry.example.com) {
        return 301 https://$host$request_uri;
    } # managed by Certbot


        server_name sentry.example.com ;

    listen 80;
    return 404; # managed by Certbot


}