HTTP 500 when upgrading NC17.0.0 to NC18

Support intro

Sorry to hear you’re facing problems :slightly_frowning_face: is for home/non-enterprise users. If you’re running a business, paid support can be accessed via where we can ensure your business keeps running smoothly.

In order to help you as quickly as possible, before clicking Create Topic please provide as much of the below as you can. Feel free to use a pastebin service for logs, otherwise either indent short log examples with four spaces:


Or for longer, use three backticks above and below the code snippet:


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:

Nextcloud version (eg, 12.0.2): 18.0.0
Operating system and version (eg, Ubuntu 17.04): unknown
Apache or nginx version (eg, Apache 2.4.25): unknown
PHP version (eg, 7.1): 7.4

The issue you are facing:
After successful update, getting HTTP 500 error when trying to log in.
As this is offsite webhosting provider, I don’t have access to command line

Is this the first time you’ve seen this error? (Y/N):

Steps to replicate it:

  1. Update from NC17
  2. Set php_value memory_limit 256M in htaccess to get past Step 5
  3. Finish update, turn off maintenance and go to admin
  4. HTTP 500

The output of your Nextcloud log in Admin > Logging:

03T12:30:05+00:00","remoteAddr":"","user":"--","app":"PHP","method":"GET","url":"/ncloud/","message":"Declaration of OCA\\FilesAccessControl\\Operation::validateOperation($name, array $checks, $operation) must be compatible with OCP\\WorkflowEngine\\IOperation::validateOperation(string $name, array $checks, string $operation): void at /ncloud/apps/files_accesscontrol/lib/Operation.php#31","userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3850.0 Iron Safari/537.36","version":""}

The output of your config.php file in /path/to/nextcloud (make sure you remove any identifiable information!):

$CONFIG = array (
  'instanceid' => '',
  'passwordsalt' => '',
  'secret' => '',
  'trusted_domains' => 
  array (
    0 => '',
  'datadirectory' => '/ncloud/data',
  'dbtype' => 'mysql',
  'version' => '',
  'overwrite.cli.url' => '',
  'dbname' => '31001180_ncloud',
  'dbhost' => 'localhost',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => '31001180_ncloud',
  'dbpassword' => '',
  'installed' => true,
  'app_install_overwrite' => 
  array (
    0 => 'end_to_end_encryption',
  'maintenance' => false,
  'updater.secret' => '',
  '' => 'beta',
  'theme' => '',

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


could be the same as we had before in this forum (pls use searchfunction of the forum --> :mag: ahead of prosting)
@tflidd offered a possible solution

pls use searchfunction of the forum ahead of prosting

Did that. Cannot use command line because of what is posted above

r u allowed running cronjobs?
so you could enter all neccessary commands into a file and let it execute by a cronjob…

how about that one?

reinstall seems a easier solution, data were not encrypted so everything is backed up,
but with encrypted data, that would be quite a disaster (I assumed data were encrypted, with server side encryption turned on, but no)

well then… good luck

Just for the future:

  • I wouldn’t upgrade now to 18.0.0, just a bit before 18.0.1 is released (where probably a few things will be fixed). Either do it from the start (or better even test the beta versions in a test environment similar to your productive system)
  • Reinstallation is an option. However, there is a risk that the underlying issue will pop up again during the next upgrade.