26 minutes ago, betaman said:

Well, this is super easy to configure and essentially offers the same benefit as the VPN enabled dockers. I didn't change containers as mentioned, just disabled the built-in VPN and moved all my dockers over to the tunnel network. Anyone just starting out and wanting to put "all" their containers behind a VPN should use the method in the video. It's way simpler now with the advances in the OS and use of Wireguard.

Whilst the unraid wireguard vpn method is really cool (and i genuinely mean this!) it does have one problem when it comes to bittorrent, no port forwarding (so no incoming port), at least that was how it was last time i looked into it.

7 minutes ago, binhex said:

Whilst the unraid wireguard vpn method is really cool (and i genuinely mean this!) it does have one problem when it comes to bittorrent, no port forwarding (so no incoming port), at least that was how it was last time i looked into it.

So I'm not sure if this is the same thing or not but I think that's why I need a PIA Server that uses port forwarding? If I don't pick one that has it then the bittorrent client either fails or is miserably slow. Make sense?

p.s.

Huge thanks to you and the work you've done over the years. My server dates back to 2009 and I've used your dockers forever!

Edited June 15Jun 15 by betaman

10 minutes ago, betaman said:

So I'm not sure if this is the same thing or not but I think that's why I need a PIA Server that uses port forwarding? If I don't pick one that has it then the bittorrent client either fails or is miserably slow. Make sense?

This makes perfect sense to me, which is why the spaceinvader one video you linked to and the solution shown in that video do NOT provide you with an incoming port, that is my point, so your speeds will be slow if you use that method, it doesnt matter what PIA endpoint you select when using that method, you will not get an incoming port, period.

3 minutes ago, binhex said:

This makes perfect sense to me, which is why the spaceinvader one video you linked to and the solution shown in that video do NOT provide you with an incoming port, that is my point, so your speeds will be slow if you use that method, it doesnt matter what PIA endpoint you select when using that method, you will not get an incoming port, period.

Ok, so it's the upload speed that will be majorly impacted in this case? You're saying this is a WG limitation?

5 minutes ago, betaman said:

Ok, so it's the upload speed that will be majorly impacted in this case?

no, both, less peers means less upload and download speed.

5 minutes ago, betaman said:

You're saying this is a WG limitation?

not at all, wireguard can do it, but the unraid wireguard implementation has no functionality to allocate a dynamic incoming port from the VPN provider allocate a incoming port from the VPN provider, and yes its tricky as each provider does it differently, PIA is actually one of the most complex providers.

Just now, binhex said:

no, both, less peers means less upload and download speed.

not at all, wireguard can do it, but the unraid wireguard implementation has no functionality to allocate a incoming port from the VPN provider, and yes its tricky as each provider does it differently, PIA is actually one of the most complex providers.

Ok, interesting. I didn't see a noticable difference in speeds between my old (this docker) and new (Unraid wireguard setup from video) setups. I'll keep an eye on it and report back.

1 hour ago, binhex said:

Whilst the unraid wireguard vpn method is really cool (and i genuinely mean this!) it does have one problem when it comes to bittorrent, no port forwarding (so no incoming port), at least that was how it was last time i looked into it.

It does port forward just fine. It uses whatever mapping you use for container. So if you try to host a website in the container on port 80, but map it it 2345. It's port 2345 for the wireguard forwarding. Granted, gonna be a pain in the ass for anything dynamic but when you know what you need, it works fine. My main page and repo is hosted that way, including their proxy, as there I don't need ipv6.

14 minutes ago, Mainfrezzer said:

Granted, gonna be a pain in the ass for anything dynamic

Sadly that is a problem for PIA, and protonvpn (i think) also uses dynamic ports, thanks for chipping in though and confirming its fine for static incoming ports, that is good to know!.

On 6/13/2026 at 5:32 PM, wgstarks said:

Looking at your docker run command I see lots of ports listed in VPN_INPUT_PORTS that I'm not seeing a corresponding port mapping for.

See https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md.

Scroll down to Q24.

Turns out it was tailscale that broke it. I've been running tailscale since unraid introduced it and never had a problem so I had no reason to suspect this was the issue. I had to add the tailscale network to the LAN_NETWORK. Holy crap I'm so happy this is fixed. Took me 2 weeks to track this down lol. Anyway, thanks for your help.

7 minutes ago, hyp3r_bor3an said:

I've appealed to both reddit and AI, neither has been helpful. If you have any advice or insight it would be greatly appreciated.

Attach your supervisord log and docker run command to your next post. Be sure to redact any users/passwords.

just went through 7.3.1 update, fyi, looks like tailscale broke something when using bridge on the container and it wont open webgui qbit, disconnecting tailscale on local client and its back, not sure why.... I'll worry about it later I guess. service continues working fine in background ofc.

1 hour ago, Mizerka said:

just went through 7.3.1 update, fyi, looks like tailscale broke something when using bridge on the container and it wont open webgui qbit, disconnecting tailscale on local client and its back, not sure why.... I'll worry about it later I guess. service continues working fine in background ofc.

Same here.

On 6/15/2026 at 12:29 PM, betaman said:

Ok, interesting. I didn't see a noticable difference in speeds between my old (this docker) and new (Unraid wireguard setup from video) setups. I'll keep an eye on it and report back.

Just reporting back as stated above. Been using the wireguard method and still haven't noticed any speed issues torrenting. Note: I only use public trackers so perhaps if I was seeding more it might be more noticeable? Not sure tbh.