profzelonka

Have you guys figured out how to solve this issue? I'm on latest version. So I went ahead and ran: php --ini Which finds this: Loaded Configuration File: /etc/php83/php.ini So I use nano the php.ini to add: opcache.enable=1 opcache.enable_cli=1 opcache.memory_consumption=256 opcache.interned_strings_buffer=16 opcache.max_accelerated_files=10000 opcache.revalidate_freq=60 opcache.save_comments=1 But on restarting nextcloud docker and db docker, issue persists. Seems like a unraid/docker setup issue? I'm using an Nginx Proxy Manager as reverse proxy, in case that matters? I'm also getting this error and can't figure out how to solve it, Nginx Proxy Manager has HSTS enabled.

Is there any way to update nextcloud if I'm unable to change the docker app versions in unraid? I have a weird issue in unraid that crashes unraid entirely when I change versions. I just can't upgrade it manually because of the new image. Well, I could if I could chjange the version but that's not an option in my case until that's resolved if ever.. Would be nice to have nextcloud again.

Thanks guys for that 1.0 Komga fix instructions. I changed everything 8080 to 25600 in that file, then hit edit for the docker app and applied the no-change but it recreated the docker as normal, now works!

Did I post in the wrong board, or something?

The other day I woke to find all my dockers are down and unraid terminal as well as any docker terminal won't open, tho dockers show as running and unraid webui was accessible. A power cycle resolved it. I'm able to reproduce the issue now by hitting edit on my nextcloud docker app and changing the lscr.io/linuxserver/nextcloud to any other version, for example lscr.io/linuxserver/nextcloud:version-25.0.4 or lscr.io/linuxserver/nextcloud:24.0.3 . This does not appear to be an issue with this particular app as I once reproduced it with a different app as well but thought it was something else at the time. Anyway, on submitting the version change, it shows to download and setup the docker app successfully. On clicking Console or Logs, the popup comes up with a half-opened terminal where nothing is shown or can be entered. If I click on my UnRaid terminal, same result. If I go to dashboard, all cpu activity stats dropped to 0% usage and nothing updates. All other dockers continue to work but I'm assuming will likely crash after enought time. Changing the nextcloud version back, does *not* unfreeze terminals and a restart is required to get anywhere. I thought it might be my USB3.0 flash and switched to a 2.0 flash drive but issue continues. On latest Unraid 6.12.1. Logs removed for time being.

Looks like that's not it. Whenever I change it to anything except lscr.io/linuxserver/nextcloud the docker freezes and makes my unraid terminal also frozen, all cpu activity stats drop to 0% usage. All other dockers continue to work but looks like it freezes all terminals. Changing it back, does NOT unfreeze terminals and a restart is required. Any ideas? *edit Don't think it's a docker app issue, created an Unraid docker support thread instead:

Got an issue after updating the docker. I didn't do an update for a few months, now log shows: How can I change the tagged image to 25? I tried changing "lscr.io/linuxserver/nextcloud" to "lscr.io/linuxserver/nextcloud:25.0.0" but it literally crashes UnRaid.. Have to restart :\ (command for docker and for unraid stops working entirely, hardware stats stop working, etc.) Am I tagging the wrong image? There's the version but also other variants like 25.0.0-ls233 and amd64-25.0.0, etc. I'm on an intel processor, an i5-10600K, latest UnRaid 6.12.1.

Komga stopped working.. log.txt *edit. Resolved by deleting artemis folder in config, looks like it's a cache folder or something. Still wondering about 443 SSL tho if you get a second.

Hey OP @Roxedus thanks for making the Komga template! It's been running great. I've been using Nginx Proxy Manager to reverse proxy it, making it https, but I wonder: Is there any benefit to making the actual app send everything via https instead of just http? And if it is more secure to do so, any pointers of where the conf file may be located? Thanks!

Please advise - For the HumHub docker, is it safe to update humhub manually within the docker or is it better to wait for the docker to be updated instead?

Set unraid ports to something else. Removed NPM, readded, still can't use it.. Looks like old ports are being remembered somewhere. How do I wipe it?

I have NPM running on 1443 and 180 instead, with router directing web traffic to those unique NPM ports. But now NPM is completely not working since I set it to host, changing it back to bridge it shows up as running but the webserver and webui are inaccessible. /facepalm

Is this what you're trying to refer to? Went ahead and set NPM as host - webui doesn't load anymore, switched it back to bridge, now NPM is a complete dud, no webui and for some reason the port reverted to 8181 from a custom one I set. Stopped it, set it back to my port, still can't access NPM any more.. Come on man.. it's 5 am for me, just gonna call it a failed no sleep night I guess.

Hey thanks! I changed docker setting's "Host access to custom networks" to Enabled. Still getting a 502 error though. Do you mean to change the npm docker's network to br0? Cause I'm using it for other dockers already so I guess that won't work for me. Is there anything else I can try to resolve my 502 error? I can access the VM via IP but not thru the proxy still.

Where can I add this trusted proxies on a VM that's not for HomeAssistant? My VM houses diaspora a decentralized social network - other than that I have the exact same setup as this post. Getting error 502 bad gateway. Can this be set in nginx somewhere on the VM?

Fair enough. I appreciate your prompt support

Ah, thanks, updating now to 6.11.5. So in theory, if I were to stay on 6.11.2 and one of my drives failed and it fails to format the new drive before the rebuilt, the data is lost?

I had one of my drives on it's way out so I moved all the files from it to the other drives and physically switched it out for another drive. I added the new drive to the array and started it. Unraid automatically started running Rebuild on the drive, I assumed to rebuilt the empty prev drive. Once finished, my new replacement drive is still "Unmountable: Unsupported partition layout". I checked to format unmountable drives, hit format. Page refreshes, nothing occurred. Retried, same. 1. What should I do now to get my new drive working in unraid? 2. Why did Unraid rebuild an empty drive? 3. Why did Unraid not format the drive before rebuilding it? 4. Were this to happen unprepared to a drive that wasn't empty.. What should I have done differently to avoid data loss?

Looks like the docker author updated gitlab. Would anyone be willing to help make this work? https://gitlab.com/koehn-docker/diaspora Edit, just in case anyone's reading this and is in the boat I was in.. I finally managed to get it to install in a VM properly in Debian 10. After all the trouble tho.. the platform currently doesn't have an android app that also has working notifications which is a huge blow IMO. Plus new members on the platform can't see old posts and the devs seem to have a hard stance on this being a feature. I had to pass and now I'm back to HumHub, which to my surprise recently got an official App development! https://github.com/humhub/app

Thank you! Got it up and running except I can't get it to work with 443 SSL enabled in nginx default site profile. Have you gotten it to work with SSL? I'm using Nginx Proxy Manager to forward traffic to the docker, my Nextcloud docker works just fine with the same settings so it looks like a HumHub docker issue. (also, clicking on the search in HumHub produces a hard error, tho honest I don't care about it much, just fyi! )

Humhub docker is broken. "Error: The assets directory is not writable by the PHP process." The files are being made as root:root, I'm assuming unraid needs it to be nobody:users but after chowning them all nothing loads without error. 😕 Also, what kind of database does humhub even use? There's no settings to be set?

Would anyone be willing to make the disapora docker work on unraid? Will pay for your appreciated time! ❤️

You got me further! Thank you!! I may have hit a wall though, the diaspora docker just reboots while redis & postgres logs show they're both "ready to accept connections". Diaspora docker log: https://pastebin.com/thjd6exp I just tried setting it up as individual dockers again, same exact issue as in log but doesn't repeat. Just as in the log above, I get the warning about the lock file which I doubt is an issue, then it says it's starting in production and it crashes endlessly. Any ideas? Would really love to run this..

Has anyone been able to get diaspora working on UnRaid? I tried setting up a custom template for docker koehn/diaspora but log showed that it's expecting yaml file and what not. So I got the Compose Manager plugin installed in UnRaid and followed the docker-compose instruction from here , but no matter of my newbie troubleshooting/changes, I'm able to compose up but the actual disapora docker doesn't show the IP on left side nor does log load - window opens and quickly closes. I don't mind manually making the dockers, without Compose Manager and docker-compose, but even with all the env set, logs still expects a yaml and some other ~toml extension file or something like that. It's just diaspora, postgres, and redis. If anyone has set it up successfully, could you please share your setup?