# Nextcloud theme broken after upgrade v9.1.1
**URL:** https://dietpi.com/forum/t/nextcloud-theme-broken-after-upgrade-v9-1-1/19372
**Category:** Troubleshooting
**Created:** [20 February 2024 20:08 UTC](https://dietpi.com/forum/t/nextcloud-theme-broken-after-upgrade-v9-1-1/19372 "2024-02-20T20:08:53Z")
**Posts on this page:** 15
**Page:** 1
### Author:  [@howardroark](https://dietpi.com/forum/u/howardroark)
#### Post date: [20 February 2024 20:08 UTC](https://dietpi.com/forum/t/nextcloud-theme-broken-after-upgrade-v9-1-1/19372/1 "2024-02-20T20:08:53Z")
After the update to DietPi v9.1.1, the Nextcloud theme completely disappeared. What can I do about this?
### Creating a bug report/issue
#### Required Information
- DietPi version
G\_DIETPI\_VERSION\_CORE=9
G\_DIETPI\_VERSION\_SUB=1
G\_DIETPI\_VERSION\_RC=1
G\_GITBRANCH=‘master’
G\_GITOWNER=‘MichaIng’
- Distro version
bookworm 0
- Kernel version
Linux DietPi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
- Architecture
arm64
- SBC model
RPi 4 Model B (aarch64)
- Power supply used | (EG: 5V 1A RAVpower)
Raspi Pi 4 power supply.
#### Additional Information (if applicable)
- Software title
Nextcloud
---
### Author:  [@Joulinar](https://dietpi.com/forum/u/Joulinar)
#### Post date: [20 February 2024 20:23 UTC](https://dietpi.com/forum/t/nextcloud-theme-broken-after-upgrade-v9-1-1/19372/2 "2024-02-20T20:23:43Z")
did you tried to reboot your system?
---
### Author:  [@howardroark](https://dietpi.com/forum/u/howardroark)
#### Post date: [20 February 2024 21:41 UTC](https://dietpi.com/forum/t/nextcloud-theme-broken-after-upgrade-v9-1-1/19372/3 "2024-02-20T21:41:23Z")
Yes.
---
### Author:  [@Joulinar](https://dietpi.com/forum/u/Joulinar)
#### Post date: [20 February 2024 21:46 UTC](https://dietpi.com/forum/t/nextcloud-theme-broken-after-upgrade-v9-1-1/19372/4 "2024-02-20T21:46:47Z")
all services are running?
```auto
dietpi-services status
```
---
### Author:  [@howardroark](https://dietpi.com/forum/u/howardroark)
#### Post date: [20 February 2024 22:04 UTC](https://dietpi.com/forum/t/nextcloud-theme-broken-after-upgrade-v9-1-1/19372/5 "2024-02-20T22:04:16Z")
> [@Joulinar](#):
>
> `dietpi-services status`
Yes.
```auto
[OK] DietPi-Services | avahi-daemon active (running) since Tue 2024-02-20 21:46:39 GMT; 17min ago
[OK] DietPi-Services | proftpd active (running) since Tue 2024-02-20 21:46:47 GMT; 17min ago
[OK] DietPi-Services | nmbd active (running) since Tue 2024-02-20 21:46:47 GMT; 17min ago
[OK] DietPi-Services | smbd active (running) since Tue 2024-02-20 21:46:48 GMT; 17min ago
[OK] DietPi-Services | redis-server active (running) since Tue 2024-02-20 21:46:47 GMT; 17min ago
[OK] DietPi-Services | mariadb active (running) since Tue 2024-02-20 21:46:48 GMT; 17min ago
[OK] DietPi-Services | php8.2-fpm active (running) since Tue 2024-02-20 21:46:50 GMT; 17min ago
[OK] DietPi-Services | nginx active (running) since Tue 2024-02-20 22:03:38 GMT; 19s ago
[OK] DietPi-Services | docker active (running) since Tue 2024-02-20 21:46:47 GMT; 17min ago
[OK] DietPi-Services | cron active (running) since Tue 2024-02-20 21:46:48 GMT; 17min ago
[OK] DietPi-Services | dropbear active (running) since Tue 2024-02-20 21:46:46 GMT; 17min ago
[INFO] DietPi-Services | dietpi-vpn inactive (dead)
[INFO] DietPi-Services | dietpi-cloudshell inactive (dead)
[OK] DietPi-Services | dietpi-dashboard active (running) since Tue 2024-02-20 21:46:46 GMT; 17min ago
[OK] DietPi-Services | dietpi-ramlog active (exited) since Tue 2024-02-20 21:46:39 GMT; 17min ago
[OK] DietPi-Services | dietpi-preboot active (exited) since Tue 2024-02-20 21:46:39 GMT; 17min ago
[OK] DietPi-Services | dietpi-postboot active (exited) since Tue 2024-02-20 21:46:46 GMT; 17min ago
[INFO] DietPi-Services | dietpi-wifi-monitor inactive (dead)
```
---
### Author:  [@howardroark](https://dietpi.com/forum/u/howardroark)
#### Post date: [20 February 2024 22:15 UTC](https://dietpi.com/forum/t/nextcloud-theme-broken-after-upgrade-v9-1-1/19372/6 "2024-02-20T22:15:13Z")
Error log visible in google chrome developer tools console
```auto
Refused to apply style from '' because its MIME type ('application/octet-stream') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
dashboard/:1 Refused to apply style from 'https://cloud.xx.com/nextcloud/apps/dashboard/css/dashboard.css?v=30c53bef-4' because its MIME type ('application/octet-stream') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
dashboard/:1 Refused to apply style from 'https://cloud.xx.com/nextcloud/apps/user_status/css/user-status-menu.css?v=5dbcc382-4' because its MIME type ('application/octet-stream') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
dashboard/:1 Refused to apply style from 'https://cloud.xx.com/nextcloud/core/css/server.css?v=6647f0bf-4' because its MIME type ('application/octet-stream') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
dashboard/:1 Refused to apply style from 'https://cloud.xx.com/nextcloud/apps/activity/css/style.css?v=2e275d50-4' because its MIME type ('application/octet-stream') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
dashboard/:1 Refused to apply style from 'https://cloud.xx.com/nextcloud/apps/dashboard/css/dashboard.css?v=30c53bef-4' because its MIME type ('application/octet-stream') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
dashboard/:1 Refused to apply style from 'https://cloud.xx.com/nextcloud/apps/user_status/css/user-status-menu.css?v=5dbcc382-4' because its MIME type ('application/octet-stream') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
dashboard/:1 Refused to apply style from 'https://cloud.xx.com/nextcloud/core/css/server.css?v=6647f0bf-4' because its MIME type ('application/octet-stream') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
dashboard/:1 Refused to apply style from 'https://cloud.xx.com/nextcloud/apps/activity/css/style.css?v=2e275d50-4' because its MIME type ('application/octet-stream') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
```
---
### Author:  [@Joulinar](https://dietpi.com/forum/u/Joulinar)
#### Post date: [21 February 2024 06:25 UTC](https://dietpi.com/forum/t/nextcloud-theme-broken-after-upgrade-v9-1-1/19372/7 "2024-02-21T06:25:11Z")
Honestly I have no idea how our update should influence this.
Probably some other apt package that has been updated in parallel. 🤔
---
### Author:  [@Jappe](https://dietpi.com/forum/u/Jappe)
#### Post date: [21 February 2024 06:37 UTC](https://dietpi.com/forum/t/nextcloud-theme-broken-after-upgrade-v9-1-1/19372/8 "2024-02-21T06:37:57Z")
~~What Webserver do you use?~~ ah I see, also nginx but on an ARM64 system.
My nextcloud running on lighttpd didn’t break after the update.
Other users instance on nginx and x86 system also broke.
---
### Author:  [@greentea1](https://dietpi.com/forum/u/greentea1)
#### Post date: [21 February 2024 07:05 UTC](https://dietpi.com/forum/t/nextcloud-theme-broken-after-upgrade-v9-1-1/19372/9 "2024-02-21T07:05:41Z")
It happens sometime for me with chrome its not broken just refresh your browser or clear your browser cache
---
### Author:  [@howardroark](https://dietpi.com/forum/u/howardroark)
#### Post date: [21 February 2024 08:14 UTC](https://dietpi.com/forum/t/nextcloud-theme-broken-after-upgrade-v9-1-1/19372/10 "2024-02-21T08:14:45Z")
I’ve tried from different browsers and mobile browser and it doesn’t seem to be related to that. The following error log caught my attention. Somehow the server must not be able to read the css files.
> [@Nextcloud theme broken after upgrade v9.1.1](https://dietpi.com/forum/t/nextcloud-theme-broken-after-upgrade-v9-1-1/19372/6):
>
> Error log visible in google chrome developer tools console Refused to apply style from '\' because its MIME type ('application/octet-stream') is not a supported stylesheet MIME type, and strict MIME checking is enabled. dashboard/:1 Refused to apply style from 'https://cloud.xx.com/nextcloud/apps/dashboard/css/dashboard.css?v=30c53bef-4' because its MIME type ('application/octet-stream') is not a supported stylesheet MIME type, and strict MIME checking is enabled. dashboard/:1 Refused to ap…
---
### Author:  [@Joulinar](https://dietpi.com/forum/u/Joulinar)
#### Post date: [21 February 2024 09:57 UTC](https://dietpi.com/forum/t/nextcloud-theme-broken-after-upgrade-v9-1-1/19372/11 "2024-02-21T09:57:20Z")
ok I did some testing and it seems related to Nginx web server.
@MichaIng any ideas where this is coming from?
---
### Author:  [@MichaIng](https://dietpi.com/forum/u/MichaIng)
#### Post date: [21 February 2024 12:48 UTC](https://dietpi.com/forum/t/nextcloud-theme-broken-after-upgrade-v9-1-1/19372/12 "2024-02-21T12:48:40Z")
Hmm, the MIME type is not set as expected. Let me check, probably `types` blocks within `location` blocks overwrite any parent block MIME type definitions. That would be one of these typical nasty Nginx behaviours for why I always prefer Apache.
---
### Author:  [@MichaIng](https://dietpi.com/forum/u/MichaIng)
#### Post date: [21 February 2024 13:16 UTC](https://dietpi.com/forum/t/nextcloud-theme-broken-after-upgrade-v9-1-1/19372/13 "2024-02-21T13:16:57Z")
Jep that’s it. Pure stupidity IMO, as if someone would want to have ALL MIME types for ALL file extensions busted when defining it for a single additional file extension within a location or server block. While for `add_header`, the same nasty behaviour is at least documented, for `types` I could not find a single hint about it, instead I even find lots of guides who do exactly this: define a single MIME type within a location block. And whatever I search for regarding location and/or server blocks overwriting parent `types`, I do not find a single matching entry, docs, blog of forum post about this …
Since we must serve `mjs` as JavaScript type for Nextcloud to function, we must additionally include the whole default types file above this block, while it is already included in the `http` block of `/etc/nginx/nginx.conf` …
```sh
sed -i '/types {/i\\tinclude mime.types;' /etc/nginx/sites-dietpi/dietpi-nextcloud.conf
systemctl restart nginx
```
You need to do an active (F5) of forced (CTRL+F5) page reload for the change to become effective.
I really can’t understand why Nginx behaves like this. This is so totally non-intuitive to me and means a lot of doubled definitions. We also need to add all security headers 3 times: In the default/parent config, within the Nextcloud `location` block and again within the sub-`location` block for Nextcloud assets, only because those have additionally a `Cache-Control` header set. Nextcloud’s official/documented Nginx config provided in their docs tapped into the same trap and served all assets without any security/privacy header for 2 years, until I found this recently when updating our Nginx config and fixed it. So it is not only me but I find this all the time in various documented Nginx configs across various software projects. This is not only an unnecessary additional maintenance and coding burden, but a security issue as well. Enough for this rant for today 😄 …
I’ll set up a live patch to have this fixed for everyone.
---
### Author:  [@howardroark](https://dietpi.com/forum/u/howardroark)
#### Post date: [21 February 2024 13:36 UTC](https://dietpi.com/forum/t/nextcloud-theme-broken-after-upgrade-v9-1-1/19372/14 "2024-02-21T13:36:43Z")
Worked! Also thank you very much for your detailed explanation, this is a great way to solve things by learning.
---
### Author:  [@system](https://dietpi.com/forum/u/system)
#### Post date: [21 May 2024 13:37 UTC](https://dietpi.com/forum/t/nextcloud-theme-broken-after-upgrade-v9-1-1/19372/15 "2024-05-21T13:37:06Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.