How to make apache serve .js.map

ℹ️ Support
, ,
10

Similar situation after upgrading to NC29, i was faced with a couple of errors:

  • Could not check that the data directory is protected. Please check manually that your server does not allow access to the data directory. 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.
  • 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 if your web server properly resolves the OCM and OCS provider URLs. 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.
  • 12 errors in the logs since August 19, 2024, 3:09:13 PM
  • Could not check that your web server is properly set up to allow file synchronization over WebDAV. 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 :arrow_upper_right:.
  • 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 :arrow_upper_right:.
  • 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 :arrow_upper_right:.
  • Could not check that your web server serves security headers correctly. Please check manually. For more details see the documentation :arrow_upper_right:.

It seems something doesn’t work correct when using subfolders, at least in my case some requests are made to domain/nextcloud/, while others are made to domain/nextcloud/nextcloud/

127.0.0.1 - - [16/Sep/2024:17:36:51 +0200] “HEAD /nextcloud/nextcloud/data/.ocdata HTTP/1.1” 404 2048 “-” “Nextcloud Server Crawler”
127.0.0.1 - - [16/Sep/2024:17:36:51 +0200] “HEAD /nextcloud/nextcloud/data/.ocdata HTTP/1.1” 404 6073 “-” “Nextcloud Server Crawler”
127.0.0.1 - - [16/Sep/2024:17:36:52 +0200] “HEAD /nextcloud/nextcloud/apps/settings/js/map-test.js.map HTTP/1.1” 404 2046 “-” “Nextcloud Server Crawler”
127.0.0.1 - - [16/Sep/2024:17:36:52 +0200] “HEAD /nextcloud/nextcloud/apps/settings/js/map-test.js.map HTTP/1.1” 404 6075 “-” “Nextcloud Server Crawler”
127.0.0.1 - - [16/Sep/2024:17:36:52 +0200] “HEAD /nextcloud/nextcloud/apps/settings/js/esm-test.mjs HTTP/1.1” 404 2050 “-” “Nextcloud Server Crawler”
127.0.0.1 - - [16/Sep/2024:17:36:52 +0200] “HEAD /nextcloud/nextcloud/apps/settings/js/esm-test.mjs HTTP/1.1” 404 6073 “-” “Nextcloud Server Crawler”
127.0.0.1 - - [16/Sep/2024:17:36:53 +0200] “HEAD /nextcloud/ocm-provider/ HTTP/1.1” 200 1427 “-” “Nextcloud Server Crawler”
127.0.0.1 - - [16/Sep/2024:17:36:53 +0200] “HEAD /nextcloud/ocs-provider/ HTTP/1.1” 200 1396 “-” “Nextcloud Server Crawler”
127.0.0.1 - - [16/Sep/2024:17:36:53 +0200] “GET /nextcloud/nextcloud/index.php/heartbeat HTTP/1.1” 404 6776 “-” “Nextcloud Server Crawler”
127.0.0.1 - - [16/Sep/2024:17:36:53 +0200] “GET /nextcloud/nextcloud/index.php/heartbeat HTTP/1.1” 404 10799 “-” “Nextcloud Server Crawler”
127.0.0.1 - - [16/Sep/2024:17:36:53 +0200] “HEAD /nextcloud/nextcloud/core/fonts/NotoSans-Regular-latin.woff2 HTTP/1.1” 404 2046 “-” “Nextcloud Server Crawler”
127.0.0.1 - - [16/Sep/2024:17:36:53 +0200] “HEAD /nextcloud/nextcloud/core/fonts/NotoSans-Regular-latin.woff2 HTTP/1.1” 404 6073 “-” “Nextcloud Server Crawler”

i ended up adding a redirect rule to my .htaccess file:

Redirect “/nextcloud/nextcloud” “/nextcloud”

I’m certain there are better ways to fix this but it’s well enough for my personal needs.

2 Likes