Vault working but stuck on loading screen

Hi, everyone,

I have setup a self-hosted instance of Bitwarden on my Synology NAS via Docker. I am reaching bitwarden through reverse-proxy via a LetsEncrypt container. Everything works fine, the Firefox extension correctly shows my vault data, the Android app works perfectly fine. But if I go on vault.mydomain.com it just keeps loading and loading (I believe it’s trying to load the login screen).

These are the settings for my nginx reverse proxy:

    listen 443 ssl;
    listen [::]:443 ssl;

    server_name vault.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 128M;

    # enable for ldap auth, fill in ldap details in ldap.conf
    #include /config/nginx/ldap.conf;

    location / {
        # enable the next two lines for http auth
        #auth_basic "Restricted";
        #auth_basic_user_file /config/nginx/.htpasswd;

        # enable the next two lines for ldap auth
        #auth_request /auth;
        #error_page 401 =200 /login;

        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_bitwarden bitwarden;
        proxy_pass http://192.168.1.200:8080;
    }

    location /notifications/hub {
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_bitwarden bitwarden;
        proxy_pass http://192.168.1.200:8080;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "Upgrade";
    }

    location /notifications/hub/negotiate {
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_bitwarden bitwarden;
        proxy_pass http://192.168.1.200:8080;
    }

}

The container is set to reverse proxy 8080:80.

The Firefox debug console shows

Loading failed for the <script> with source "https://vault.mydomain.com/app/vendor.eff9c393dd1fb9ae5504.js" vault.mydomain.com:29:1
Loading failed for the <script> with source "https://vault.mydomain.com/app/main.eff9c393dd1fb9ae5504.js".

I hope anyone can help! Thanks

Well, it seems like restarting letsencrypt fixed my problem after all. DId not change anything in the nginx conf :S