-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.mjs
setup check failing with self-signed certificate
#43153
Comments
.mjs
setup check failing with self-signed certificate
Cc @susnux |
@theoriginalguy you can add your certificate to the truested ones like this: |
I have the same problem with PHP 8.1 & Apache.
-- I made a few attempts by deleting and adding certificates again, and I found that:
To sum up:
|
So this did resolve my issue, but my question is am I going to have to do this every time the certificate expires? |
you could also automate this when you deploy your new certificate to your server. But we will include a fix for this in 28.0.3 |
I'm using a certificate from Let's Encrypt and also have this message in serverurl/settings/admin/overview, "Security & setup warnings". But nice that it already will be fixed in next version 👍🏼 |
That could have a different reason, please enable debug logging ( |
@thomasmerz make sure you are not missing this part
In your nginx configuration |
This nginx config will throw a warning, because application/javascript js is already set in the mimes.conf file. As far as I understand it, application/javascript is the better way to do it, but I don't know if Nextcloud can handle that. |
You can do both, either add It does not make a big difference, as browsers support both, but the recommended MIME is |
As https://github.com/nextcloud/docker/blob/master/.examples/docker-compose/with-nginx-proxy/mariadb/fpm/web/nginx.conf#L165-L176 says, this should be fixed uptream in nginx!? Currently it's only a warning that doesn't impact me or my users/family using our private nextcloud. So I can (and may have to?) wait… 😉 |
Please not that if you do not configure your webserver to serve |
@susnux , still not available with 28.0.3? When will it be available or did the fix not work? |
It is working. As you can see it says that it could not check it but did not fail. Are you sure your Nextcloud instance can connect to itself? Meaning that it can resolve any of the trusted domains? So please provide the debug log message so we can figure out what is going on. |
Bug description
After upgrading from 27.1.5 to 28.0.2 RC4, despite having support for mjs MIME type file, I am seeing the following unclear-able warning message:
"Could not check for JavaScript support. Please check manually if your webserver serves
.mjs
files using the JavaScript MIME type."After investigation on my side it appears that the curl check from the JavaScriptModeules.php does not account for self signed certificates, and in my case I run Nextcloud locally and have no need for a legit certificate. I would like either support for self-signed certs, or a way to silence this message (preferably support for self-signed certs).
Steps to reproduce
1.Run NC with a self-signed certificate in 27.1.5
2. Follow upgrade documents to upgrade to NC 28.0.2 RC4
Expected behavior
There should be no warnings or errors regarding .mjs MIME Type support if the webserver allows them.
Installation method
Official All-in-One appliance
Nextcloud Server version
28
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.2
Web server
Nginx
Database engine version
None
Is this bug present after an update or on a fresh install?
Updated from a MINOR version (ex. 22.1 to 22.2)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response
The text was updated successfully, but these errors were encountered: