Closed adhoc-post closed 1 month ago
Would you mind sharing your virtual host (?or server block?) file?
What fixed it for me, was correcting a misconfiguration I had done in the .conf file that managed the nextcloud site. Specifically, I had it configured like this:
Alias /nextcloud "var/www/nextcloud"
DocumentRoot /var/www
This, might have somehow messed up the forwarding of requests to the server. What fixed it though, was (obviously):
Alias /nextcloud "var/www/nextcloud"
DocumentRoot /var/www/nextcloud
My nextcloud.conf
(Apache) looks like this:
Alias /nextcloud "/var/www/nextcloud/"
<Directory /var/www/nextcloud/>
Require all granted
AllowOverride All
Options FollowSymLinks MultiViews
<IfModule mod_dav.c>
Dav off
</IfModule>
Header always set Strict-Transport-Security "max-age=15552000; includeSubDomains"
Satisfy Any
</Directory>
Looks like the reverse proxy and the rewrite rules are not in there. They are essential for communicating with the backend websocket server.
They are on the bottom of the README.md, but, here's a version similar to my setup:
ProxyPreserveHost On
ProxyPass /whiteboard/ http://yourDomain:backendServerPort/ retry=0
ProxyPassReverse /whiteboard/ http://yourDomain:backendServerPort/
RewriteEngine on
RewriteCond %{HTTP:Upgrade} websocket [NC]
RewriteCond %{HTTP:Connection} upgrade [NC]
RewriteRule ^/?whiteboard/(.*) "ws://yourDomain:backendServerPort/$1" [P,L]
The first lines setup the reverse proxy, while the rewrite rules...:
ws://yourDomain:backendServerPort/whatever
EDIT: Forgot to mention that the rewrite rules belong to the rewrite module of apache.
This needs to be enabled, I don't believe its on by default on a debian/ubuntu system when installing apache.
sudo a2enmod rewrite
Thanks for your reply. But I have to admit: after reading the README.md you mentioned, the scope of this app took me by surprise. I was expecting a simple app. However, there seems to be much more to it than that.
And therefore, I haven't RTFM. So, please don't bother explaining further details to me as I have to do my homework first.
So, thanks for your effort and for point out the obvious to me.
I guess, this bug ticket can be closed (PEBKAC).
⚠️ This issue respects the following points: ⚠️
Bug description
After update to NC30, whiteboards can be created but not edited. When opening a created whitebaord, the app opens but immediately reports: "server: Request failed with status code 404" and closes again.
Steps to reproduce
Expected behavior
No error reported and app allows editing the whiteboard.
Nextcloud Server version
30
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.3
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Upgraded to a MAJOR version (ex. 28 to 29)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
Is it true that "Nextcloud 30 been rolled out over the “stable” channel although known to be unstable"?!
https://help.nextcloud.com/t/nextcloud-30-been-rolled-out-over-the-stable-channel-although-known-to-be-unstable/204189