Setup checks fail on 31.0.13.1, HTTP connection

Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. :heart:

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • 31.0.13.1
      
  • Operating system and version (e.g., Ubuntu 24.04):
    • Red Hat Enterprise Linux release 9.7 (Plow)
  • Web server and version (e.g, Apache 2.4.25):
    • nginx/1.20.1
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • replace me
  • PHP version (e.g, 8.3):
    • PHP 8.3.30
  • Is this the first time you’ve seen this error? (Yes / No):
    • Yes
  • When did this problem seem to first start?
    • When upgrading to 30.0.2
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • Archive
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • No

Summary of the issue you are facing:

settings/admin/overview shows

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

  • sudo -u apache php occ setupchecks -vvv
    shows✗ WebDAV endpoint: Your web server is not yet properly set up to allow file synchronization, because the WebDAV interface seems to be broken.
    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.

  • Log shows, that HTTP connections are tried. But only HTTPS is configured. Port 80 is closed.

Steps to replicate it (hint: details matter!)

  1. Upgrade to 30.0.2

Log entries

Nextcloud

Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary.

PASTE HERE  "reqId": "A5T5ZSxqm7qR1rokylnn",
  "level": 0,
  "time": "January 22, 2026 11:58:22",
  "remoteAddr": "",
  "user": "--",
  "app": "settings",
  "method": "",
  "url": "--",
  "scriptName": "occ",
  "message": "Can not connect to local server for running setup checks",
  "userAgent": "--",
  "version": "31.0.13.1",
  "occ_command": [
    "occ",
    "setupchecks"
  ],
  "exception": {
    "Exception": "GuzzleHttp\\Exception\\ConnectException",
    "Message": "cURL error 28: Operation timed out after 30001 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for
 http://a.b.c/apps/theming/fonts/OpenDyslexic-Regular.otf",
    "Code": 0,
    "Trace": [
      {
        "file": "/var/www/abc/nextcloud-31.0.13/3rdparty/guzzlehttp/guzzle/src/Handler/CurlFactory.php",
        "line": 205,
        "function": "createRejection",
        "class": "GuzzleHttp\\Handler\\CurlFactory",
        "type": "::",
        "args": [
          "*** sensitive parameters replaced ***"
        ]
      },
      {
        "file": "/var/www/abc/nextcloud-31.0.13/3rdparty/guzzlehttp/guzzle/src/Handler/CurlFactory.php",
        "line": 157,
        "function": "finishError",
        "class": "GuzzleHttp\\Handler\\CurlFactory",
        "type": "::"
      },

Web Browser

If the problem is related to the Web interface, open your browser inspector Console and Network tabs while refreshing (reloading) and reproducing the problem. Provide any relevant output/errors here that appear.

PASTE

Web server / Reverse Proxy

The output of your Apache/nginx/system log in /var/log/____:

PASTE HERE

Configuration

Nextcloud

The output of occ config:list system or similar is best, but, if not possible, the contents of your config.php file from /path/to/nextcloud is fine (make sure to remove any identifiable information!):

 'trusted_domains' =>
  array (
    0 => 'a.b.c',
  ),
  'datadirectory' => '/var/www/abc/data',
  'dbtype' => 'mysql',
  'version' => '31.0.13.1',
  'overwrite.cli.url' => 'https://a.b.c',

Apps

The output of occ app:list (if possible).

Tips for increasing the likelihood of a response

  • Use the preformatted text formatting option in the editor for all log entries and configuration output.
  • If screenshots are useful, feel free to include them.
    • If possible, also include key error output in text form so it can be searched for.
  • Try to edit log output only minimally (if at all) so that it can be ran through analyzers / formatters by those trying to help you.

The tests try http as a last resort.

Please provide the actual output of occ config:list system. Also try doing a curl from your system back to itself via the URL.

sudo -u apache php occ config:list system

output

{
“system”: {
“instanceid”: “REMOVED SENSITIVE VALUE”,
“passwordsalt”: “REMOVED SENSITIVE VALUE”,
“secret”: “REMOVED SENSITIVE VALUE”,
“trusted_domains”: [
“a.b.c”
],
“datadirectory”: “REMOVED SENSITIVE VALUE”,
“dbtype”: “mysql”,
“version”: “31.0.13.1”,
“overwrite.cli.url”: “https://a.b.c”,
“dbname”: “REMOVED SENSITIVE VALUE”,
“dbhost”: “REMOVED SENSITIVE VALUE”,
“dbport”: “”,
“dbtableprefix”: “oc_”,
“mysql.utf8mb4”: true,
“dbuser”: “REMOVED SENSITIVE VALUE”,
“dbpassword”: “REMOVED SENSITIVE VALUE”,
“installed”: true,
“maintenance”: false,
“log_type”: “file”,
“logfile”: “/var/log/nextcloud/nextcloud.log”,
“logmode”: 416,
“logfilemode”: 420,
“logdateformat”: “F d, Y H:i:s”,
“mail_domain”: “REMOVED SENSITIVE VALUE”,
“mail_smtpmode”: “smtp”,
“mail_sendmailmode”: “smtp”,
“mail_from_address”: “REMOVED SENSITIVE VALUE”,
“mail_smtphost”: “REMOVED SENSITIVE VALUE”,
“mail_smtpport”: “25”,
“memcache.local”: “\OC\Memcache\Redis”,
“filelocking.enabled”: “true”,
“memcache.distributed”: “\OC\Memcache\Redis”,
“memcache.locking”: “\OC\Memcache\Redis”,
“redis”: {
“host”: “***REMOVED SENSITIVE VALUE***”,
“port”: 6379,
“timeout”: 0,
“dbindex”: 0
},
“skeletondirectory”: “”,
“theme”: “”,
“loglevel”: 0,
“default_locale”: “et_EE”,
“default_language”: “et”,
“defaultapp”: “files”,
“updatechecker”: false,
“updater.release.channel”: “stable”,
“proxy”: “http:\/\/172.24.152.10:3128”,
“twofactor_enforced”: “false”,
“twofactor_enforced_groups”: ,
“twofactor_enforced_excluded_groups”: ,
“app_install_overwrite”: [
“occweb”
],
“allow_user_to_change_display_name”: false,
“default_phone_region”: “EE”,
“enable_previews”: false,
“htaccess.RewriteBase”: “\/”
}

}

sudo -u apache curl -v can successfully make https connections to the address in trusted_domains, overwrite.cli.url and sudo -u apache curl -v -k https://localhost

You have Nextcloud configured to use an outbound proxy.

Can your local curl test also pass when used via your outbound proxy?