No access to app store (fresh install via Web Installer / setup-nextcloud.php)

The Basics

  • Nextcloud Server version (e.g., 29.x.x):

  • Operating system and version (e.g., Ubuntu 24.04):

    • couldn't check
  • Web server and version (e.g, Apache 2.4.25):

    • couldn't check
  • Reverse proxy and version _(e.g. nginx 1.27.2)

    • none
  • PHP version (e.g, 8.3):

    • see logs, was updated from 8.2 to 8.5 or something
  • Is this the first time you’ve seen this error? (Yes / No):

    YES

  • When did this problem seem to first start?

    • 2026-10-17, but could be earlier
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)

    • netinstall on rented webspace
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)

    • NO

Summary of the issue you are facing:

I wanted to update my nextcloud instance, and instead of updating I did a clean reinstall via setup-nextcloud.php, pointing to clean mySQL database as usual (I do this regularly). But after installation, I get the following error “No access to app store” during the recommendation page after installation.

When afterwards manually clicking on “Apps”, and being directed to URL Login – Nextcloud, I get an internal server error (500).

What did I do until now?

  • I downloaded the newest Web Installer from nextcloud.com today (2026-10-19), and diffed it with my available file: binary same.

  • I checked the logs, see attachment

  • I already did a reinstall on Saturday, 2026-10-17, before the new Nextcloud versions dropped (see announcement today “Nextcloud Hub 26 Winter (version 33.0.10) Nextcloud Hub 26 Spring (version 34.0.5) Nextcloud Hub 26 Summer (version 35.0.2)”)

The only difference that I could check is to use an old PHP version, since I regularly use the newer versions when the old ones are almost deprecated.

I am installing on a webserver (worked the last 2 years, so if nextcloud did not suddenly get bloated since the last reinstall a few weeks ago, this should not be the issue).
This means I only have restricted debugging options, and if it does no longer work out-of-the box (at least access to the App-store with some basics such as calendar-app is needed), I will have to change to a different provider, such as Owncloud or Opencloud or similar..

Steps to replicate it (hint: details matter!):

  1. drop setup-nextcloud.php in your webspace

  2. access via URL

  3. install nextcloud

  4. a) error occurs on Welcome screen, instead of selection of “app proposals”

  5. change URL to go to the nextcloud instance

  6. click on “Apps”

  7. b) error occurs, this time “internal server error (500)”

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.

{"reqId":"HZ3YRBHfJT3aGnLxOHWj","level":2,"time":"2026-10-19T17:37:23+00:00","remoteAddr":"2001:16b8:23d5:5b00:12b2:fd2b:4fac:ff6a","user":"--","app":"PHP","method":"POST","url":"/","scriptName":"/index.php","message":"Undefined array key \"passwordsalt\" at /var/www/vhosts/xxxxxxx/lib/private/Setup.php#376","userAgent":"Mozilla/5.0 (X11; Linux x86_64; rv:152.0) Gecko/20100101 Firefox/152.0","version":"","data":{"app":"PHP"}}
{"reqId":"HZ3YRBHfJT3aGnLxOHWj","level":2,"time":"2026-10-19T17:37:23+00:00","remoteAddr":"2001:16b8:23d5:5b00:12b2:fd2b:4fac:ff6a","user":"--","app":"PHP","method":"POST","url":"/","scriptName":"/index.php","message":"Undefined array key \"secret\" at /var/www/vhosts/xxxxxxxx/lib/private/Setup.php#377","userAgent":"Mozilla/5.0 (X11; Linux x86_64; rv:152.0) Gecko/20100101 Firefox/152.0","version":"","data":{"app":"PHP"}}

Web server / Reverse Proxy

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

no changes

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!):

<?php

/*
 * WARNING
 *
 * This file gets modified by automatic processes and all lines that are not
 * active code (ie. comments) are lost during that process.
 *
 * If you want to document things with comments or use constants add your settings
 * in a '<NAME>.config.php' file which will be included and rendered into this file.
 *
 * Example:
 *   <?php
 *   $CONFIG = [];
 *
 * See also: https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/config_sample_php_parameters.html#multiple-merged-configuration-files
 */
$CONFIG = array (
  'instanceid' => 'xxxxxx',
  'passwordsalt' => 'xxxxxxxx',
  'secret' => 'xxxxxxxxx',
  'trusted_domains' => 
  array (
    0 => 'mydomain.de',
  ),
  'datadirectory' => '/var/www/vhosts/xxxxxxx/data',
  'dbtype' => 'mysql',
  'version' => '35.0.2.2',
  'overwrite.cli.url' => 'https://mydomain.de',
  'dbname' => 'foo',
  'dbhost' => 'xxxxxx',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => 'xxxxxx',
  'dbpassword' => 'xxxxxxx',
  'installed' => true,
);

The two log lines you posted are only notices from the setup request itself, they don’t show the 500. Open the Apps page once more, then copy the newest entry from nextcloud.log in your data directory. That one should name the real error. One likely candidate on rented webspace: the app store needs outgoing https from your server. The Nextcloud admin manual (Hardening and security guidance, Connections to remote servers) lists the systems it must reach, including the app store and GitHub for app downloads. If your host blocks outbound requests, the store check fails. PHP 8.5 is fine by the way, the Nextcloud 35 system requirements list it as supported.
Partly written with AI assistance.

Ok,
these are the additional log lines from nextcloud.log:
{“reqId”:“Mb2Bvzy9MxxXORDquPpe”,“level”:2,“time”:“2026-10-20T01:27:00+00:00”,“remoteAddr”:“167.71.38.118”,“user”:“–”,“app”:“no app in context”,“method”:“GET”,“url”:“/”,“scriptName”:“/index.php”,“message”:“Generating the capabilities of the following apps took longer than 0.1 seconds: OCA\Circles\AppInfo\Capabilities (0.21s), OCA\Password_Policy\Capabilities (0.35s), OCA\Theming\Capabilities (0.44s)”,“userAgent”:“Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/153.0.0.0 Safari/537.36”,“version”:“35.0.2.2”,“data”:}
{“reqId”:“p1rRuuYfBSqLFzDorn9b”,“level”:3,“time”:“2026-10-20T08:44:41+00:00”,“remoteAddr”:“34.97.193.215”,“user”:“–”,“app”:“no app in context”,“method”:“GET”,“url”:“/”,“scriptName”:“/index.php”,“message”:“Generating the capabilities of the following apps took longer than 0.1 seconds: OCA\Circles\AppInfo\Capabilities (0.33s), OCA\Password_Policy\Capabilities (0.91s), OCA\Theming\Capabilities (0.74s)”,“userAgent”:“Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36”,“version”:“35.0.2.2”,“data”:}
{“reqId”:“WYdhOwOTXo0snYC1YNjf”,“level”:2,“time”:“2026-10-20T14:40:17+00:00”,“remoteAddr”:“34.97.193.215”,“user”:“–”,“app”:“no app in context”,“method”:“GET”,“url”:“/”,“scriptName”:“/index.php”,“message”:“Generating the capabilities of the following apps took longer than 0.1 seconds: OCA\Circles\AppInfo\Capabilities (0.19s), OCA\Password_Policy\Capabilities (0.46s), OCA\Theming\Capabilities (0.69s)”,“userAgent”:“Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36”,“version”:“35.0.2.2”,“data”:}

Timestamps are a bit off, probably due to non-configured timezone, so the default is used.

Since I did not change any firewall- or network-settings and as mentioned it worked the last 2 years, I don’t expect the address to be blocked by the hoster.

Anyway, I will take the server offline for now, until the PHP vulnerability is fixed, and then try again afterwards…
Thank you in advance for your support.

Those are still only capability/performance notices (level 2 and 3), not the failing request itself. Also check the time: your paste is from 20.10, so it may predate your last try. Easiest filter: open the Apps page once, then search nextcloud.log for fresh lines containing appstore or cURL. A blocked outbound connection typically shows there as a cURL error (7 = could not connect, 28 = timeout) at level 3 or 4. If nothing with appstore appears, that alone does not prove the request never left your server: log level, component filters or where the log is actually written can hide it. So check your log destination and level, and test outbound https from the server itself (for example curl https://apps.nextcloud.com). A connect error or timeout there would support the hoster-block idea. Partly written with AI assistance.