Unable to access eternal storage or local files - Cant add files after upgrade

Support intro

Sorry to hear you’re facing problems :slightly_frowning_face:

help.nextcloud.com is for home/non-enterprise users. If you’re running a business, paid support can be accessed via portal.nextcloud.com 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, 20.0.5): 28.0.2
Operating system and version (eg, Ubuntu 20.04): 22.04.3
Apache or nginx version (eg, Apache 2.4.25): Apache 2.4.52-1
PHP version (eg, 7.4): 8.3

The issue you are facing:
Upgraded instance to 28.0.2. External mounts no longer work. Receive the error of " External mount error
There was an error with this external storage. Do you want to review this mount point config in the settings page?"
Additionally, i am unable to add any files in the files app. The Add option is grayed out.
Lastly all local files are not presented.

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

Steps to replicate it:

  1. All i did was upgrade from 28.0.1

The output of your Nextcloud log in Admin > Logging:


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

$CONFIG = array (
  'instanceid' => 'ocmbkxzjtpa4',
  'passwordsalt' => xxxxxxxxxsOL10rQnh92H6DCf2',
  'secret' => 'NWiHF9FxxxxxxxxxxxxxxxGYKepherQoNUwcb6bl1YzGNk',
  'trusted_domains' =>
  array (
    0 => '',
    1 => 'nc.xxxxxxxxxxxx',
  'trusted_proxies' =>
  array (
    0 => '',
  'datadirectory' => '/var/www/xxxxxxxxxxxxxxxxx.com/data',
  'dbtype' => 'mysql',
  'version' => '',
  'overwrite.cli.url' => '',
  'dbname' => 'nextcloud',
  'dbhost' => 'localhost',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => 'nextcloud',
  'dbpassword' => 'xxxxxxxxxxxxxxxxx',
  'installed' => true,
  'default_phone_region' => 'US',
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'filelocking.enabled' => true,
  'memcache.locking' => '\\OC\\Memcache\\Redis',
  'redis' =>
  array (
    'host' => '/var/run/redis/redis.sock',
    'port' => 0,
    'timeout' => 0.0,
  'mail_from_address' => 'admin',
  'mail_smtpmode' => 'smtp',
  'mail_sendmailmode' => 'smtp',
  'mail_domain' => 'xxxxxxxxxxxxx.com',
  'mail_smtphost' => 'smtp.zoho.com',
  'mail_smtpport' => '587',
  'mail_smtpauth' => 1,
  'mail_smtpname' => 'admin@xxxx.com',
  'mail_smtppassword' => 'xxxxxxxxxxxxxx',
  'maintenance' => false,
  'app_install_overwrite' =>
  array (
    0 => 'facerecognition',
  'loglevel' => 'debug',
  'logdateformat' => 'F d, Y H:i:s',
  'force_language' => 'en',
  'updater.secret' => '$2y$10$VCXE9wuez/YEMPYjlUmJj.lONGYNkqcpCNZ/hRPUnk.LZwTvI93jm',
  'theme' => '',
  'maintenance_window_start' => '1',

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



Output errors in nextcloud.log in /var/www/ or as admin user in top right menu, filtering for errors. Use a pastebin service if necessary.


digging into this a bit more i see that my files are still available in my /data/userID/ directory. So nothing is wiped BUT the nextcloud Files app is not displaying anything and i cant access external storage so this seems limited to the application itself.
nextcloud logs show nothing other than my updater logs.

I believe you’re the reporter in #43302[1].

Just summarizing two things here for anyone running across this thread:

  • logging configuration invalid
  • subsequent 500 error indicates your Redis server is offline

[1] https://github.com/nextcloud/server/issues/43302

Would need to add a few points here to clarify and align this issue with others facing the same problem.

  1. My logging configuration in the config.php file was incorrect. Had it been correct I might have spotted the issue immediately
  2. Redis was working fine for a while prior to the upgrade. No OS level changes have been done. The fix was to reinstall Redis using the same config file.
  3. Others have reported the same symptoms as I have although the underlying cause may be different. Reports on GitHub and Reddit do point to this being a quality issue with the update so at this time I would advise not to upgrade