NextCloudPi, Internal Server Error, external HD

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:

example

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

longer
example
here

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): current
Operating system and version (eg, Ubuntu 20.04): Debian Buster
Apache or nginx version (eg, Apache 2.4.25): dont know
PHP version (eg, 7.4): 7.3.31

The issue you are facing:
Internal Server Error when accessing WebGUI
I ran nextcloudpi for a few weeks and all was well. I added a HDD to the raspberry pi, formatted it with btfrs as in the documentation. All fine. I ssh into the pi and saw the hdd was mounted. I went to the ncp gui and followed the doc to move the dB and files to the hdd. I got an error. From the top of my head it started with cannot unmount harddisk, then it seemed to continue with some actions and then it was over. Since then I cannot access NextCloud anymore. Internal Server Error.
I see on the hdd that some db files have been moved.
I have some basic unix skills but no NextCloud skills. How can proceed from here if I dont want to reinstall everything from scratch?

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

Steps to replicate it:

  1. Connect HDD
  2. Format HDD: no-format USB
  3. Enable automount: nc-automount
  4. Change datadir to new hdd drive: nc-datadir
  5. Migrate db to HDD with nc-database using the new datadir

The output of your Nextcloud log in Admin > Logging:

Logfile is empty

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


php
$CONFIG = array (
  'passwordsalt' => 'XXX',
  'secret' => 'XXX',
  'trusted_domains' => 
  array (
    0 => 'localhost',
    22 => 'nextcloudpi',
    11 => 'XXX',
    1 => '192.168.1.167',
    3 => 'nextcloudpi',
  ),
  'datadirectory' => '/var/www/nextcloud/data',
  'dbtype' => 'mysql',
  'version' => '21.0.4.1',
  'overwrite.cli.url' => 'https://nextcloudpi/',
  'dbname' => 'nextcloud',
  'dbhost' => 'localhost',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => 'ncadmin',
  'dbpassword' => 'XXX',
  'installed' => true,
  'instanceid' => 'ocpe8kxr2xem',
  'memcache.local' => '\\OC\\Memcache\\Redis',
  'memcache.locking' => '\\OC\\Memcache\\Redis',
  'redis' => 
  array (
    'host' => '/var/run/redis/redis.sock',
    'port' => 0,
    'timeout' => 0.0,
    'password' => 'XXX',
  ),
  'tempdirectory' => '/var/www/nextcloud/data/tmp',
  'mail_smtpmode' => 'smtp',
  'mail_smtpauthtype' => 'LOGIN',
  'preview_max_x' => '2048',
  'preview_max_y' => '2048',
  'jpeg_quality' => '60',
  'overwriteprotocol' => 'https',
  'trusted_proxies' => 
  array (
    11 => '127.0.0.1',
    12 => '::1',
    13 => 'nextcloudpi',
    14 => '',
  ),
  'mail_sendmailmode' => 'smtp',
  'maintenance' => true,
);

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

Syslog output:
Jan 26 09:51:22 nextcloudpi mysqld[3633]: 2022-01-26  9:51:22 0 [Note] /usr/sbin/mysqld (mysqld 10.3.31-MariaDB-0+deb10u1) starting as process 3633 ...
Jan 26 09:51:22 nextcloudpi mysqld[3633]: 2022-01-26  9:51:22 0 [Warning] Can't create test file /media/myCloudDrive/nextcloudpi.lower-test
Jan 26 09:51:23 nextcloudpi systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Jan 26 09:51:23 nextcloudpi systemd[1]: mariadb.service: Failed with result 'exit-code'.
Jan 26 09:51:23 nextcloudpi systemd[1]: Failed to start MariaDB 10.3.31 database server.
Jan 26 09:51:24 nextcloudpi bash[1437]: Cannot load Zend OPcache - it was already loaded
Jan 26 09:51:27 nextcloudpi bash[1437]: Cannot load Zend OPcache - it was already loaded
Jan 26 09:51:28 nextcloudpi systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Jan 26 09:51:28 nextcloudpi systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 2159.
Jan 26 09:51:28 nextcloudpi systemd[1]: Stopped MariaDB 10.3.31 database server.
Jan 26 09:51:28 nextcloudpi systemd[1]: Starting MariaDB 10.3.31 database server...
Jan 26 09:51:31 nextcloudpi bash[1437]: Cannot load Zend OPcache - it was already loaded
Jan 26 09:51:34 nextcloudpi bash[1437]: Cannot load Zend OPcache - it was already loaded
Jan 26 09:51:37 nextcloudpi bash[1437]: Cannot load Zend OPcache - it was already loaded
Jan 26 09:51:40 nextcloudpi bash[1437]: Cannot load Zend OPcache - it was already loaded

Error.log

[Tue Jan 25 16:48:06.515195 2022] [authz_host:error] [pid 8260:tid 547980370304] [client 192.168.1.136:63789] AH01753: access check of 'localhost' to / failed, reason: unable to get the remote host name
[Tue Jan 25 16:48:08.710471 2022] [authnz_external:error] [pid 8260:tid 547980370304] [client 192.168.1.136:63789] AuthExtern pwauth [/usr/sbin/pwauth]: Failed (1) for user ncp
[Tue Jan 25 16:48:08.710572 2022] [auth_basic:error] [pid 8260:tid 547980370304] [client 192.168.1.136:63789] AH01617: user ncp: authentication failure for "/": Password Mismatch
[Tue Jan 25 16:48:21.137169 2022] [authz_host:error] [pid 8260:tid 547980370304] [client 192.168.1.136:63791] AH01753: access check of 'localhost' to / failed, reason: unable to get the remote host name
[Tue Jan 25 16:48:21.208468 2022] [authz_host:error] [pid 8260:tid 547980370304] [client 192.168.1.136:63791] AH01753: access check of 'localhost' to / failed, reason: unable to get the remote host name
[Tue Jan 25 16:48:21.208992 2022] [authz_host:error] [pid 8260:tid 547980370304] [client 192.168.1.136:63791] AH01753: access check of 'localhost' to /index.php failed, reason: unable to get the remote host name
[Tue Jan 25 16:48:21.266460 2022] [authz_host:error] [pid 8260:tid 547980370304] [client 192.168.1.136:63791] AH01753: access check of 'localhost' to /index.php failed, reason: unable to get the remote host name
[Tue Jan 25 16:48:21.832164 2022] [authz_host:error] [pid 8260:tid 547980370304] [client 192.168.1.136:63791] AH01753: access check of 'localhost' to /js/minified.js failed, reason: unable to get the remote host name
[Tue Jan 25 16:48:21.833656 2022] [authz_host:error] [pid 8260:tid 547997172096] [client 192.168.1.136:63791] AH01753: access check of 'localhost' to /js/ncp.js failed, reason: unable to get the remote host name
[Tue Jan 25 16:48:21.835324 2022] [authz_host:error] [pid 8260:tid 547988771200] [client 192.168.1.136:63791] AH01753: access check of 'localhost' to /css/ncp.css failed, reason: unable to get the remote host name
[Tue Jan 25 16:48:21.835424 2022] [authz_host:error] [pid 8260:tid 548005572992] [client 192.168.1.136:63791] AH01753: access check of 'localhost' to /img/ncp-logo.svg failed, reason: unable to get the remote host name
[Tue Jan 25 16:48:21.836907 2022] [authz_host:error] [pid 8260:tid 548013973888] [client 192.168.1.136:63791] AH01753: access check of 'localhost' to /img/loading-small.gif failed, reason: unable to get the remote host name
[Tue Jan 25 16:48:21.918539 2022] [authz_host:error] [pid 8260:tid 547988771200] [client 192.168.1.136:63791] AH01753: access check of 'localhost' to /ncp-launcher.php failed, reason: unable to get the remote host name
[Tue Jan 25 16:48:21.918937 2022] [authz_host:error] [pid 8260:tid 548013973888] [client 192.168.1.136:63791] AH01753: access check of 'localhost' to /ncp-output.php failed, reason: unable to get the remote host name
[Tue Jan 25 16:48:25.320286 2022] [authz_host:error] [pid 8260:tid 547988771200] [client 192.168.1.136:63791] AH01753: access check of 'localhost' to /ncp-launcher.php failed, reason: unable to get the remote host name
[Tue Jan 25 16:48:25.347380 2022] [authz_host:error] [pid 8260:tid 547988771200] [client 192.168.1.136:63791] AH01753: access check of 'localhost' to /ncp-launcher.php failed, reason: unable to get the remote host name
[Tue Jan 25 16:52:34.276789 2022] [authz_host:error] [pid 4140:tid 547980370304] [client 192.168.1.136:63816] AH01753: access check of 'localhost' to /ncp-output.php failed, reason: unable to get the remote host name
[Tue Jan 25 16:52:56.665139 2022] [authz_host:error] [pid 4140:tid 548131504512] [client 192.168.1.136:63816] AH01753: access check of 'localhost' to /ncp-launcher.php failed, reason: unable to get the remote host name
[Tue Jan 25 16:53:06.110442 2022] [authz_host:error] [pid 4140:tid 548131504512] [client 192.168.1.136:63816] AH01753: access check of 'localhost' to /ncp-launcher.php failed, reason: unable to get the remote host name

What can I do, being a non techie?

I have no idea about NCP but if you are configring the Snappy one, you will have to execute a command to allow nextcloud to access “removeable media”, if you wish to allow it to r/w on an external drive. There might be something similar in NCP

Ok, maybe I can help. I had same problems but it was late and I did not copy all the links to solution. However I remember the following:

“Cannot load Zend OPcache” - I did a google search and found out there is a process (obviously) blocking the maintanace mode. It seams to be a comon problem to nextcloud/ncp.

I had access to the admin page. I did an upgrade. I needed at least two times trying including reboot to let it run through smoothly. So be patient. After that I mounted the HDD, looked for the UUID and put it into fstab. Just google for mount and fstab and there will be several howto’s for the shell. In ubuntu there is also a gui-tool.

So I did “mount -a” afterwards and put into the admin page the path of the mount point including the name for the folder of data e.g. /media/ncpdata/data and gave it a shot.

It worked. I even did a backup, corrupted the installation and put the backup back in place to test. No problem.

Although I would recomend ncp not on top of a linux installation but using a single ncp installation or using docker.