blaine07

I had to change Owner of folder to "nobody" as well to get it to install. Issue now is the same-- Not sure what to do now... sigh: EDIT: anyways, I did have to change permissions on the nextcloud* appdata folder..and once I restarted container again it seems the cron thing sorted itself out..It's updating in similar time frames and other NC instance I have and not red anymore? Edit 2: more I think about it the more I think that folder shouldn’t be having ownership problems. Not sure at what point ownership should get changed to “nobody” but it appears that failing to happen, for whatever reason, was what the issue was. When at installation is it supposed to handle that itself? Change ownership of install folder. Is that a Nextcloud or Unraid issue?

@mgutt I haven’t had time to edit my Post Arguments yet but I just want to say thank you. Thank you for all the help you provide all of us in this thread. I can see it’s daunting. Good work mate; thank you!

I can’t confirm yet I’ve resolved my issue but it’s likely my own idiocracy. See my post above about post arguments.

My Nextcloud and other stuff IS on a custom network BUT NPM isn’t running on HOST; it’s a static BRO IP on network. Yeah I don’t think it’s something I even need; likely my problem, too lol. I’ll remove and report back soon.

I’ll try just removing it and see what happens. Since not referring to any containers by “name” and instead using all IP:PORT I don’t think I even need the syntax/be on specific network too?

Am I doing this add on network thing right? I don’t even think I need it because I am not referring to any containers by name- all IP:PORT. Could this be my issue?

Back to doing it again. Guess I just may ignore it. It never quits working. Just spams logs. Or I need to put a 1 hour restart chrono on NPM. Sometimes it goes 2-4 or 12 hours without spamming logs.... Hmm

Macvlan was total chaos for me. I just deleted the mapping on pfSense. We’ll see what that does.

I think other issue is now that Unraid uses ipvlan for Docker it uses same mac address for every container in Unraid. I am already using Unraids NIC Mac address for a static IP for Unraid itself which means I can't actually set static IP for NPM since MAC address is already tied to Unraids actual IP. Since Unraid changed to ipvlan I haven't figured out how to get around it; i suspect it's relative to my issue, somehow, though.

No, but in pfSense I don’t have a MAC addresses assigned with .3 or static set because Unraid uses same MAC address for everything? See post below below for pics. Somehow totally jacked up post.

Shouldn’t be. That’s my static range in pfSense.

It’s only sometimes it does it, though? Do you see anything awry?

Anyone have any ideas how to stop this? Rebooting container stops it for a bit but it always comes back sooner or later. I thought “98” pointed to a config possibly but no dice. Any ideas? See attached. Edit: seems to always continue to work fine when it does this; maybe slows down slightly.

CLI or update.phar thing? Anyrhing noteworthy on 25.0.2 for you?(yes I read change log but…)

Nextcloud 25.0.2 corresponding container was released by Linuxserver.io sometime yesterday. You both, above, have newest version of container? I wanted to go 25.0.2 but I guess so far good thing I held out...

In Unraid file manager who does it show has ownership of Nextcloud app data? What is its read write rules?

I’m not re-inventing wheel but this works: https://forums.unraid.net/topic/48383-support-linuxserverio-nextcloud/?do=findComment&comment=1183298

Anyone gone 25.0.2 successfully yet?

Is the default username/password not "guacadmin" anymore? Spun a new instance up today and can not login...Any ideas? RESOLVED: EDIT: I am dumb, basically.

This morning I went to upload a file and was greeted with "General error: 1034 index for table 'oc_filecache' is corrupt; try to repair it" Does anyone have any ideas how to fix this before I inevitably go way out in the weeds and make my day worse? IMG_5142.heic EDIT: It *appears* that "emtpying" the "oc_filecache" table in phpMyAdmin has done the trick... :cross fingers: EDIT 2: Is this anything harmful? What does it mean? :see below:

Can confirm; THANK YOU!

Getting a lot of "system error" when trying to start containers. Grabbed a diagnostics and log file; attached. Any help, please? tower-diagnostics-20221115-0659.zip tower-syslog-20221115-1300.zip

Anyone have any ideas what "service unavailable" would allude to out of the blue? Restarted container; same thing. EDIT: Evidently a few days ago I made a "breaking" change. No idea why just today it became and issue; figured it out. I dumb, basically. Live, learn. Sometimes I learn more than I live; that day is today LOL.

Well I moved my PostgreSQL Nextcloud over; it works fine etc but can't seem to get the self hosted version of Collabora to work. It's configured just as it is , and works, on my NC 24.0.6. Only difference I see is on NC 25.0.1 the "Nextcloud Office" version is 7.0.1 and on my NC 24.0.6 the version is 6.3.1. Anyone have any ideas? Anyone else having Collarboar work correctly in NC 25? EDIT: I am dumb; had to add second instance to "aliasgroup2" in Collabora container. 🙂