Nextcloud version (eg, 20.0.5): 21.0.0.18
Operating system and version (eg, Ubuntu 20.04): Ubuntu Server 20.04.2
Apache or nginx version (eg, Apache 2.4.25): Unknown
PHP version (eg, 7.4): Unknown
The issue you are facing:
Is this the first time you’ve seen this error? (Y/N): Y
Steps to replicate it:
- Start the server
- Connect to it
The output of your Nextcloud log in Admin > Logging:
Unable to access Nextcloud at all
The output of your config.php file in /path/to/nextcloud
(make sure you remove any identifiable information!):
<?php
$CONFIG = array (
'htaccess.RewriteBase' => '/',
'memcache.local' => '\\OC\\Memcache\\APCu',
'apps_paths' =>
array (
0 =>
array (
'path' => '/var/www/html/apps',
'url' => '/apps',
'writable' => false,
),
1 =>
array (
'path' => '/var/www/html/custom_apps',
'url' => '/custom_apps',
'writable' => true,
),
),
'instanceid' => '[Removed],
'passwordsalt' => '[Removed]',
'secret' => '[Removed]',
'trusted_domains' =>
array (
0 => '10.0.0.84:8080',
1 => '[Removed]',
),
'datadirectory' => '/var/www/html/data',
'dbtype' => 'pgsql',
'version' => '21.0.0.18',
'overwrite.cli.url' => 'http://10.0.0.84:8080',
'dbname' => 'postgres',
'dbhost' => 'postgres',
'dbport' => '',
'dbtableprefix' => 'oc_',
'dbuser' => 'oc_cesium',
'dbpassword' => '[Removed]',
'installed' => true,
'mail_smtpmode' => 'smtp',
'mail_sendmailmode' => 'smtp',
'mail_from_address' => 'no-reply',
'mail_domain' => '[Removed]',
'mail_smtpauthtype' => 'LOGIN',
'mail_smtpauth' => 1,
'mail_smtphost' => '[Removed]',
'mail_smtpport' => '[Removed]',
'mail_smtpname' => '[Removed]',
'mail_smtppassword' => '[Removed]',
'updater.release.channel' => 'stable',
);
The output of your Apache/nginx/system log in /var/log/____
:
Log file does not exist
I know this is probably not very helpful, but I’m hoping the error I got could lead us to where the log files are located. I launched it for the first time and it worked for a few hours. I moved the server (a Raspberry Pi) to a different location and ran a script used to remove the old containers, start the new ones, and start my Argo tunnel.
In the screenshot I sent in the issue portion, that was all I could see. There was nothing on any type of error and it didn’t lead me onto any logs. Connecting via the Argo tunnel and the direct IP yield the same results.
One more thing to note is that I used this video to install it this morning. Everything should be the latest version of what ships with the docker image.