Nextcloud 29.0.6 was perfectly running on my NAS Synology with:
PHP 8.2.21-0104
APACHE 2.4.58-0150
MariaDB 10.11.6-1369
Redis 7.0.11-14
I migrated the instance to Nextcloud 29.0.7
Lot of errors appeared:
Failed to get an iterator for log entries: Error while opening /volume1/OCTData/nextcloud.log
Your webserver is not set up to serve .js.map files. Without these files, JavaScript Source Maps won’t function properly, making it more challenging to troubleshoot and debug any issues that may arise.
Could not check for JavaScript support via any of your trusted_domains nor overwrite.cli.url. This may be the result of a server-side DNS mismatch or outbound firewall rule. Please check manually if your webserver serves .mjs files using the JavaScript MIME type. To allow this check to run you have to make sure that your webserver can connect to itself. Therefor it must be able to resolve and connect to at least one its trusted_domains or the overwrite.cli.url.
Could not check that your web server serves security headers correctly, unable to query /OCT/index.php/heartbeat For more details see the documentation .
Could not check that your web server serves .well-known correctly. Please check manually. To allow this check to run you have to make sure that your webserver can connect to itself. Therefor it must be able to resolve and connect to at least one its trusted_domains or the overwrite.cli.url. For more details see the documentation .
Could not check for WOFF2 loading support. Please check manually if your webserver serves .woff2 files. To allow this check to run you have to make sure that your webserver can connect to itself. Therefor it must be able to resolve and connect to at least one its trusted_domains or the overwrite.cli.url. For more details see the documentation .
The recent changes in how nextcloud performs these internal security checks seems to have introduced a few bugs, especially in the case of nextcloud installed in a subdirectory of your webserver.
The documentation provided doesn’t give examples on how to test them yourself and assumes the nextcloud warnings are valid, which they aren’t.
I have the same problem since I have migrated to 29.0.7 : A lot of error appeared but nextcloud still works fine… (My nextcloud is on raspberry pi5) :
Your web server is not configured to serve .js.map files. Without these files, JavaScript source maps will not work properly, making it more difficult to troubleshoot and resolve potential issues.
Unable to verify Javascript support through one of your trusted_domains or overwrite.cli.url. This may be due to a server-side DNS mismatch or an outbound firewall rule. Please manually check if your web server is serving .mjs files using the JavaScript MIME type. To allow this check, you must ensure that your web server can connect to itself. It must be able to resolve and connect to at least one of its trusted_domains or the overwrite.cli.url URL.
Unable to verify that your web server is serving security headers correctly, unable to request /nextcloud/heartbeat
I hadn’t these issues with previous version and I don’t change anything on my serveur configuration…
There are some refinements going on for subdirectory handling with these checks. Not all made it in time for this latest maintenance release, but they’re actively being worked on (or already merged). Hopefully will be tightened up a bit for the next maintenance release.
Same here. Quite frankly, Nextcloud to me makes a less and less trustworthy impression. I have my instance up and running since 2018 and it seems that in the last releases more and more “unfinished” code made it into production. Why the heck they had to release the 29.0.7 just two weeks after .06? And if your explanation is correct, why include half a dozen of unfinished checks?
So i am not sure now: Will there be even more messages, or are these messages false positives?
I had an error during upgrade from 29.0.6 to 29.0.7 concerning onlyoffice
Log Entry:
[onlyoffice] Fatal: Error during app service registration: An exception occurred while executing a query: SQLSTATE[22001]: String data, right truncated: 7 FEHLER: Wert zu lang für Typ character varying(32)
von ? von – um 13.09.2024, 11:56:08
It only occurs once as far as i can see but don’t know if there is need of any action by myself or not.
ONLYOFFICE is running as a docker instance beside NC (native installed on ubuntu server 22.04.5)
The docker image is “latest” (stable)…
Hi,
same problem here. In addition to the above mentioned symptoms I can add the following:
The system complains about missing WOFF2 support and the documentation link below the error message ref. NGINX only
I have also noted that the security scan advises that I’m on NC Vers. 29.0.2.2 and not on 29.0.7
Since the system is still working I guess it is better to be patient for a while before doing anything stupid
Thanks
I updated from 29.0.7 to 30.0.0 with the hope that solves all the false error I have after updating to 29.0.7.
Unfortunately, it’s worse… several red error appeared As I have a clone of my server’s ssd with 29.0.5 : i come back to 29.0.5 version whitch works fine, and wait for a validated 30.x.x version
Thank you for informing us. Following this warning, I am staying with version 27.0.6, which seems stable, and will wait for 30.0.1 or 30.0.2 before upgrading.
.