[Support] Linuxserver.io - Nextcloud

[alturismo]

1 hour ago, JoergH said:

and my protocoll starting Nextcloud

 

may try removing those 2 entries

 

  'overwritehost' => 'nextcloud.xxx.info',
  'overwriteprotocol' => 'https',

 

shouldnt be needed as over...url is given already, here from mine

 

[Geck0]

2 hours ago, JoergH said:

Thank you! Yes, it is. I can't access it from anywhere and my clients can't access the files neither.

 

Could you please specify which log you mean?

There are so many: Nextcloud.log (81 MB), nginx/error.log, nginx/access.log, ssl, etc.

 

Here is my php.config

 

<?php
$CONFIG = array (
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'datadirectory' => '/data',
  'instanceid' => 'ocigxr2ap7z6',
  'passwordsalt' => 'MrjMPWDDediMvzjHzDv78RxfbUd/rj',
  'secret' => 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx',
  'trusted_domains' => 
  array (
    0 => '192.168.178.66:444',
    1 => 'nextcloud.xxx.info',
  ),
  'trusted_proxies' => 
  array (
    0 => 'swag',
  ),
  'default_phone_region' => 'DE',
  'dbtype' => 'mysql',
  'version' => '29.0.7.1',
  'overwrite.cli.url' => 'https://nextcloud.xxx.info/',
  'overwritehost' => 'nextcloud.xxx.info',
  'overwriteprotocol' => 'https',
  'dbname' => 'nextcloud',
  'dbhost' => '192.168.178.66:3306',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => 'nextcloud',
  'dbpassword' => 'xxxxx',
  'installed' => true,
  'loglevel' => 0,
  'maintenance' => false,
  'filelocking.enabled' => 'true',
  'memcache.locking' => '\\OC\\Memcache\\APCu',
  'mail_from_address' => 'xxx',
  'mail_smtpmode' => 'smtp',
  'mail_sendmailmode' => 'smtp',
  'mail_domain' => 'xxx.de',
  'mail_smtphost' => 'mail.xxx.de',
  'mail_smtpport' => '587',
  'mail_smtpauth' => 1,
  'mail_smtpname' => 'xxx',
  'mail_smtppassword' => 'xxxxx',
  'upgrade.disable-web' => true,
);

 

and my protocoll starting Nextcloud

 

 

Nextcloud protocol.txt 4.38 kB · 2 downloads

Config file looks good. I note your trustef proxy is just "swag".

 

Was this entry the same before or have you changed it recently?

 

Have you tried using the dedicated ip address of your swag server?

 

You don't need to specify the port 444 in trusted domains. This should be handled by your reverse proxy.

 

Ideally, your should let the proxy handle https between the client and the proxy. Between proxy and server should be http. If you specify 444 as your https port, its likely thst this is the problem. Also depends whats in your local nginx, if thats misconfigured for https, it could be another reason. Could also be the reason why you can't access locally.

 

Change this first and if still issues then:

 

Attach the logs, Nextcloud.log and error.log

Edited 20 hours ago by Geck0

[Greygoose]

my nexcloud just stopped working...  Ive searched and im a little lost, is it reddis causing it, im unsure how to locate the issue.

 

[JoergH]

7 hours ago, alturismo said:

may try removing those 2 entries

 

  'overwritehost' => 'nextcloud.xxx.info',
  'overwriteprotocol' => 'https',

 

shouldnt be needed as over...url is given already, here from mine

 

Thank you! That helped so far, that I can access the browser login page now locally again....

 

I still can't access it from somewhere else...

[alturismo]

12 minutes ago, JoergH said:

 

I still can't access it from somewhere else...

may try reverting all other changes ... 

[JoergH]

13 minutes ago, alturismo said:

may try reverting all other changes ... 

If I would know...I used the new config files instead of the ones I used before. I checked if I can see any differences. Once I couldn't find any, I overwrote the old config file. I used to have these two lines active before and it worked but the updates obviously changed that...

 

Maybe it is some nginx configuration issue? Unfortunately I do not really understand how all this works in detail and am staggering in the mist a little...

I overwrote the nginx config and autehlia config as far as I remember....

[JoergH]

8 hours ago, Geck0 said:

Config file looks good. I note your trustef proxy is just "swag".

 

Was this entry the same before or have you changed it recently?

 

Have you tried using the dedicated ip address of your swag server?

 

You don't need to specify the port 444 in trusted domains. This should be handled by your reverse proxy.

 

Ideally, your should let the proxy handle https between the client and the proxy. Between proxy and server should be http. If you specify 444 as your https port, its likely thst this is the problem. Also depends whats in your local nginx, if thats misconfigured for https, it could be another reason. Could also be the reason why you can't access locally.

 

Change this first and if still issues then:

 

Attach the logs, Nextcloud.log and error.log

I did not change the trusted proxy. It was swag before. I tried the dedicated IP but it won't help.

Took out the ":444"

Nextcloud.log is 81 MB...do you still want it?

error.log is empty.

[JoergH]

I found out something now.

 

In nginx error.log it shows that he adds the port twice...

 

2024/09/20 20:15:29 [error] 872#872: *61 invalid port in upstream "192.168.178.66:444:444", client: 2.138.145.170, server: nextcloud.*, request: >

 

How can I correct this?

[Geck0]

3 hours ago, JoergH said:

I found out something now.

 

In nginx error.log it shows that he adds the port twice...

 

2024/09/20 20:15:29 [error] 872#872: *61 invalid port in upstream "192.168.178.66:444:444", client: 2.138.145.170, server: nextcloud.*, request: >

 

How can I correct this?

Yeah, I had a feeling it was a port issue. 

The other changes you made allowed you to access NC within your network, but they're not the cause. 

This looks like a reverse proxy error message, telling you that your server config for nextcloud is incorrect.

 

You've specified the port twice in swag. I don't use SWAG, however this won't be difficult to find. I'm guessing you've set the port correctly in one field and where you've specified the upstream client you've specified the server with the port, when only the address is needed. You'll need to find that entry and remove the port from the upstream server.

 

Unless this is an old error message and it relates to the :444 setting you removed in config.php, but I doubt it. 

You're not clear whether you're looking at nginx.error in Swag or in Nextcloud docker. I'm assuming SWAG because this would be the same error I would expect if I made the same mistake in Opnsense docker for nginx reverse proxy.

 

I would look in both nginx configuration files. In swag and in NC container. But I'm guessing SWAG, based on what you've written. If you haven't touched SWAG, then it's the docker's nginx file.

 

 

Edited 7 hours ago by Geck0

[Geck0]

10 hours ago, Greygoose said:

my nexcloud just stopped working...  Ive searched and im a little lost, is it reddis causing it, im unsure how to locate the issue.

 

Does the NC docker run at all?

Is the Redis docker running?

The information out is only as good as what goes in. Ie. You'll need to elaborate.

 

Have you changed anything recently? Ie. Upgraded, changed config files, nginx or reverse proxy? 

 

 

Edited 3 hours ago by Geck0