betaman

Bumping this thread since I sent it right before holidays

I’m using Ontario with no issue except the random speed drop. Still wondering if there’s a better setup for all containers vs these vpn specific ones?

I thought you also said connection to binhex *arr containers also didn’t work? If only Sabnzbdvpn isn’t working then try setting vpn configuration setting to no in the docker settings and see if it launches?

I’ve been searching for an “updated” guide on configuring my UnRAID server to run my *arr, sabnzbd and qbittorent containers behind a vpn (preferably PIA as that’s what I currently use). I’m somewhat familiar with some wireguard setups (ie using WG plus PIA in Binhex’s vpn containers currently) as well as recently configuring Tailscale for remote access (was previously using Wireguard for tunneled access but kept having intermittent issues like I have with the vpn configured containers). Anyway, looking for some guidance on if there’s a better setup in 2024 with either UnRAID 6.12.14 or a 7 RC to simplify this setup and not have to worry if the vpn is working or not, speed issues etc? Thanks

You mention Tailscale but have you tried turning off the VPN in the sabnzbdcpn docker config settings? The fact that your *arr dockers aren’t working though points to a configuration issue with your server. Can you access any docker URL’s on your server? I’m sure someone more experienced will come along but since it’s Christmas Eve responses might be sparse.

Has anyone had an issue with speed lately? I'm using this container and qbittorrentvpn and only seeing speed issues with this one. Only getting about 1.5MB/s on my gig line. I've tried resetting my connection with my news server (Tweaknews) but issue seems to be related to VPN (using PIA+Wireguard thru Ontario...same setup as qbittorrentvpn). Disabling VPN on sabnzbdvpn solves the issue. In general, is there a better vpn setup now with PIA+Wireguard for nzb's and torrents than the individual vpn containers?

Thanks for the help. Restarting the PC (and installing some Windows updates) seems to have fixed it for now. I'll report back if the issue returns or mark as solved. Thanks again.

So it seems to be tied to one browser on one WIndows PC on my network. Browser is Chrome and PC is running WIndows 10 22H2. Chrome is logged in with my Google account so settings should be shared across platforms. I have another Win 10 environment (running in a VM on the Unraid server) that is working fine with Chrome. Any thoughts? EDIT: Just checked safari as well from my phone and it's working correctly. Also, the PC was working fine and then stopped all of the sudden (that's why it took me a while to figure out what was going on with my server). Some settings in the browser are managed by group policy but I have no idea what might be affecting this behavior since I can reach the server fine (ie firewall).

That’s just one example. No terminal window, log or commands get executed when I click them from local gui. They only work from the online management gui.

I can't get a command prompt, see the log file etc. unless I'm using the web version. Pulliing up the log is a blank screen and I'm guessing all commands except reboot and shutdown do nothing as well. I discovered the problem when I couldn't delete a Wireguard tunnel. Here's what the log file looks like through local GUI with Array started (same if it's not started though): As noted, I can't run a diagnostics either unless I use the https://connect.myunraid.net site. tower-diagnostics-20240917-1556.zip

So I think the issue had to do with Unraid.net? Seems my system got logged out and by logging in I was able to manage my server from the connect.myunraid.net website? Does that make sense? It's like my webgui wasn't really connected to the server so the commands weren't doing nothing (except shutdown worked?). Array is running now. EDIT: Upon further investigation, my local webui is not functioning and I can only execute commands via Server Management on the https://connect.myunraid.net/ site?

My array is set to not autostart. Upon a reboot, the array will no longer start and the GUI is stuck. I also can't access the log (before or after) the attempted array start (regular and maintenance mode). I also can't post a diagnostics report as the system just hangs. The system will shutdown. Should I pull the flash to try and review the log? Looking for some troubleshooting guidance. Thanks. Note: I'm using 6.12.13

Well, 2.5 yrs later and I have the same issue...ugh. Will check the ipad to see if I can get it back there.

I did what I described above and was able to resolve the IP conflict as well as reserve the IP address once I undid and redid the bridging solution that @JorgeB suggested. Thanks!

The other thing is I can't assign a fixed IP address (reservation) to this new MAC address because the UDM-SE thinks it's still tied to the prior setting. Do I need to reverse the bridging, remove fixed IP from the original MAC address and then re-enable bridging etc.? EDIT: Probably not a huge deal since I have the static IP assigned in UnRAID but I guess I'm just anal...haha

Thanks for the response. I'm on v6.12.10 so I tried enabling bridging in network settings and I did a reboot of the server. I was still showing 2 MAC addresses with different IPs but now it seems to be "fixed". One address showing but I don't recognize the MAC address (it's 72:cd:fe:eb:3e:49 which is not the MAC address of the eth0 port on my server). Perhaps it's related to the bridging (see pic):

I replied to this post earlier in the week but no traction so thought I'd start a new thread. I've got a Ubiquity DM-SE router and it's reporting an IP conflict with my UnRAID server IP: Doing an ifconfig from a terminal window shows this with respect to the MAC address with the conflict: I tried removing vhost0 from the GUI but no luck plus I noticed I have the same route (192.168.1.0/24) with 2 different gateways (vhost0 and bond0): How do I figure out what setting is causing the IP conflict or is this to be expected (doesn't seem it like should be)? Thanks

I'd like to bump this as well as I have a similar issue: Edit: I ran an ifconfig and see this related to the same MAC address:

Having the same issue but in my case the timing is coincidental with a modem change from my ISP (Spectrum). Also having DNS issues with Qbittorrentvpn from Binhex (using PIA and Wireguard). Also, in my case it never resolves itself. EDIT: Pretty sure it's the same issue with both (and related to the new modem) as I have the same DNS failure in both docker logs: EDIT 2: Idiot alert...never thought to restart the containers after the modem change. Doh..all fixed.

I got a new modem yesterday from my cable company. Router config didn't change. I'm using wireguard with PIA in the docker config. Having DNS issues and not sure what I need to configure to get it working again? This is what I see in the supervisord.log: 2024-05-29 08:58:41,096 DEBG 'watchdog-script' stdout output: [warn] Incoming port site 'https://canyouseeme.org/' failed to web scrape, marking as failed 2024-05-29 08:58:41,107 DEBG 'watchdog-script' stdout output: [warn] Incoming port site 'https://ifconfig.co/port/55162' failed json download, marking as failed 2024-05-29 09:00:06,291 DEBG 'watchdog-script' stdout output: [info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure... 2024-05-29 09:01:31,490 DEBG 'watchdog-script' stdout output: [info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure... 2024-05-29 09:02:56,690 DEBG 'watchdog-script' stdout output: [info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure... 2024-05-29 09:04:21,872 DEBG 'watchdog-script' stdout output: [info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure... 2024-05-29 09:05:47,042 DEBG 'watchdog-script' stdout output: [info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure... 2024-05-29 09:07:12,241 DEBG 'watchdog-script' stdout output: [info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure... 2024-05-29 09:08:37,447 DEBG 'watchdog-script' stdout output: [info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure... I also can't find /tmp/dnsfailure log file. EDIT: Idiot alert...never thought to restart the containers after the modem change. Doh..all fixed.

Not sure why it matters (since I set the parameter from ovpn to wireguard) but I deleted the Openvpn folder in my Qbittorrent config folder and it worked.

docker run -d --name='binhex-qbittorrentvpn' --net='bridge' --privileged=true -e TZ="America/New_York" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Tower" -e HOST_CONTAINERNAME="binhex-qbittorrentvpn" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='XXXXX' -e 'VPN_PASS'='XXXXX' -e 'VPN_PROV'='pia' -e 'VPN_CLIENT'='wireguard' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='yes' -e 'WEBUI_PORT'='8080' -e 'LAN_NETWORK'='192.168.1.0/24' -e 'NAME_SERVERS'='84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1' -e 'VPN_INPUT_PORTS'='' -e 'VPN_OUTPUT_PORTS'='' -e 'DEBUG'='false' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8080]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/qbittorrent-icon.png' -p '6881:6881/tcp' -p '6881:6881/udp' -p '8080:8080/tcp' -p '8118:8118/tcp' -v '/mnt/user/appdata/downloads':'/data':'rw' -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw' 'binhex/arch-qbittorrentvpn' b62d305dd6ed14ece4b1d60d366b49eee6b377ae9282c083719b902316c5de17 The command finished successfully!

I just took a look at the supervisorord.log. Getting this warning: [warn] Unable to successfully download PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'

Yeah, sorry, I just saw this toggle as well: Still not getting the webgui.

Thanks for the advanced view tip - knew about it and just forgot. What I see now is this: I'm still unclear where I should add --privileged=true? EDIT: Nevermind. I just saw that "Privileged" was already toggled on. Still can't get the Webgui to come up. Could this be the issue: AllowedIPs = 0.0.0.0/0 If I try to change this to 192.168.1.0/24 it just reverts back on container startup.