Nextcloud not fully loading in Edge, Chrome works - related somehow to default.conf

[Intenos]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I upgraded Nextcloud from 27.X to 28.0.1.1 with the latest Docker release build and replaced the default.conf by the newly provided default.conf.sample.

Whereas in Chrom Nextcloud works properly, it doesn´t fully load in Edge. It starts that on the login page that it shows "Anmelden bei {productName}" instead of "Anmelden bei Nextcloud". After loging in and showing the Dashboard, it is neither able to load the files, nor the mails or weather. When switching to the Files App, it doesn´t show any files. In the development sidebar of Edge, a lot "..404 (Not Found)" errors are shown.

Expected Behavior

It should work in Edge as in Chrome

Steps To Reproduce

After playing around a bit and trying out different things, I found that it works again when removing the following (new) part of the default.conf below "location ~ .(?:css|js|mjs|svg|gif|png|jpg|ico|wasm|tflite|map|ogg|flac)$ {":

location ~ \.js$ {
         default_type text/javascript;
     }

     location ~ \.mjs$ {
         default_type text/javascript;
     }

Whether the above is just a (not proper workaround) for resolving the actual problem or really the solutions, I don´t know.

Environment

- OS: OpenMediaVault 6.9.11-2 (Shaitan) on Linux 5.10.0-26-amd64
- How docker service was installed: Portainer

CPU architecture

x86-64

Docker creation

![image](https://github.com/linuxserver/docker-nextcloud/assets/44039580/e9bf3398-dfa0-4b98-a421-85a81e9bb3cf)

Container logs

[mod-init] Attempting to run Docker Modification Logic
[mod-init] Adding linuxserver/mods:universal-package-install to container
[mod-init] linuxserver/mods:universal-package-install at sha256:179666823e425c84f903183aa0b76eb4fe6ce386fdeb55ca85b56b7791669140 has been previously applied skipping
[migrations] started
[migrations] 01-nginx-site-confs-default: skipped
[migrations] 02-default-location: skipped
[migrations] done
usermod: no changes
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗ 
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝ 

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    911
User GID:    911
───────────────────────────────────────

using keys found in /config/keys
**** The following site-confs have extensions other than .conf ****
**** This may be due to user customization. ****
**** You should review the files and rename them to use the .conf extension or remove them. ****
**** nginx.conf will only include site-confs with the .conf extension. ****
/config/nginx/site-confs/default.conf.20230623
/config/nginx/site-confs/default.conf.20231216
/config/nginx/site-confs/default.conf.20230616
**** Adding nodejs to OS package install list ****
**** Adding npm to OS package install list ****
[mod-init] **** Installing all mod packages ****
fetch http://dl-cdn.alpinelinux.org/alpine/v3.18/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.18/community/x86_64/APKINDEX.tar.gz
OK: 361 MiB in 261 packages
[custom-init] No custom files found, skipping...
[ls.io-init] done.

[OvernightPancake]

I am facing a similar issue on Firefox, albeit I am having far less of the page load than you seem to. Removing those lines seems to only resolve the issue for me if I also spoof my user agent to Chrome.

[cravas]

#388 (comment)

I saw that issue a while ago.
Had to revert those changes and just live with the warn on the log.

[atlanticfirst]

same issue，had to revert those changes to get nextcloud properly work

[drizuid]

we have a PR being confirmed now to resolve this. applies to #403 also

[Intenos]

@drizuid
Thank you very much for your work. But unfortunately it didn´t solve the issue. I still have to out-comment the mentioned parts.