So how come it’s failing the check and throwing up the “Could not check for JavaScript support. Please check manually if your webserver serves .mjs files using the JavaScript MIME type.” error in the Administration>Overview?
@szaimen You have been able to help countless times before. Do you have any idea on how to resolve this issue? I say issue, it doesn’t seem to actually be affecting by Nextcloud from operating, it’s just reporting this error.
Check if any of the docker containers have updates for them. AIO uses Apache 2 as a webserver, so I can’t speak specifically to that, since I use nginx running on bare metal.
I needed to add a line to my nginx mime types file in /etc/nginx/mime.types:
application/javascript js;
application/javascript mjs;
I can only assume that in the apache container there is a similar config file, where mjs has to be added. Either by the AIO-Maintainers or manually by you.
This doesn’t directly solve your issue, but should give you information on what to search for and how to solve it. Fingers crossed!
@canisdata I will have a look and see what I can find. It seems funny that no one from support can offer any advice on this. It seems to be a widespread problem experienced by many users. For me, at least, it only appeared recently.
Not sure what you mean by “from support”. This is a community forum and everyone here is volunteering to help others for free.
There are a lot of posts about this topic - many with answers - because it’s a legitimate check to detect a problem.
The vast majority of the occurrences where this warning pops up are local environment matters - generally internal DNS or outbound firewall situations.
You posted output saying you tried from the container and it worked, but the error from your log suggests that isn’t the case. Did you test with https? That’s what needs to work.
Is the https interface on HAProxy via pfsense perhaps not reachable within your network (or, at the very least, not from the Docker network you have AIO on)? If so, that’s what needs to be fixed. Either via the approach suggested by @szaimen or by making the HAProxy external https interface (what your Nextcloud hostname is presumably pointed at), reachable from within your network (which would need to be addressed at the pfsense and/or HAProxy level).
P.S. This isn’t the check saying .mjs handling is failing; this is the check itself for that handling not even being able to execute because of a local environment matter.