Nextcloud Upgrade 28.0.3 still the same error

ℹ️ Support
,
1

Hello, I get this error message despite update 28.0.3

“Could not check for JavaScript support. Please check manually if your webserver serves .mjs files using the JavaScript MIME type.”

ClientException Client error: HEAD https://yourDomain/apps/settings/js/esm-test.mjs resulted in a 403 Forbidden response
Can not connect to local server for checking JavaScript modules support

I run myNextcloud as a Docker container and access is enabled by nginx reverse proxy

Does the line have to be entered in the Nextcloud container or Docker host

thx

2

Can you post more information? But maybe this nginx problem. Read also here.

3

And user has posted this unfortunately nobody knows an answer

Woodboy12

I added an entry to my host file on Debian 11 and it seems to have fixed this error.

sudo nano /etc/hosts

added

127.0.0.1 your.nextcloud_domain.com

Link

1 Like
4

What information do you need exactly ?

5

It fixed the problem for me as well. :slight_smile:

6

Hello!

Does the line have to be entered in the Nextcloud container or Docker host ?

thx

7

To be onest - I dont know.
My Nextcloud is not runnig in a Docker-Container.

I just added in
/etc/hosts

the line

127.0.0.1 your.nextcloud_domain.com

and it worked.
Maybe you can try first in de Nextcloud-Container, if not then the Docker Host?
Regards Andreas

8

Has anyone installed Nextcloud like this: Nextcloud container or Docker host with this error ?
Would appreciate any help

Best regards

9

I’ll give it a try.

10

Just wanted to update from 28.0.2 to 28.0.3 and I get also an error.
28.0.2 was working absolutly fine. I updated via portainer. I Have a docker container runing on my synology nas.

What shal I do?

here is the log

Configuring Redis as session handler
=> Searching for scripts (.sh) to run, located in the folder: /docker-entrypoint-hooks.d/before-starting
AH00558: apache2: Could not reliably determine the server’s fully qualified domain name, using 192.168.144.4. Set the ‘ServerName’ directive globally to suppress this message
AH00558: apache2: Could not reliably determine the server’s fully qualified domain name, using 192.168.144.4. Set the ‘ServerName’ directive globally to suppress this message
[Sat Mar 09 22:40:05.488770 2024] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.57 (Debian) PHP/8.2.16 configured – resuming normal operations
[Sat Mar 09 22:40:05.488800 2024] [core:notice] [pid 1] AH00094: Command line: ‘apache2 -D FOREGROUND’
127.0.0.1 - - [09/Mar/2024:22:40:34 +0000] “GET / HTTP/1.1” 503 10087 “-” “curl/7.88.1”
127.0.0.1 - - [09/Mar/2024:22:41:04 +0000] “GET / HTTP/1.1” 503 10093 “-” “curl/7.88.1”
127.0.0.1 - - [09/Mar/2024:22:41:35 +0000] “GET / HTTP/1.1” 503 10085 “-” “curl/7.88.1”
127.0.0.1 - - [09/Mar/2024:22:42:05 +0000] “GET / HTTP/1.1” 503 10087 “-” “curl/7.88.1”
127.0.0.1 - - [09/Mar/2024:22:42:36 +0000] “GET / HTTP/1.1” 503 10087 “-” “curl/7.88.1”
127.0.0.1 - - [09/Mar/2024:22:43:07 +0000] “GET / HTTP/1.1” 503 10087 “-” “curl/7.88.1”
[Sat Mar 09 22:43:24.814463 2024] [mpm_prefork:notice] [pid 1] AH00170: caught SIGWINCH, shutting down gracefully
Configuring Redis as session handler
=> Searching for scripts (.sh) to run, located in the folder: /docker-entrypoint-hooks.d/before-starting
AH00558: apache2: Could not reliably determine the server’s fully qualified domain name, using 192.168.144.4. Set the ‘ServerName’ directive globally to suppress this message
AH00558: apache2: Could not reliably determine the server’s fully qualified domain name, using 192.168.144.4. Set the ‘ServerName’ directive globally to suppress this message
[Sat Mar 09 22:43:31.211370 2024] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.57 (Debian) PHP/8.2.16 configured – resuming normal operations
[Sat Mar 09 22:43:31.211397 2024] [core:notice] [pid 1] AH00094: Command line: ‘apache2 -D FOREGROUND’
127.0.0.1 - - [09/Mar/2024:22:44:01 +0000] “GET / HTTP/1.1” 503 10087 “-” “curl/7.88.1”
127.0.0.1 - - [09/Mar/2024:22:44:31 +0000] “GET / HTTP/1.1” 503 10089 “-” “curl/7.88.1”

11

The error still occurs even if I customize the host file and if I customize it in the Nextcloud folder it is recreated on reboot and the entry is gone.

Does anyone else have a solution or could this be fixed with the next update?

Error:
Nextcloud Security & setup warnings:
Could not check for JavaScript support. Please check manually if your webserver serves .mjs files using the JavaScript MIME type.

Nextcloud Log:

ClientException Client error: HEAD https://you Domain/apps/settings/js/esm-test.mjs resulted in a 403 Forbidden response
Can not connect to local server for checking JavaScript modules support

12

To the Nextcloud support team!

Does no one have a solution for my problem or can it be fixed in the next update?

thx

13

I run one nc-instance with nginx “natively” (no revproxy, no docker etc) and in its admin-interface i always get the “mjs mimetype-error.” I fixed the minetypes via nginx’s configs and since curl -I https://xxx.xxx.xxx/apps/settings/js/esm-test.mjs gets content-type: text/javascript (exactly the same as with an apache-instance) i decided to just ignore that.
per your problem you need to find out exactly where (apache, nginx, dns) it happened and fix it there - i’d consider a 403 not too complex to debug.
GOOD LUCK!

14

I hope it will be fixed with the next update

15

after update to 28.0.4 still the same problem too bad