Are these issues real issues I should be concerned about?

ℹ️ Support
, , , , , ,
1

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • Latest AIO
  • Operating system and version (e.g., Ubuntu 24.04):
    • TrueNAS Scale, running in a docker app.
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • Cloudflare Tunnel

Hello,

I finally got Nextcloud AIO working on my Truenas server using Cloudflare Tunnel. I’m aware of a lot of the issues and difficulties that exist using this method (took me a few days to get things to run nicely in the first place), and now that it is seemingly working without issue, I want to ask some questions about errors I do see and whether they are superficial or valid complaints the system is spitting at me. Beyond that, any thoughts, ideas, questions, or concerns you think I should be aware of would be greatly appreciated! I’m more so exploring the utility of having a home NAS/server and how I can de-google my life in favor of a self hosted solution I can access from anywhere and easily give similar access to those I approve of.

First off, looking at the admin overview panel, I am met with the following error notices:

Overview

  • Error: Cannot connect to server

  • 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 Web server can connect to itself. Therefore it must be able to resolve and connect to at least one of its trusted_domains or the overwrite.cli.url. This failure may be the result of a server-side DNS mismatch or outbound firewall rule.

  • 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.

  • Unable to run check for JavaScript support. Please remedy or confirm 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 Web server can connect to itself. Therefore it must be able to resolve and connect to at least one of its trusted_domains or the overwrite.cli.url. This failure may be the result of a server-side DNS mismatch or outbound firewall rule.

  • 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 Web server can connect to itself. Therefore it must be able to resolve and connect to at least one of its trusted_domains or the overwrite.cli.url. This failure may be the result of a server-side DNS mismatch or outbound firewall rule.

  • 165 errors in the logs since April 7, 2025, 5:37:23 PM

  • One or more mimetype migrations are available. Occasionally new mimetypes are added to better handle certain file types. Migrating the mimetypes take a long time on larger instances so this is not done automatically during upgrades. Use the command occ maintenance:repair --include-expensive to perform the migrations.

  • 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 Web server can connect to itself. Therefore it must be able to resolve and connect to at least one of its trusted_domains or the overwrite.cli.url. This failure may be the result of a server-side DNS mismatch or outbound firewall rule. 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 Web server can connect to itself. Therefore it must be able to resolve and connect to at least one of its trusted_domains or the overwrite.cli.url. This failure may be the result of a server-side DNS mismatch or outbound firewall rule. 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 Web server can connect to itself. Therefore it must be able to resolve and connect to at least one of its trusted_domains or the overwrite.cli.url. This failure may be the result of a server-side DNS mismatch or outbound firewall rule. For more details see the documentation :arrow_upper_right:.

  • Your installation has no default phone region set. This is required to validate phone numbers in the profile settings without a country code. To allow numbers without a country code, please add “default_phone_region” with the respective ISO 3166-1 code of the region to your config file. For more details see the documentation :arrow_upper_right:.

  • No SIP backend configured

  • Could not check for WASM loading support. Please check manually if your web server serves .wasm files. To allow this check to run you have to make sure that your Web server can connect to itself. Therefore it must be able to resolve and connect to at least one of its trusted_domains or the overwrite.cli.url. This failure may be the result of a server-side DNS mismatch or outbound firewall rule. For more details see the documentation :arrow_upper_right:.

Some things appear to be low concern, like the “default phone region” bit. But things up top seem more important (plus they are colorful in my dashboard). I question their validity as the red error “cannot connect to server” appears to be more of it not liking that it is behind Cloudflare Tunnel, as I can clearly connect to the server via my URL from a remote network.

The things asking questions such as checking the data directory seem to be more valid, but I want to make sure it is a real concern or something made by the tunnel before I tweak things and break something (again).


Next we have the error log that the overview points to. This is a lot of repeating the same set of errors and boils down to the following:


[details="Log errors"]
ConnectException
cURL error 7: Failed to connect to [redacted] port 443 after 6 ms: Could not connect to server (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for [redacted]/cool/convert-to/png
Failed to convert preview: cURL error 7: Failed to connect to [redacted] port 443 after 6 ms: Could not connect to server (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for [redacted]/cool/convert-to/png

ConnectException
cURL error 6: Could not resolve host: [redacted] (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for [redacted]/hosting/discovery

Undefined array key "error" at /var/www/html/apps/weather_status/lib/Service/WeatherStatusService.php#260
[/details]

As stated, these mostly repeat as the services attempt to try again. I'm not entirely sure if there is a valid way to resolve these complaints the system has as I am using Cloudflare Tunnel, and as far as I can tell, there aren't any notable breaks in the software? So from what I can tell, this is just the equivalent of a car's "check engine" light and I can safely ignore it. If I am mistaken in this and it is something that needs to be resolved for the service's proper functionality, any assistance in getting it to work would be greatly appreciated!

Next things appear to be calm in all the admin tabs until we get to the Office tab with Collabora. It spits two red and yellow error boxes at me with the following respectively:

Office tab

Could not establish connection to the Collabora Online server.

Failed to connect to the remote server: cURL error 6: Could not resolve host: [redacted] (see libcurl - Error Codes) for [redacted]/hosting/discovery


You have not configured the allow-list for WOPI requests. Without this setting users may download restricted files via WOPI requests to the Nextcloud server. [Click here for more info](https://docs.nextcloud.com/server/latest/admin_manual/office/configuration.html#wopi-settings)

This one I haven’t played with too much yet beyond opening a docx file I uploaded to the drive. Nextcloud seems to handle it well. I can scroll, edit, and do things with it as far as I can tell. So it also appears to be crying wolf? But again, if it is something I need to resolve, let me know and I’ll put it on my priority list!


From what I can see right now, those are the only complaints the system appears to be yelling about at this time. And it seems to be running fine for what I have tested. I will probably be exploring possible solutions regardless, but with how many times I had to restart from 0 the past few days, I would like to not risk breaking things again if everything is actually fine.

Again, I thank you all for your comments and thoughts ^.^/ I look forward to exploring and learning more about Nextcloud and the general utility I can get out of my new system~