manderso

Understood. Thanks for the help.

I deleted and re-created the docker.img file. Then re-installed all the apps. They all worked, until I added a second port to the VPN_INPUT_PORTs on my binhex-qbittorrentvpn container. I'm trying to allow multiple apps to use the qbittorrent vpn network. Once I added that second port, the container restarts fine, but then the docker UI is inaccessible again. Is there anything I can do to resolve this, other than re-do the docker.img again?

Can anyone suggest anything to try here?

What's odd is that while I can't click anything when I'm on the docker tab, the docker panel on my dashboard is accessible and can be used.

here's a diag w/ docker actually started... tower-diagnostics-20260513-1312.zip

I updated a container, adding a port to qbittorrent config. After that, I can see the docker UI, but the "thinking" graphic stays on the screen, and the mouse won't click anything, also in the "thinking' graphic. I can click back and go to other pages in Unraid fine, but anytime I hit the docker page, can't get past the thinking graphic. I've restarted, disabled and re-enabled docker. Changed docker network settings from macvlan to ipvlan and restarted again. No change. I've had docker started, and stopped each container from the command line, and the ui shows that the containers are stopped, but still it's not accessible w/ the thinking graphic. I'm on 7.2.6 since yesterday. tower-diagnostics-20260513-1305.zip

Thank you!

I swapped out motherboard and CPU on my unraid server, and since then, the sabnzbd UI won't load. I've attached the logs as per the help instructions. Any help would be greatly appreciated. Thank you sabnzbd_container_out.txt sabnzbd_supervisord.txt

https://www.facebook.com/share/d6cPaWimnfeF7tQM/?mibextid=79PoIi sonnet tempo sata e4p pi47042-2p3b wondering if this will be supported in unraid. Thanks.

Random question, and I don't think it's been asked yet. I'm monitoring qBittorrent/data/logs/qbittorrent.log from a splunk universal forwarder container. The log is getting saved as 600, so the splunk user from the other container cannot read it. How would I go about changing the permissions for that file (without having to do it manually) to be readable to others? Thank you

Yep. Thought I had copied over the new file, guess I didn't. Sorry to bother you. Thanks for the help.

I'm still getting "the remote line is referencing PIA legacy network which is now shutdown" error, even though I've downloaded the newest openvpn.zip file from PIA, and am using the latest (and tried the test) branch of binhex-delugevpn. I've also tried another ovpn file (usually using CA\ Montreal.ovpn, tried CA\ Toronto.ovpn), and get the same error. What am I doing wrong? 2020-12-17 11:34:30.164925 [info] PUID defined as '99' 2020-12-17 11:34:30.189888 [info] PGID defined as '100' 2020-12-17 11:34:30.871321 [info] UMASK defined as '000' 2020-12-17 11:34:30.894360 [info] Permissions already set for volume mappings 2020-12-17 11:34:30.918113 [info] Deleting files in /tmp (non recursive)... 2020-12-17 11:34:30.945285 [info] VPN_ENABLED defined as 'yes' 2020-12-17 11:34:30.969321 [warn] VPN_CLIENT not defined (via -e VPN_CLIENT), defaulting to 'openvpn' 2020-12-17 11:34:30.992415 [info] VPN_PROV defined as 'pia' 2020-12-17 11:34:31.608775 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/CA Toronto.ovpn 2020-12-17 11:34:31.646677 [crit] VPN configuration file '/config/openvpn/CA Toronto.ovpn' 'remote' line is referencing PIA legacy network which is now shutdown, see Q19. from the following link on how to switch to PIA 'next-gen':- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md exiting script... client dev tun proto udp remote ca-montreal.privateinternetaccess.com 1198 resolv-retry infinite nobind persist-key persist-tun cipher aes-128-cbc auth sha1 tls-client remote-cert-tls server auth-user-pass compress verb 1 reneg-sec 0 <crl-verify> -----BEGIN X509 CRL----- ... -----END X509 CRL----- </crl-verify> <ca> -----BEGIN CERTIFICATE----- ... -----END CERTIFICATE----- </ca> manderso@Tower:/mnt/user/appdata/binhex-delugevpn$ ls -al openvpn/ total 16 drwxrwxr-x 1 nobody users 124 Dec 17 11:34 ./ drwxrwxr-x 1 nobody users 486 Nov 8 14:40 ../ -rwxrwxr-x 1 nobody users 3180 Dec 17 11:34 CA\ Toronto.ovpn* -rwxrwxr-x 1 nobody users 2025 Dec 17 11:03 ca.rsa.2048.crt* -rwxrwxr-x 1 nobody users 20 Nov 11 08:26 credentials.conf* -rwxrwxr-x 1 nobody users 869 Dec 17 11:03 crl.rsa.2048.pem* Thanks for your help.

Are you saying you were able to get your fusionio drive working in unraid using the steps above? Are you using it as a cache drive, and is it working as expected? Thanks

Finally figured this out by looking in the letsencrypt.log file in /config. Was seeing this: and i'm not sure how I solved it, but that the account in the mentioned directory was not there. I originally had 2 sub domains set to get a cert, and stopped using one of them and deleted it in the settings, then hit apply, which brought the image down again and for some reason, added a new account to the directory. Letsencrypt saw it and allowed the cert to renew.

Looking at page information, on the security tab in firefox, for my nextcloud page, I see Verified by: Let's Encrypt, Expires on: December 28, 2019.