On 4/10/2021 at 3:10 PM, bastl said:

HTTP Strict Transport Security (HSTS) is a web security policy mechanism that helps to protect websites against man-in-the-middle attacks such as protocol downgrade attacks[1] and cookie hijacking. It allows web servers to declare that web browsers (or other complying user agents) should automatically interact with it using only HTTPS connections, which provide Transport Layer Security (TLS/SSL), unlike the insecure HTTP used alone. HSTS is an IETF standards track protocol and is specified in RFC 6797.

Thanks for explaining about HSTS! After it was enabled, my app also started getting the 403 error because HSTS forces all traffic to go through HTTPS only. Some of my internal service calls were still using HTTP, which caused them to fail. Once I enabled the “Use HTTPS for internal communications” setting, all calls switched to HTTPS, and the issue got resolved. This ensures secure communication and full compliance with HSTS. I hope it helps!

22 hours ago, Geck0 said:

Edit the container, select "Advanced View" on the top right hand side, scroll down to "privileged" and turn it off with the slider button.

I saw that setting. Will that Collabora container work with it turned off?

I gave the L4stIdi0t template a try. Things went completely wonky when I added the CNAME for Collabora in my registrars DNS setting for my domain. Took me all morning to get SWAG and Nextcloud working again just from that one little change. Not even sure what fixed it other than perhaps a DNS propagation of changes.

Nextcloud seems like a delicate house of cards. Again, I think I'll leave well enough alone.

I got it!

It was a little weird here and there, but I now have editing capabilities in my Nextcloud instance. Woohoo!

Here's what I did:

1. Installed Collabora using the template from L4stIdi0t. I changed the container name to collabora and turned off privileged mode. Tested that I was able to access the container by using the WebUI link for the container.

2. Went into SWAG's appdata/ and removed .sample from the file swag/nginx/proxy-confs/collabora.subdomain.conf.sample

3. At this point, SWAG revokes certs and has a problem connecting back to the standalone server on port 80 to confirm the CA cert. More on this in a bit.

4. Added the CNAME to my domain's DNS. Used TTL=30 minutes so I waited at least this amount of time for it to propagate. Had to wait a little longer but confirmed CNAME was ready by going to https://toolbox.googleapps.com/apps/dig/ to confirm it. At this point going to collabora.mydomain.com gives an OK

5. So now onto getting SWAG to refresh certs. I had to edit the config.php in Nextcloud to remove the "s" for 'overwrite.cli.url' and 'overwriteprotocol'. This made SWAG work again but I don't know why. I then put things back to the way they were originally.

6. With new certs, I was then able to access Nextcloud again. I added the "Nextcloud Office" plugin. I entered the URL for my collabora instance(collabora.mydomain.com) in the "Use your own server".

And it worked!

I do get a warning about WOPI. I'm not sure what to add to that list. I tried the real IP of the nextcloud and collabora containers and still got an error. I have Collabora turned off for now until I can figure out this WOPI business. I think this ties it down so only Nextcloud can access the internet facing Collabora container.

Can someone point me in the right direction on the plugin's WOPI setting?

1 hour ago, nraygun said:

I got it!

It was a little weird here and there, but I now have editing capabilities in my Nextcloud instance. Woohoo!

Here's what I did:

1. Installed Collabora using the template from L4stIdi0t. I changed the container name to collabora and turned off privileged mode. Tested that I was able to access the container by using the WebUI link for the container.

2. Went into SWAG's appdata/ and removed .sample from the file swag/nginx/proxy-confs/collabora.subdomain.conf.sample

3. At this point, SWAG revokes certs and has a problem connecting back to the standalone server on port 80 to confirm the CA cert. More on this in a bit.

4. Added the CNAME to my domain's DNS. Used TTL=30 minutes so I waited at least this amount of time for it to propagate. Had to wait a little longer but confirmed CNAME was ready by going to https://toolbox.googleapps.com/apps/dig/ to confirm it. At this point going to collabora.mydomain.com gives an OK

5. So now onto getting SWAG to refresh certs. I had to edit the config.php in Nextcloud to remove the "s" for 'overwrite.cli.url' and 'overwriteprotocol'. This made SWAG work again but I don't know why. I then put things back to the way they were originally.

6. With new certs, I was then able to access Nextcloud again. I added the "Nextcloud Office" plugin. I entered the URL for my collabora instance(collabora.mydomain.com) in the "Use your own server".

And it worked!

I do get a warning about WOPI. I'm not sure what to add to that list. I tried the real IP of the nextcloud and collabora containers and still got an error. I have Collabora turned off for now until I can figure out this WOPI business. I think this ties it down so only Nextcloud can access the internet facing Collabora container.

Can someone point me in the right direction on the plugin's WOPI setting?

I posted an image on where it is, but it contained some info that shouldn't be public. Go to Admin / Settings / Office......Scroll down and you'll see the WOPI setting. The allow list should include the ip address of the collabora server, in my case its the unRaid server, as I haven't specified a separate address for the docker.

Not a security setting per se', but you could also create groups in Nextcloud, assign users that should be able to use Collabora into that group and then assign the group on the same page, using the "restrict usage to specific groups" option. I suggest you google Nextcloud Collabora setup, there are settings you can add for Collabora. Collabora has a specific page help page for Nextcloud integration.

Edited October 29, 2025Oct 29 by Geck0

I had found the WOPI area of the app and had said I tried things there so you didn't need to provide the breadcrumbs to get there. The online dox for Collabora are pretty bare bones in my opinion.
And to get to this point, yes, I've been Googling. Surely you recognized this or perhaps you're new to trying to help people.

However, I'll keep Googlin'.

Edited October 30, 2025Oct 30 by nraygun

Let's all get back to being nice to each other and respecting our forum rules, thanks.

I got it!

I had to add the container range, the server range, and the IP of that my ISP gives me to the WOPI setting in the configuration for the Nextcloud Office app.

I even tested taking entries out one at a time to confirm they are needed.

So, the WOPI values for my instance are:

172.18.0.0/24,192.168.0.100/24,ipaddrisp

where ipaddrisp is my IP from the ISP.

hi everyone after the last update i try to create new folder or new doc. the nextcloud return with these errors

On 11/1/2025 at 10:03 AM, Erik1erik1 said:

hi everyone after the last update i try to create new folder or new doc. the nextcloud return with these errors

I think I have the same issue, but I added a folder using the desktop client.

When I go on the webUI the folder was created but when I open it up it says unavailable.

Docker image ID = eff6bc263603, latest tag.

25 minutes ago, tonyuh said:

I think I have the same issue, but I added a folder using the desktop client.

When I go on the webUI the folder was created but when I open it up it says unavailable.

Docker image ID = eff6bc263603, latest tag.

Seems like it was caused by Client Push App, after I disable it from Admin Settings, everything works again. I guess there is misconfiguration within Client Push app for my install.

EDIT:

Fixed by running the Docker Safe New Perms on the nextcloud share. Now it works fine.

Any ideas why this thing all of a sudden decided it no longer likes the permissions on my data directory, which has worked fine for years and even immediately after the most recent upgrade (done 2-3 days ago)? It just randomly started some time between then and now, and nothing else has changed.

I can access and browse the data directory just fine. I can access the database just fine. The application even works on my devices. It's ONLY this web interface giving the error both locally and through public URL (using Swag proxy).

The link doesn't even take you to a valid URL so you just get forwarded to the main page of the documents, with no information on how to fix it.

Container settings;

Share permissions:

Edited November 14, 2025Nov 14 by carnivorebrah

I've seen quite a few posting about problems upgrading to v32.

Has anyone here upgraded without issue? I usually hold off upgrading to a major version until one or more minor versions have come out. That's now happened, but I'm hesitant to upgrade seeing some of the weird API errors and permission problems it seems to be causing.

Are there any success stories about that could make me feel safer in the upgrade?

Many thanks.

No problem here, but probably depends quite a bit on the apps/integrations you use.

5 minutes ago, Kilrah said:

No problem here, but probably depends quite a bit on the apps/integrations you use.

True.

Mine is just using the file syncing/sharing capabilities. I don't use it for calendar, contacts, docs, chat or video calls etc.

I might give the upgrade a go tomorrow.

Hello,

I want to solve this specific (php-) error from passman:

{
  "reqId": "ZU1i5UVHRM902ej4RGVq",
  "level": 3,
  "time": "2025-11-17T21:45:02+00:00",
  "remoteAddr": "",
  "user": "--",
  "app": "PHP",
  "method": "",
  "url": "--",
  "message": "OCA\\Passman\\Service\\CredentialRevisionService::getRevision(): Implicitly marking parameter $user_id as nullable is deprecated, the explicit nullable type must be used instead at /config/www/nextcloud/apps/passman/lib/Service/CredentialRevisionService.php#87",
  "userAgent": "--",
  "version": "32.0.1.2",
  "data": {
    "app": "PHP"
  },
  "id": "691b9811cb89b"
}

Can anybody lead me to a proper fix for that? Many thanks in advance!

edit, 19.11.2025: I've found this bug report: https://github.com/bcit-ci/CodeIgniter/issues/6302

But all the file locations are not available on my undraid-instance nor in the nextcloud docker.

Edited November 19, 2025Nov 19 by Chlorgas

On 11/17/2025 at 4:49 PM, jademonkee said:

I've seen quite a few posting about problems upgrading to v32.

Has anyone here upgraded without issue? I usually hold off upgrading to a major version until one or more minor versions have come out. That's now happened, but I'm hesitant to upgrade seeing some of the weird API errors and permission problems it seems to be causing.

Are there any success stories about that could make me feel safer in the upgrade?

Many thanks.

I waited for 32.0.1 with my upgrade from 31- but still encountered a log of problems. The notes app floods the log with warning if enabled.
Mail app (and others) randomly showed 404 when trying to use them. Phots has a problem with the widget breaking the dashboard. I was using "on this day" on the dashboard and had to remove it. Also "on this day" does not display anything when trying to use it in the app itself.
New had a few problems as well.

Tried a couple of things. Disablind, uninstalling and re-installing mail + news seems to have solved the 404 issues, but the photos widget and notes are still haveing issues

Next time, I'll wait for X.0.3 at least...

3 minutes ago, dreadu said:

I waited for 32.0.1 with my upgrade from 31- but still encountered a log of problems. The notes app floods the log with warning if enabled.
Mail app (and others) randomly showed 404 when trying to use them. Phots has a problem with the widget breaking the dashboard. I was using "on this day" on the dashboard and had to remove it. Also "on this day" does not display anything when trying to use it in the app itself.
New had a few problems as well.

Tried a couple of things. Disablind, uninstalling and re-installing mail + news seems to have solved the 404 issues, but the photos widget and notes are still haveing issues

Next time, I'll wait for X.0.3 at least...

Good to know, thanks.

I haven't yet upgraded, so might wait for a few more point releases before I do.

As a quick update:
Notes app got an update as well. At first glance it seems to work fine now.

Mail also got a few updates the last weeks and seems to be stable as well.

Only thing still not working is the photos app widget and "on this day".

As well as there are a few unnecessary errors that could be warnings or info, not not really an issue- except filling the logs.

GitHub

[Bug]: Logs filled with A non-numeric value encountered a...

⚠️ This issue respects the following points: ⚠️ This is a bug, not a question or a configuration/webserver/proxy issue. This issue is not already reported on Github OR Nextcloud Community Forum (I'...

GitHub

[Bug]: Make nullable explicit to silence STDERR message ·...

⚠️ This issue respects the following points: ⚠️ This is a bug, not a question or a configuration/webserver/proxy issue. This issue is not already reported on Github OR Nextcloud Community Forum (I'...

/edit

Update #2

With 32.0.3 photos app (esp. "on this day") also works again

Edited December 11, 2025Dec 11 by dreadu

Just updated Nextcloud and apparently managed to sneak in just in time to get hit with a bug bundled with it Update 32.0.4.

Following error in the logs:

Exception: Database error when running migration 33000Date20251209123503 for app core

Index "mounts_user_root_path_index" does not exist on table "oc_mounts".

Update failed

Maintenance mode is kept active

Documented here: https://github.com/nextcloud/server/issues/57572

The fix is apparently to adjust this file: /var/www/html/nextcloud/core/Migrations/Version33000Date20251209123503.php

My problem is, my version of Nextcloud doesn't have a core/Migrations directory, I'm not sure if its since the install has existed since 2023 or if its a specific Unraid Docker thing.

Ordinarily I'd restore from an AppData backup but guess who forgot to reinstall that a few weeks ago? (It was me)

Thanks!

8 hours ago, Low-Volt said:

Just updated Nextcloud and apparently managed to sneak in just in time to get hit with a bug bundled with it Update 32.0.4.

Following error in the logs:

Exception: Database error when running migration 33000Date20251209123503 for app core

Index "mounts_user_root_path_index" does not exist on table "oc_mounts".

Update failed

Maintenance mode is kept active

Documented here: https://github.com/nextcloud/server/issues/57572

The fix is apparently to adjust this file: /var/www/html/nextcloud/core/Migrations/Version33000Date20251209123503.php

My problem is, my version of Nextcloud doesn't have a core/Migrations directory, I'm not sure if its since the install has existed since 2023 or if its a specific Unraid Docker thing.

Ordinarily I'd restore from an AppData backup but guess who forgot to reinstall that a few weeks ago? (It was me)

Thanks!

I found it located at /app/www/public/core/Migrations/Version33000Date20251209123503.php

2 hours ago, Wilkie said:

I found it located at /app/www/public/core/Migrations/Version33000Date20251209123503.php

That's the one, thank you! In the interest of learning how'd you find it? I tried using cli 'find' but that didn't work.

Also for anyone impacted by this, you'll most likely have to run occ maintenance:mode --off after the successful update.

Is this a different install than the AIO container?

Yes.

Running Unraid Nextcloud Docker and Nginx with own Certificate of Authority and Self-signed certificates.

Finally have it working.

Lingering question that appears not to make a difference.

I placed the certificate and key in /mnt/dockers/appdata/Nextcloud/keys

But I see a ssl.conf where it seems to suggest to place them here:

/config/keys/

Are they even read by Nextcloud or even used at all?? There is no path or variable in the docker setup that even references these locations.

My nextcloud server has been having a lot of issues lately. My unraid server had all of its cores pegged to 100% from the nextcloud container and I saw this in the error.log file. What would be causing this and how can I get my server back to functioning properly?

[09-Feb-2026 10:22:25] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 89 total children

[09-Feb-2026 10:22:26] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 90 total children

[09-Feb-2026 10:22:27] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 91 total children

[09-Feb-2026 10:22:28] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 92 total children

[09-Feb-2026 10:22:29] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 93 total children

[09-Feb-2026 10:22:30] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 94 total children

[09-Feb-2026 10:22:31] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 95 total children

[09-Feb-2026 10:22:32] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 96 total children