4ch1m
commented
3 months ago Hi there,
I have discovered the same issue. (And I think it is related to #40252.)
This line needs to be improved:
It obviously doesn't take overwritewebroot into consideration; which is used when running Nextcloud behind a reverse proxy (see: "Reverse proxy").
Combined with a fail2ban-setup, this issue may have severe impact, because you will be locked out completely after the CSS tries to load the background. (Which happened in my case. :smile:)
derbenx
⚠️ This issue respects the following points: ⚠️
Bug description
In maintenance mode background comes up as 404 when nextcloud is in a folder. It's been in pretty much every version, since I remember. :P think the updating mode does this too...
it tries to use: https://server.xxx/apps/theming/img/background/kamil-porembinski-clouds.jpg instead of: https://server.xxx/subdir/apps/theming/img/background/kamil-porembinski-clouds.jpg It's configured in weblink, under theming with the folder and anywhere else I can think of.
I tried light and dark theme, in case it was one or the other.
Steps to reproduce
Expected behavior
no 404 errors.
Installation method
Community Manual installation with Archive
Nextcloud Server version
29
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.2
Web server
Apache (supported)
Database engine version
MySQL
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
\apps\theming\css\default.css is hard coded to: --image-background-default: url('/apps/theming/img/background/kamil-porembinski-clouds.jpg');
This seems to fix it: --image-background-default: url('../../apps/theming/img/background/kamil-porembinski-clouds.jpg');