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

 

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 September 20, 20241 yr by Geck0

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

 

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...

12 minutes ago, JoergH said:

 

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

may try reverting all other changes ... 

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....

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.

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?

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 September 20, 20241 yr by 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 September 21, 20241 yr by Geck0

4 hours ago, Geck0 said:

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? 

 

 

 

Hey, thnaks for the help.

 

ok ive posted the docker run and the log from nextcloud which shows errors.

 

ive not touched anything to cause this to happen. Reddis running no issues on the docker run.

 

 

41 minutes ago, Greygoose said:

 

Hey, thnaks for the help.

 

ok ive posted the docker run and the log from nextcloud which shows errors.

 

ive not touched anything to cause this to happen. Reddis running no issues on the docker run.

 

 

The answers there in yellow. You're getting an access denied message for the database user specified for your nextcloud database.

 

Don't assign them as a local user, which I think is the problem. Create and assign the user like this: 

CREATE USER nextcloud@'%';

I think you've specified the user as a local account, so the database cannot receive remote access requests from Nextcloud on it. It doesn't make sense though that it just suddenly happened. Are you sure you haven't done some maintenance or recreated the account??

 

See link below, which should help you out (don't know what your experience is like).

MySQL account setup

 

There is also an issue with your nginx setup, with deprecated entries that will need fixing up, but that's not the biggest issue.

Hopefully, that's the main issue and you can resolve it this way. I could be wrong, but it seems pretty clear.

Edited September 21, 20241 yr by Geck0

10 hours ago, Geck0 said:

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

... 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.

 

 

Thanks! I found it now. The error log was from nextcloud but the setting I had to correct was in

/mnt/user/appdata/swag/nginx/proxy-confs/nextcloud.subdomain.conf

 

The upstream app definition included the port..probably it took it from the nextcloud config

 

Everything works again as before. Thank you for your help!

Another question:

 

I managed to delete some of the warnings inside Nextcloud but where to I find the apache config to correct these:

 

Quote

Einige Header sind in deiner Instanz nicht richtig eingestellt - Der HTTP-Header `X-Content-Type-Options` ist nicht auf `nosniff` gesetzt. Dies stellt ein potenzielles Sicherheits- oder Datenschutzrisiko dar und es wird empfohlen, diese Einstellung zu ändern. - Der HTTP-Header `X-Frame-Options` ist nicht auf `sameorigin` gesetzt. Dies stellt ein potenzielles Sicherheits- oder Datenschutzrisiko dar und es wird empfohlen, diese Einstellung zu ändern. - Der HTTP-Header `X-XSS-Protection` enthält nicht `1; mode=block`. Dies stellt ein potenzielles Sicherheits- oder Datenschutzrisiko dar und es wird empfohlen, diese Einstellung zu ändern. - Der HTTP-Header `Referrer-Policy` ist nicht auf "no-referrer", "no-referrer-when-downgrade", "strict-origin", "strict-origin-when-cross-origin" oder "same-origin" gesetzt. Dadurch können Verweisinformationen preisgegeben werden. Siehe die W3C Recommendation. - Der `Strict-Transport-Security`-HTTP-Header ist nicht gesetzt (er sollte mindestens `15552000` Sekunden betragen). Für erhöhte Sicherheit wird empfohlen, HSTS zu aktivieren.

 

I set the first one inside the ssl.conf to "nosniff" but that didn't make a difference....

4 minutes ago, JoergH said:

Another question:

 

I managed to delete some of the warnings inside Nextcloud but where to I find the apache config to correct these:

 

 

I set the first one inside the ssl.conf to "nosniff" but that didn't make a difference....

If you are using linuxserver.io Nextcloud then its based on nginx, not Apache. If you do have Apache then you would set this in .htaccess (I think, its been a while since I looked at an Apache server).

You would normally set these in 

/mnt/user/appdata/nextcloud/nginx/site-confs/nginx.conf
/mnt/user/appdata/nextcloud/nginx/site-confs/default.conf  --> Normally in this file

 

My reverse proxy normally handles most of the settings you're asking about, which is also nginx.

Here is an excerpt from default.conf in nextcloud, you can see most of the settings there,but I would set these in SWAG. I've actually got them set in both proxy and in Nextcloud, which shouldn't be neccesary.

 

Don't forget to post your resolution, it helps others. 

 

 # Enable gzip but do not remove ETag headers
    gzip on;
    gzip_vary on;
    gzip_comp_level 4;
    gzip_min_length 256;
    gzip_proxied expired no-cache no-store private no_last_modified no_etag auth;
    gzip_types application/atom+xml application/javascript application/json application/ld+json application/manifest>

    # HTTP response headers borrowed from Nextcloud `.htaccess`
    add_header Referrer-Policy                      "no-referrer"   always;
    add_header X-Content-Type-Options               "nosniff"       always;
    add_header X-Download-Options                   "noopen"        always;
    add_header X-Frame-Options                      "SAMEORIGIN"    always;
    add_header X-Permitted-Cross-Domain-Policies    "none"          always;
    add_header X-Robots-Tag                         "noindex, nofollow"          always;
    add_header X-XSS-Protection                     "1; mode=block" always;

    # Remove X-Powered-By, which is an information leak
    fastcgi_hide_header X-Powered-By;

    root /app/www/public;

 

Thank you for the explanation, @Geck0!

I will do so.

 

EDIT: Just checked, that the settings are all active, so this is just not recognized by Nextcloud, it seems.

 

 

Hopefully my final problem with this now:

 

After doing the asked occ maintenance my Users disappeared from the list. I can see 7 Users in the group overview on the left side but they don't show with names etc. on the right...

 

How can I recover them?

 

 

Edited September 21, 20241 yr by JoergH

9 minutes ago, JoergH said:

Thank you for the explanation, @Geck0!

I will do so.

 

EDIT: Just checked, that the settings are all active, so this is just not recognized by Nextcloud, it seems.

 

 

Hopefully my final problem with this now:

 

After doing the asked occ maintenance my Users disappeared from the list. I can see 7 Users in the group overview on the left side but they don't show with names etc. on the right...

 

How can I recover them?

 

 

I've been dealing with you and another member, so I can't remember everything thats been done.

You can't lose users doing occ maintenance, or rather, its highly unlikely. 

 

Did you upgrade to the latest version today? It may be a cache issue. I've experienced a similar issue with icons disappearing after an upgrade. I had to clear my cache and restart the docker. 

 

Try that first.

 

Have you asked any of the users if they have access??

 

11 minutes ago, Geck0 said:

I've been dealing with you and another member, so I can't remember everything thats been done.

You can't lose users doing occ maintenance, or rather, its highly unlikely. 

 

Did you upgrade to the latest version today? It may be a cache issue. I've experienced a similar issue with icons disappearing after an upgrade. I had to clear my cache and restart the docker. 

 

Try that first.

 

Have you asked any of the users if they have access??

 

Thank you, again!

 

I closed the tab, reopened Nextcloud, logged in and here they were again. Exactely, I did do an update, just today.

Just now, JoergH said:

Thank you, again!

 

I closed the tab, reopened Nextcloud, logged in and here they were again. Exactely, I did do an update, just today.

No worries, happy to help. I've been through similar headaches.  😅👍

3 hours ago, Geck0 said:

The answers there in yellow. You're getting an access denied message for the database user specified for your nextcloud database.

 

Don't assign them as a local user, which I think is the problem. Create and assign the user like this: 

CREATE USER nextcloud@'%';

I think you've specified the user as a local account, so the database cannot receive remote access requests from Nextcloud on it. It doesn't make sense though that it just suddenly happened. Are you sure you haven't done some maintenance or recreated the account??

 

See link below, which should help you out (don't know what your experience is like).

MySQL account setup

 

There is also an issue with your nginx setup, with deprecated entries that will need fixing up, but that's not the biggest issue.

Hopefully, that's the main issue and you can resolve it this way. I could be wrong, but it seems pretty clear.

Hi,

 

I have no idea why this has happened, im trying to restore MariDB from a backup.

 

 

12 minutes ago, Greygoose said:

Hi,

 

I have no idea why this has happened, im trying to restore MariDB from a backup.

 

 

If you don't know, then it's likely an auto upgrade. I always set my NC and Maria to labels, to avoid surprises when they auto upgrade ahd break.

 

You shouldn't have to restore a DB backup, just create a new user and assign it to the DB. Update your config.php with the new user account.

 

If you're going to restore;

 

If you've done a recent upgrade of NC, I would recommend rolling back NC and the database together. 

 

 

 

 

Has anyone managed to get nextloud working with swag using a subfolder instead of subdomain? ie. my.domain.com/nextcloud?

 

I used to use this with this docker back in the day and it worked perfectly but with the change a year of 2 ago I've never been able to get it working.

10 hours ago, allanp81 said:

Has anyone managed to get nextloud working with swag using a subfolder instead of subdomain? ie. my.domain.com/nextcloud?

 

I used to use this with this docker back in the day and it worked perfectly but with the change a year of 2 ago I've never been able to get it working.

Post your config.php from Nextcloud and default.conf from its nginx config.

Hi all, I just updated to NC30 and had the following issue, which I (hope to) have already resolved and would like to provide a little information for others like me that are not too deep into the background of how everything runs "under the hood":

1st of all- whats the problem:

Did get the above error message every 10 minutes.

 

The problem seems to already be fixed in 30.0.1(?) and there is a patch for it

https://github.com/nextcloud/server/issues/47275

https://help.nextcloud.com/t/error-after-upgrading-to-30-0-driver-exception/203947/13

 

I did get the updated file

https://github.com/nextcloud/server/blob/2f2394cfa995bba08cdc9f1f945875a437110a9e/apps/dav/lib/CalDAV/Reminder/Backend.php

and had to figure out where in unraid / docker it is.

 

 

It includes only 2 changes

 

So I did change my local file, restarted NC and do not have errors showing in my Log for the last 22minutes, which should have included 2 more already, if the error would not have been solved.

 

Hope it does help somebody else

 

 

P.S. Also disabled the Usage-Survey app due to some other errors- but not sure on that one.

5 hours ago, dreadu said:

Hi all, I just updated to NC30 and had the following issue, which I (hope to) have already resolved and would like to provide a little information for others like me that are not too deep into the background of how everything runs "under the hood":

1st of all- whats the problem:

Did get the above error message every 10 minutes.

 

The problem seems to already be fixed in 30.0.1(?) and there is a patch for it

https://github.com/nextcloud/server/issues/47275

https://help.nextcloud.com/t/error-after-upgrading-to-30-0-driver-exception/203947/13

 

I did get the updated file

https://github.com/nextcloud/server/blob/2f2394cfa995bba08cdc9f1f945875a437110a9e/apps/dav/lib/CalDAV/Reminder/Backend.php

and had to figure out where in unraid / docker it is.

 

 

It includes only 2 changes

 

So I did change my local file, restarted NC and do not have errors showing in my Log for the last 22minutes, which should have included 2 more already, if the error would not have been solved.

 

Hope it does help somebody else

 

 

P.S. Also disabled the Usage-Survey app due to some other errors- but not sure on that one.

 

I still think its early days to upgrade to NC30. I normally wait for bug fixes like this to be sorted before upgrading, so  I don't have to patch. Its issues like this that should be caught in early RC versions. I'll likely not upgrade until at least 3 stable versions in. It also gives 3rd party app developers time to work on their upgrades. The alternative is that you start losing support (temporarily) of the apps you depend upon (I don't use AIO and have separate dockers). 

Edited September 29, 20241 yr by Geck0