-
-
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
[Bug]: There are some warnings regarding your setup (v29) #44114
Comments
We also have the same problem after updating to Nextcloud Hub 8 version (29.0.0 beta 1) from version 28.0.3. The same messages after update vía GUI web interface. |
Well done :-) Security & setup warnings All checks passed. Version Update |
btw - what did you do with 29.x - it runs much faster than ever - wough - what a difference ! |
Thanks for the report @Githopp192. Going to close this out since it seems fixed. :) |
should be
e.g. line server/apps/settings/l10n/en_GB.json Line 131 in cb27fbc
|
I still have this issue, after updating to NC 29.0.0 yesterday:
I am running NC in a docker-container in a VM behind a proxy on another VM on th same host. I installed with this docker-compose:
maybe, because I linked the volume to another partition?
mountpoint
I tried
but the messages are still there |
I have the same issue after upgrading. Nextcloud 29.0.0 is installed directly on arch linux. No docker is involved. Where does nextcloud take the domain from for checking? |
Actually, I get an error in the logs:
Which is weird, because |
@rubo77 All your failures suggest the app container itself can't connect to your
Causes are usually internal DNS not matching your external DNS or internal firewalling that prevents connecting from the Nextcloud Server through your HTTPS/reverse proxy server. In older Nextcloud versions many of these checks ran from your browser. Now that they're server-side, the connectivity from the Nextcloud Server to itself matters.
@t-h-e See above.
Is it reachable via https from the Server itself? e.g. test with |
@joshtrichards Yes, for me the issue was that the server was not able to reach itself via the domain name. I added an entry in |
Can you please show your hosts file? |
Replace Afterwards, if you ping the domain from your server, it should ping |
With the recommended nginx configuration.
|
I'm not a GitHub user, so please have patience! I looked through this thread and it indicates that this "bug" is fixed. I just upgraded my NC to Hub 8 and I get all of the indicated error messages at the head of this, yet a scan of the headers from the system shows that all is well with an A+ rating. I took each error one by one, and my configuration files seem to be fine! Any clues where I should start? TIA |
As someone also seeing this, I'm hoping to add a useful "data point". If I try
The same command from my desktop succeeds (with the <IPv6#> and <IPv4#> here matching those shown in the above):
So I assume I have some other server configuration problem here, and its not a NextCloud problem itself. But not obvious to me what I need to do to fix it. (My server is cPanel-based for what it's worth.) |
Update: The https server couldn't communicate properly because... of a slight misconfiguration in my hosts file. Yeah. Please disregard my posts, thx. |
Perhaps as an "on the other hand", I looked at the apache logs after a check, and found the following: In the
Also, fwiw, is the following in Apache's
|
If you land here, please take troubleshooting queries to the help forum: https://help.nextcloud.com EDIT: Some clarifications added to the Release Notes which some may find helpful: https://docs.nextcloud.com/server/latest/admin_manual/release_notes/upgrade_to_28.html#setup-checks |
What did you do to solve the warnings? |
In my case, based on the comment by SomeGuyInSandy above, I checked my My VPS is managed by cPanel. I don't recall having looked at my My entries map to the public IP#s, not Hope this helps. |
I have my Nextcloud instance running on Docker. Recently, after a sudden server restart (hosted on-premise), the application is not resolving to the correct internal IP address. Steps Taken:
Despite these efforts, the issue persists. When pinging the Nextcloud domain from inside the server, it resolves to an incorrect external IP address. Question: Could the incorrect resolution to the external IP address instead of the internal IP be causing the issue? Additional Information:
Nextcloud version: 29.0.3 (Nextcloud Hub 8) Any assistance in resolving this issue would be greatly appreciated. Thank you. |
@arioberek Please post your query on the help forum - https://help.nextcloud.com This channel is for bug reports. Every time someone posts here it notifies all the developers, which isn't a good use for everyone's limited time and energy. :-) The Community Help Forum is a good spot for this sort of thing. Thanks! |
I think this is related to server configuration, and not necessarily a bug. But it is a bit complex. Since Docker was mentioned, I know these warnings can be caused by running Nextcloud inside a container without internet access — or, if you have specifically configured your container with a non-standard port, maybe because you have a proxy like Treafik handle actual 80 and 443 traffic externally. That is, if you get to see them at all, because I noticed the problem by manually requesting So, if that is a problem for you as well, then simply use the standard ports internally. It is perfectly possible to run your web server on the standard ports, if they are only exposed on the internal network, and still have another service like Traefik handle 443 and 80 traffic on the WAN. For Docker, I think it is a good idea to have two networks configured in
Instead of:
Long story short. Nextcloud needs internet for updates and to perform its checks. This means that your PHP-FPM container should at least have internet access, still while carefully making sure not to accidentally expose port 9000 directly to the internet. E.g. use |
Bug description
TEST Uprade from NC 28.0.3 to 29.0.0. BETA:
There are some warnings regarding your setup.
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 theoverwrite.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. 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 itstrusted_domains
or theoverwrite.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 theoverwrite.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 itstrusted_domains
or theoverwrite.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 itstrusted_domains
or theoverwrite.cli.url
. For more details see the documentation ↗.Please double check the installation guides ↗, and check for any errors or warnings in the log.
Steps to reproduce
Expected behavior
no warnings or errors
Installation method
Community Manual installation with Archive
Nextcloud Server version
28
Operating system
RHEL/CentOS
PHP engine version
PHP 8.2
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Upgraded to a MAJOR version (ex. 22 to 23)
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
Nextcloud Logs
No response
using self singed cert. (Nextcloud vm test instance)
No response
The text was updated successfully, but these errors were encountered: