blaine07

There was some way jc21 was telling them, on github, to enable a "debug" type mode that provided more logging but not sure if he was kicking it off with a ENV or what.

I couldn't confidently tell you it would change anything, but in your last pic my "NPM" fold is owned by "root": EDIT: what you did above with PGID and PUID appears to mimic mine.

In shares browsing to that folder in appdata who does it show “owns” it out of curiosity? In a sec I can upload a pic of what I’m talking about…

I did this, to see what existing PUID and PGID were: Then I set two ENV up in NPM container, "PUID" and "PGID" and set them to what above discovered that they HAD been and upgraded to 2.10.0. All is working fine/welll following these few steps.

What did you set PUID and PGID as?

When manually upgrading this is when I’ve had to fix owner and permissions in the process:

Look at who owns config folder and who had owned and what rights of the old one. Last few times I’ve upgraded Nextcloud I’ve had to change owner and permissions back to “what they were”. I could look at mine later and tell you if I needed. Never the les same thing. Upgraded would fail because when following manual upgrade instructions new folder permissions and owner weren’t correct.

Did you use PUID and PGID and what did you change them to with ENV?

@Tweak91

Unraid 6.11.4 uses PHP 7.4.33. To upgrade PHP you’ll need to figure out how/if you want to/can upgrade Unraid itself To get a newer PHP.

What version of unraid are you on

Thank you! Still curious as to if Nextcloud themselves can get it built in/working, too, though. Some more info - looks like it's been in the works for a long time. https://github.com/nextcloud/server/pull/23825

What problems might or cause for other sites I have hosted through this domain with Cloudflare? Will these be breaking changes to other services I host since I can't define "per subdomain"?

This: # 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 "none" always; add_header X-XSS-Protection "1; mode=block" always; It looks a update was pushed out by Linuxserver mere hours ago that updates this file again; I wonder what changes were this time. EDIT: changes pushed our hours ago turned the Robots tag stuff back to be correct for NC 26 it appears: https://github.com/linuxserver/docker-nextcloud/commit/c1568bac547f6f660849487ed7e443520417a1b7

How do I add it or? Reverse proxy or? all I could find: https://github.com/nextcloud/server/issues/22792

Interesting. The best I can get is a A but “permissions-policy” i’m missing. I wonder if permissions policy was fixed/added in 26 or?

Where did you run that test at?

Irony! I went through today and Updated the few files on run commands it said I had "out of date" and one of them was this file. When I updated it fussed and MADE ME change it to "NONE" to work; here we are, it already needs to be back on what it had just updated to LOL FARKLE Thank you! How is V26 of Nextcloud in general?

Unraid shows I am on version "2023.01.28" is that the latest released version? I feel like a lot of changes discussed above but is there a beta or something I am not privy to or am I in fact on "current" version?

Is this helpful? When I enable containers one by one what *exactly* am I looking for to confirm it’s the culprit? Just by starting container(s) I never see anything wonky?

I am so discombobulated...I am flustered. I can't tell if it's coming or going or what it's doing. Every-time I think I discover something I am wrong. What would you encourage my next steps to be?

Just a few ago it tried to lock up: Mar 7 06:19:31 Tower kernel: oom-kill:constraint=CONSTRAINT_MEMCG,nodemask=(null),cpuset=0c85bb041886edc37981442c550f8522b2687c54eddc7769fe20d345c7a32c92,mems_allowed=0-1,oom_memcg=/docker/0c85bb041886edc37981442c550f8522b2687c54eddc7769fe20d345c7a32c92,task_memcg=/docker/0c85bb041886edc37981442c550f8522b2687c54eddc7769fe20d345c7a32c92,task=nginx,pid=16299,uid=0 Mar 7 06:19:31 Tower kernel: Memory cgroup out of memory: Killed process 16299 (nginx) total-vm:271632kB, anon-rss:173940kB, file-rss:0kB, shmem-rss:112kB, UID:0 pgtables:424kB oom_score_adj:0

Well It was: Mar 6 21:36:36 Tower kernel: oom-kill:constraint=CONSTRAINT_MEMCG,nodemask=(null),cpuset=b7bf47074734f898f67616851b6c9c6128f182ef264006024be566416b2d07e1,mems_allowed=0-1,oom_memcg=/docker/b7bf47074734f898f67616851b6c9c6128f182ef264006024be566416b2d07e1,task_memcg=/docker/b7bf47074734f898f67616851b6c9c6128f182ef264006024be566416b2d07e1,task=nginx,pid=25095,uid=0 Mar 6 21:36:36 Tower kernel: Memory cgroup out of memory: Killed process 25095 (nginx) total-vm:274036kB, anon-rss:176240kB, file-rss:4kB, shmem-rss:516kB, UID:0 pgtables:412kB oom_score_adj:0 Mar 6 21:36:38 Tower kernel: oom_reaper: reaped process 25095 (nginx), now anon-rss:0kB, file-rss:0kB, shmem-rss:516kB Mar 6 21:44:06 Tower root: Fix Common Problems Version 2023.03.04 Mar 6 21:44:08 Tower root: Fix Common Problems: Warning: unRaids built in FTP server is running ** Ignored Mar 6 21:44:16 Tower root: Fix Common Problems: Error: Out Of Memory errors detected on your server Mar 6 21:44:29 Tower root: Fix Common Problems: Warning: Wrong DNS entry for host ** Ignored

Well the long string right ABOVE your excerpt: I took that and went to "shares" then "appdata" then "system" shares then clicked "docker" then "docker" again then clicked "container" and searched for above long string. Once I did that I went into corresponding folder and downloaded "hostconfig" and was able to determine that that long string was referencing NginxProxyManager. I don't know if that's right or if it's culprit; but thats how I arrived. I did limit CPU for NPM, too though.

I found that, and container listed with it(right above it before OOM) is NginxProxyManager - I restricted CPU cores, but it already has "--memory=1G --no-healthcheck" in extra parameters?