pXius

8 Years in for me. The one thing that almost pulled me away was ZFS. Now that we have that, I'll be here for much longer. Even if I move away from the traditional array pool completely, the OS still ticks a lot of the boxes that are important to me. Immutability, app discovery, quick updates relative to the kernel and of course the community that serves as a support base. You can still go off script and do advances things if you have a use case that calls for it. Want compose files? There's a plugin. Want kubernetes? Install k3s/d in an LXC container etc. Here's to 19 more.

Thanks! Will give it a shot and report back.

@furian Same issue. Did you ever get it resolved?

SOLVED - See bottom of post. --- Hey @binhex I'm at a loss trying to figure out a connectivity issue I've recently run into. Non of my containers routing traffic through privoxyvpn have internet access. This includes the privoxy container itself. Confirmed by pinging google.com from the privoxyvpn container along with sanity checks from other containers routing through it. I'm using a wireguard configuration which has not changed in some time. I've also recreated by wiregaurd conf just in case. I'm using the default nameservers as per the container env. I enabled debug logs and noticed this. 2024-07-27 22:17:03,301 DEBG 'start-script' stderr output: mv: cannot move '/etc/resolv.conf.676.openresolv' to '/etc/resolv.conf': Device or resource busy When I cat that file it produces: # Generated by resolvconf nameserver 10.64.0.1 The above address is not in the resolv.conf it's trying to override. It only has the nameservers from the ENV var set in the template. The debug logs also indicate that www.google.com can not be resolved. That said, even if I ping the google IP directly from the container shell to avoid the lookup, it still times out. I should mention that containers within the container network can communicate with one another without issue. Any help with the above would be greatly appreciated. Please find attached my docker-conf, logs and IP table output. --- SOLUTION: After spending hours on this I finally realized the issue was with the specific VPN node I was connecting to (Mullvad). A node I have been using for the better part of 2 years. I discovered this when testing the config file on another device. I created another config file selecting another node and the issues are resolved. I also deleted my unraid template because it's a bit outdated compared the new one when it comes to env vars available. This got rid of the resolv file not being bale to be overridden. It would be awesome if we could have multiple wg#.conf files as fallbacks. Is that a reasonable request? -- Removing attachments for privacy.

You can roll back to ver 2. here. https://forums.unraid.net/topic/40756-support-linuxserverio-sabnzbd/?do=findComment&comment=884284 But you'll probably need to change your flow going forward.

If you're using Authentication version 3 breaks the ability to log in. You get an HTTP 500 error. SABNZBD forum says it will be fixed in the next version. In the meantime, disable auth, or use your reverse proxy's HTML auth. Alternatively, roll back to version 2 by pasting linuxserver/sabnzbd:2.3.9-0ubuntu1jcfp218.04-ls67 into you template's repository field, instead of linuxserver/sabnzbd:latest Link to the thread. https://forums.sabnzbd.org/viewtopic.php?f=2&t=24885

EU Endpoints working again. Quick question, Is there a way to get the webui to function if you're using a custom br ip? When I use a custom IP my web ui no longer loads. Bridge obviously works just fine. Also, I AM using a server that supports port forward. Sweden. Tried Frankfurt as well. PS. Disabling VPN lets web ui function even on a custom IP. I've tried a ton of things but I'm at a loss.

Been pulling my hair out of my head thinking I messed up somewhere. Great....

Awesome! Thanks!

Just ran into the error as well. Is there an easy way to roll back to an older release?

I'm having an issue with the BitWarden container. Version 1.9.1-8be2ed62 Unraid Version: 6.8.0-rc 3 Regardless of what I set the port to in the template, it will keep using port 80. This makes my port forwarding tricky considering port 80 is already being used. Any ideas?

You having the same issue I had, how are you trying to connect to your WEBUI? On what IP range is your Deluge and what IP range is the mashine you are trying to connect from? Also, give your Deluge an IP other than that of the Unraid machine.

Download the Firefox container from the APPS section in unraid. If your Deluge docker is using the same IP as your host unraid machine, then use the same IP for firefox as well. If your deluge docker has an ip different from that of the host machine, you will need to use a different IP for the firefox docker as well. It's a security thing. After that you can access the Deluge docker via the firefox docker by entering the deluge IP in the firefox address bar. When outside your network you'll need to access your local network via a VPN of sorts. My router has a openVPN server as a feature, so I just connect to that when away from home.

Ended up being an issue logging onto my home network remotely via a VPN. I'm now just using the Firefox docker container to access Deluge when away from home. Thanks for the help and the awesome contribution to the community! It's appreciated a million times over!

Another "Can't access the webGui post". Been running fine for months, not sure what changed. I've tried different PIA endpoints to no avail. Seems to connect to the VPN, webgui just won't launch. Any ideas? 2019-06-10 23:47:52,096 DEBG 'start-script' stdout output: [debug] OpenVPN command line:- /usr/bin/openvpn --daemon --reneg-sec 0 --mute-replay-warnings --auth-nocache --setenv VPN_PROV 'pia' --setenv DEBUG 'true' --setenv VPN_DEVICE_TYPE 'tun0' --setenv VPN_REMOTE 'de-frankfurt.privateinternetaccess.com' --script-security 2 --writepid /root/openvpn.pid --remap-usr1 SIGHUP --log-append /dev/stdout --pull-filter ignore 'up' --pull-filter ignore 'down' --pull-filter ignore 'route-ipv6' --pull-filter ignore 'ifconfig-ipv6' --pull-filter ignore 'tun-ipv6' --pull-filter ignore 'persist-tun' --pull-filter ignore 'reneg-sec' --remote 185.220.70.171 1198 udp --remote 185.220.70.166 1198 udp --remote 185.220.70.138 1198 udp --remote 185.220.70.152 1198 udp --remote 185.220.70.155 1198 udp --remote 185.220.70.136 1198 udp --remote 185.220.70.169 1198 udp --remote 185.220.70.172 1198 udp --remote 185.220.70.134 1198 udp --remote 185.220.70.140 1198 udp --remote 185.220.70.131 1198 udp --remote 185.220.70.144 1198 udp --remote 185.220.70.170 1198 udp --remote-random --up /root/openvpnup.sh --up-delay --up-restart --keepalive 10 60 --setenv STRICT_PORT_FORWARD 'yes' --disable-occ --auth-user-pass credentials.conf --cd /config/openvpn --config '/config/openvpn/DE Frankfurt.ovpn' 2019-06-10 23:47:52,096 DEBG 'start-script' stdout output: [info] Starting OpenVPN... 2019-06-10 23:47:52,110 DEBG 'start-script' stdout output: Mon Jun 10 23:47:52 2019 WARNING: file 'credentials.conf' is group or others accessible Mon Jun 10 23:47:52 2019 OpenVPN 2.4.7 [git:makepkg/2b8aec62d5db2c17+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 19 2019 Mon Jun 10 23:47:52 2019 library versions: OpenSSL 1.1.1b 26 Feb 2019, LZO 2.10 2019-06-10 23:47:52,110 DEBG 'start-script' stdout output: [info] OpenVPN started 2019-06-10 23:47:52,110 DEBG 'start-script' stdout output: Mon Jun 10 23:47:52 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts [debug] Waiting for valid IP address from tunnel... 2019-06-10 23:47:52,110 DEBG 'start-script' stdout output: Mon Jun 10 23:47:52 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]185.220.70.170:1198 2019-06-10 23:47:52,110 DEBG 'start-script' stdout output: Mon Jun 10 23:47:52 2019 UDP link local: (not bound) Mon Jun 10 23:47:52 2019 UDP link remote: [AF_INET]185.220.70.170:1198 2019-06-10 23:47:52,261 DEBG 'start-script' stdout output: Mon Jun 10 23:47:52 2019 [84dcd2f8211fd75d6fad788d96ffef26] Peer Connection Initiated with [AF_INET]185.220.70.170:1198 2019-06-10 23:47:58,533 DEBG 'start-script' stdout output: Mon Jun 10 23:47:58 2019 TUN/TAP device tun0 opened Mon Jun 10 23:47:58 2019 /usr/bin/ip link set dev tun0 up mtu 1500 2019-06-10 23:47:58,534 DEBG 'start-script' stdout output: Mon Jun 10 23:47:58 2019 /usr/bin/ip addr add dev tun0 local 10.37.10.6 peer 10.37.10.5 2019-06-10 23:47:58,534 DEBG 'start-script' stdout output: Mon Jun 10 23:47:58 2019 /root/openvpnup.sh tun0 1500 1558 10.37.10.6 10.37.10.5 init 2019-06-10 23:47:58,537 DEBG 'start-script' stdout output: [debug] Waiting for valid IP address from tunnel... 2019-06-10 23:47:58,537 DEBG 'start-script' stdout output: [debug] Waiting for valid IP address from tunnel... 2019-06-10 23:47:58,538 DEBG 'start-script' stdout output: Mon Jun 10 23:47:58 2019 Initialization Sequence Completed 2019-06-10 23:47:58,639 DEBG 'watchdog-script' stdout output: [debug] Valid IP address from tunnel acquired '10.37.10.6' [info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.37.10.6 different, marking for reconfigure 2019-06-10 23:47:58,642 DEBG 'start-script' stdout output: [debug] Valid IP address from tunnel acquired '10.37.10.6' 2019-06-10 23:47:58,642 DEBG 'watchdog-script' stdout output: [info] Deluge not running 2019-06-10 23:47:58,643 DEBG 'start-script' stdout output: [debug] Valid IP address from tunnel acquired '10.37.10.6' 2019-06-10 23:47:58,643 DEBG 'start-script' stdout output: [debug] Port forwarding is enabled 2019-06-10 23:47:58,643 DEBG 'start-script' stdout output: [debug] Checking endpoint 'de-frankfurt.privateinternetaccess.com' is port forward enabled... 2019-06-10 23:47:58,643 DEBG 'start-script' stdout output: [debug] Valid IP address from tunnel acquired '10.37.10.6' 2019-06-10 23:47:58,644 DEBG 'start-script' stdout output: [debug] Attempting to get external IP using Name Server 'ns1.google.com'... 2019-06-10 23:47:58,645 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI not running 2019-06-10 23:47:58,646 DEBG 'start-script' stdout output: [info] Attempting to curl https://www.privateinternetaccess.com/vpninfo/servers?version=82... 2019-06-10 23:47:58,787 DEBG 'start-script' stdout output: [info] Successfully retrieved external IP address 185.220.70.170 2019-06-10 23:47:58,847 DEBG 'watchdog-script' stdout output: [debug] External IP address from tunnel is '185.220.70.170' 2019-06-10 23:47:58,847 DEBG 'watchdog-script' stdout output: [debug] Waiting for file '/home/nobody/vpn_incoming_port.txt' to be generated (contains PIA API generated incoming port number)... 2019-06-10 23:47:59,030 DEBG 'start-script' stdout output: [info] Curl successful for https://www.privateinternetaccess.com/vpninfo/servers?version=82, response code 200 2019-06-10 23:47:59,077 DEBG 'start-script' stdout output: [debug] PIA endpoint 'de-frankfurt.privateinternetaccess.com' is in the list of endpoints that support port forwarding 2019-06-10 23:47:59,077 DEBG 'start-script' stdout output: [info] List of PIA endpoints that support port forwarding:- [info] ca-toronto.privateinternetaccess.com [info] ca-montreal.privateinternetaccess.com [info] ca-vancouver.privateinternetaccess.com [info] de-berlin.privateinternetaccess.com [info] de-frankfurt.privateinternetaccess.com [info] sweden.privateinternetaccess.com [info] swiss.privateinternetaccess.com [info] france.privateinternetaccess.com [info] czech.privateinternetaccess.com [info] spain.privateinternetaccess.com [info] ro.privateinternetaccess.com [info] israel.privateinternetaccess.com [debug] Attempting to get dynamically assigned port... 2019-06-10 23:47:59,080 DEBG 'start-script' stdout output: [info] Attempting to curl http://209.222.18.222:2000/?client_id=1450c6c2e51317ffe1d184a94bab67aacf61835be0969a7f1cb66ff362bfbd8c... 2019-06-10 23:47:59,928 DEBG 'start-script' stdout output: [info] Curl successful for http://209.222.18.222:2000/?client_id=1450c6c2e51317ffe1d184a94bab67aacf61835be0969a7f1cb66ff362bfbd8c, response code 200 2019-06-10 23:47:59,951 DEBG 'start-script' stdout output: [debug] Successfully assigned incoming port 24365 2019-06-10 23:48:00,849 DEBG 'watchdog-script' stdout output: [debug] Incoming port for tunnel is '24365' 2019-06-10 23:48:00,849 DEBG 'watchdog-script' stdout output: [info] Deluge incoming port 6890 and VPN incoming port 24365 different, marking for reconfigure 2019-06-10 23:48:00,849 DEBG 'watchdog-script' stdout output: [info] Attempting to start Deluge... [info] Removing deluge pid file (if it exists)... 2019-06-10 23:48:01,063 DEBG 'watchdog-script' stdout output: [info] Deluge listening interface currently defined as 0.0.0.0 [info] Deluge listening interface will be changed to 0.0.0.0 [info] Saving changes to Deluge config file /config/core.conf... 2019-06-10 23:48:01,288 DEBG 'watchdog-script' stdout output: [info] Deluge process started [info] Waiting for Deluge process to start listening on port 58846... 2019-06-10 23:48:01,498 DEBG 'watchdog-script' stdout output: [info] Deluge process listening on port 58846 2019-06-10 23:48:01,865 DEBG 'watchdog-script' stdout output: Setting random_port to False.. Configuration value successfully updated. 2019-06-10 23:48:02,227 DEBG 'watchdog-script' stdout output: Setting listen_ports to (24365, 24365).. Configuration value successfully updated. 2019-06-10 23:48:02,614 DEBG 'watchdog-script' stdout output: [info] No torrents with state 'Error' found 2019-06-10 23:48:02,614 DEBG 'watchdog-script' stdout output: [info] Starting Deluge Web UI... 2019-06-10 23:48:02,614 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI started 2019-06-10 23:48:02,615 DEBG 'watchdog-script' stdout output: [debug] VPN incoming port is 24365 [debug] Deluge incoming port is 24365 [debug] VPN IP is 10.37.10.6 [debug] Deluge IP is 10.37.10.6 2019-06-10 23:48:32,616 DEBG 'watchdog-script' stdout output: [debug] Waiting for valid IP address from tunnel... 2019-06-10 23:48:32,729 DEBG 'watchdog-script' stdout output: [debug] Valid IP address from tunnel acquired '10.37.10.6' 2019-06-10 23:48:32,734 DEBG 'watchdog-script' stdout output: [debug] External IP address from tunnel is '185.220.70.170' 2019-06-10 23:48:32,735 DEBG 'watchdog-script' stdout output: [debug] Incoming port for tunnel is '24365' 2019-06-10 23:48:32,737 DEBG 'watchdog-script' stdout output: [debug] VPN incoming port is 24365 [debug] Deluge incoming port is 24365 [debug] VPN IP is 10.37.10.6 [debug] Deluge IP is 10.37.10.6