magsol

Figured it out--somehow, the web.conf had bloated to over 78MB (yes, MB) and so was preventing deluge from starting. Deleting it and letting deluge recreate it restored everything from the previous working state (except the web UI password, which I simply reset myself). I have no idea why or how the file got so bloated (even web.conf.bak was over 40MB), so I guess that's something I'll keep an eye on going forward.

Suddenly in the past week, my binhex-delugevpn has stopped working. When I first noticed it and attempted to login, I was unable to (told my password was incorrect). On a hunch, I punched in the default password for the web UI, and that worked--but ALL the settings and active torrents had disappeared. It was like deluge has been reset to 0. So I turned it off (shut down the docker container) and turned it back on, and in this instance, the web UI wouldn't even start. These are the docker logs: [info] bo-bolivia-pf.privacy.network [info] is.privacy.network [info] qatar.privacy.network [info] spain.privacy.network [info] uk-2.privacy.network [info] ro.privacy.network [info] ca-vancouver.privacy.network [info] uk-manchester.privacy.network [info] br.privacy.network [info] sofia.privacy.network [info] kr-south-korea-pf.privacy.network [info] bahamas.privacy.network [info] srilanka.privacy.network [info] au-australia-so.privacy.network [info] france.privacy.network [info] morocco.privacy.network [info] austria.privacy.network [info] italy.privacy.network [info] bangladesh.privacy.network [info] swiss.privacy.network [info] monaco.privacy.network [info] saudiarabia.privacy.network [info] uk-southampton.privacy.network [info] sanjose.privacy.network [info] ireland.privacy.network [info] bogota.privacy.network [info] man.privacy.network [info] montenegro.privacy.network [info] de-frankfurt.pvt.site [info] de-berlin.pvt.site 2026-01-06 09:46:27,667 DEBG 'start-script' stdout output: [info] Successfully downloaded PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken' 2026-01-06 09:46:27,670 DEBG 'start-script' stdout output: [info] Successfully generated PIA token for wireguard [debug] PIA generated 'token' for wireguard is '<REDACTED>' 2026-01-06 09:46:27,846 DEBG 'start-script' stdout output: [debug] PIA generated 'token' for port forwarding is '<REDACTED>' [debug] PIA assigned incoming port is '42122' [debug] PIA port forward assigned expires on '2026-03-10T02:46:27.808370111Z' 2026-01-06 09:46:27,847 DEBG 'start-script' stdout output: [debug] Running infinite while loop to keep assigned incoming port for PIA live... 2026-01-06 09:46:28,010 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port 2026-01-06 09:46:28,847 DEBG 'watchdog-script' stdout output: [debug] Checking we can resolve name 'www.google.com' to address... 2026-01-06 09:46:28,891 DEBG 'watchdog-script' stdout output: [debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.139.106 142.250.139.103 142.250.139.104 142.250.139.147 142.250.139.105 142.250.139.99' 2026-01-06 09:46:28,892 DEBG 'watchdog-script' stdout output: [debug] Waiting for iptables chain policies to be in place... 2026-01-06 09:46:28,895 DEBG 'watchdog-script' stdout output: [debug] iptables chain policies are in place 2026-01-06 09:46:28,895 DEBG 'watchdog-script' stdout output: [info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.30.130.140 different, marking for reconfigure 2026-01-06 09:46:28,900 DEBG 'watchdog-script' stdout output: [info] Deluge not running 2026-01-06 09:46:28,901 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI not running 2026-01-06 09:46:28,905 DEBG 'watchdog-script' stdout output: [info] Privoxy not running 2026-01-06 09:46:28,905 DEBG 'watchdog-script' stdout output: [info] Deluge incoming port 6890 and VPN incoming port 42122 different, marking for reconfigure 2026-01-06 09:46:28,906 DEBG 'watchdog-script' stdout output: [info] Attempting to start Deluge... [info] Removing deluge pid file (if it exists)... 2026-01-06 09:46:29,206 DEBG 'watchdog-script' stdout output: [info] Deluge key 'listen_interface' currently has a value of '10.27.248.138' [info] Deluge key 'listen_interface' will have a new value '10.30.130.140' [info] Writing changes to Deluge config file '/config/core.conf'... 2026-01-06 09:46:29,380 DEBG 'watchdog-script' stdout output: [info] Deluge key 'outgoing_interface' currently has a value of 'wg0' [info] Deluge key 'outgoing_interface' will have a new value 'wg0' [info] Writing changes to Deluge config file '/config/core.conf'... 2026-01-06 09:56:28,209 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port 2026-01-06 10:06:28,412 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port 2026-01-06 10:16:28,614 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port 2026-01-06 10:26:28,814 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port 2026-01-06 10:36:29,012 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port Notice the timestamps in particular: 10 minutes start passing between logging outputs, and the web UI still hasn't come up, but no error messages that I can tell. I haven't changed anything in the past week--nothing in the Unraid app configuration, nor in the deluge configuration files directly. Deluge has been happily seeding away up until a few days ago, so I'm not sure what could have changed, or even where to look. Any help would be greatly appreciated.

Would love to know the answer here, in case anyone else has run into this.

Thank you!

I recently repurposed an old(ish) desktop into an Unraid server. It's old enough that the motherboard doesn't have any M.2 slots, but instead has 4 4TB SSDs. I've seen in the documentation that SSDs are great for cache / pool, but I haven't seen any recommendations pertaining to SSDs in the parity / main array slots, and in fact I've seen some Reddit posts suggesting this would actually lead to performance degradation. There unfortunately isn't any space in the 4U chassis I'm using for HDDs. For the trial period I used what was basically a "dummy" USB drive as the lone main array drive, and configured any apps I installed to use the "cache" of 4 SSDs instead. I did set up the SSD cache to use ZFS, as it seems like that provides some safety in the case of drive failures (in lieu of a parity drive / main array). I guess my question is: is this configuration viable for long-term use? Or should I be trying something else?

Yep! But a lot seem to come with built-in network configs that have to be changed; rather than try and guess which configuration options are exposed in the CA templates and which are hidden, I wanted to see if I could just spin up containers via docker run commands or docker-compose yamls; as I said, I'm more familiar with those. I have; nextcloud-aio and pi hole. In both cases I've run into some of the issues I mentioned about configuration ambiguity, hence I wanted to see if I could essentially strip out the UI entirely and build the configuration from scratch. I completely agree, my problem is figuring out how Unraid works in this regard--it's the simplest, but that simplicity comes with hiding some details, like how to mount volumes within the container deployments. The portainer application I was running that couldn't find its local environment had that problem because it didn't have any mounts; the CA templates don't seem to have that problem (e.g. the CA PortainerCI mounts the volumes correctly), but I'm not entirely sure why, and critically: I haven't been able to figure out why. If someone could clarify how exactly the CA templates are built and how to specify the arbitrary options I am apparently missing, that would also fix my issues. Thanks so much!

I'm brand new to Unraid but familiar with Docker and Docker-Compose. The easiest route to executing `docker run` and Docker-Compose scripts seems to be installing Portainer. I clicked through the portainer search results on the Community Apps page to view the results from DockerHub, and installed the portainer-ce application. However, when I access the admin console, I get this message on the Environment Wizard: In the logs for running docker application, I see this error message repeated: I haven't been able to find any information about how to fix this. I'm unsure what path the `docker.sock` socket lives at in Unraid, but even if I knew, I don't know how to send that volume to the `docker run` command via Unraid's Docker tab. I tried setting the portainer-ce application to "privileged" but that didn't help (I didn't think it would, but I'm just flipping switches at this point). So where does the `docker.sock` socket live in Unraid, and how can I send this volume information to a Docker container in Unraid? Thanks in advance!