Chromium-based browsers hang on "Load Drive (0%)"

BlameBurr

Mentioned it briefly in the Matrix channel earlier but was wondering if anyone has any solutions or whether this is just a bug. When I spun the server up it was originally on one domain and I had this issue, tried splitting it across domains instead.

The server is on an internal network so uses self-signed certificates with the unsafeUrl as the top level internal domain and the safe URL as a subdomain of the domain and uses the basic nginx config from GitHub. The platform's accessible via Firefox but not Chromium based browsers.

When loading the page, it hangs at "Load Drive (0%)" and upon checking the browser developer console every network request succeeds, there's no backend errors and the only error in browser console is:
drive/#:1 Failed to fetch a worker script.

Browsers tried include:
Chromium version: Version 137.0.7151.68 (Official Build) snap (64-bit) (hangs)
Microsoft Edge version: Version 137.0.3296.83 (Official build) (64-bit) (hangs)
Firefox (works)
I've tried the browsers in incognito/private mode and there are no extensions loaded/running.

Thanks in advance

Mathilde

Hello,

BlameBurr The server is on an internal network so uses self-signed certificates with the unsafeUrl as the top level internal domain and the safe URL as a subdomain of the domain and uses the basic nginx config from GitHub. The platform's accessible via Firefox but not Chromium based browsers.

I believe this cannot work on Chromium. You need to have a single TLS certificate for both domains. Otherwise it won't load the application.

Even if you are trying to access your instance outside the internet (air gapped?) you should be able to generate "real" TLS certificates with Let's Encrypt nowadays. With the ability to have one valid for two different domains.

BlameBurr

Mathilde
I've done some more digging and it's definitely due to certificates, we're going to change how we manage our certificates anyway so hopefully that'll improve it but I managed to get it to run correctly by launching chromium with the "--ignore-certificate-errors" flag so it's definitely a certificate based issue.

Hopefully once the certificates are under the new management solution it'll work as there's no reason that one certificate for both domains should't work, especially as I'm using subdomains rather than different domains

Appreciate the support 🙂