For many versions I have kept the following warnings and would be glad if someone from nextcloud team/staff shares their experience for community instead of watching facebook, youtube, tiktok algorithmical stuff.
⚠ .well-known URLs: Your web server is not properly set up to resolve `.well-known` URLs, failed on:
⚠ Mimetype migrations available: One or more mimetype migrations are available. Occasionally new mimetypes are added to better handle certain file types. Migrating the mimetypes take a long time on larger instances so this is not done automatically during upgrades. Use the command `occ maintenance:repair --include-expensive` to perform the migrations.
⚠ HTTP headers: Some headers are not set correctly on your instance
[root@antcloud config]#
Does maybe anyone have an idea? I spent more than 10, ten hours on sorting out these three warnings, and nothing helps.
My cofig is a static IP with a reverse proxyserver running httpd on another vm than the nextcloud vm. I am aware there is httpd running on nextcloud, too.
One hint that I could ask. These three warnings, are they related to httpd on my reverse proxy or are they related to the httpd on the nextcloud vm ?
If I could watch the browser console, in what direction shall I debug and send screenshots, in order to realize where these warnings come from and if I am able to remove them at all.
https://antcloud.domain.tld/nextcloud is the nextcloud reachable address. Also Webdav, CalDav, CarDav work and my data is an NFS mount on a truenas Server
Just upgraded Archlinux Hub 8 29.0.7 from 29.0.6 and instead of fixing .well-known finger per the patch in the last thread, the update broke more than it fixed. After applying the web-finger patch to 29.0.6 I had NO warnings in the administrator check. Now after update to 29.0.7 I get:
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 .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 .
This looks like 0-steps forward 4-steps back. How to fix this mess?
I have exactly the same messages since the Update to 29.0.7.
I have nextcloud in a subdirectory (https://domain-name/cloud/ in my case)
and the apache access-log shows the following:
Same Problem. Nextcloud 29 check problems are totally annoying and the automated .htaccess rewrite always kills the workaround to e.g. the webfinger-problem. Our Nextcloud is installed in a subdirectory and for example .js.map etc. all work when tested via curl on the command line.
Same problem here with two very different installations. No warning in 29.0.6. Which item in changelog could lead to this behavior?
I just realized that path mangling is even worse. My data directory is /hd1/nextCloud, but when testing presence of .ocdata, nextcloud looks for /nextcloud/nextcloud//hd1/nextCloud/.ocdata.
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 /nc/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 .
Either in your configuration for your virtual web server (Apache2, nginx) or if this is not possible in /path/to/html/.htaccess or /path/to/html/nextcloud/.htaccess. Although I’m not sure whether this will work.
This is not really useful, as these are only warnings triggered by the Nextcloud system check.
instead of watching facebook, youtube, tiktok algorithmical stuff.
Use Debian 12, Apache, php8.2