ProtonVPN (paid) setup for port forwarding, log says it's setup, portchecker.io disagrees #2723
Answered
by
GamerKingFaiz
jgeorgeson
asked this question in
Q&A
-
|
To preface, I'm looking at this because my torrent client is reporting that it's firewalled and I assume that is preventing me from properly seeding. Downloads are working fine. I have a paid subscription, I did add As the title says, the gluetun logs indicate that port forwarding was setup successfully, but when I test it with portchecker.io it's reported as closed. I did try updating to v3.40 with no improvement, and this issue seems to indicate there is some regression related to Proton port forwarding in v3.40. compose config log |
Beta Was this translation helpful? Give feedback.
Answered by
GamerKingFaiz
Mar 2, 2025
Replies: 1 comment 1 reply
-
|
The logs seem to indicate that all is working well. We see 178.249.210.8 as your VPN IP and 64391 as the forwarded port. Is whatever program you're needing to forward actually running and using that port? If you're not actively running the program that needs forwarding then a site like portchecker won't actually show as open. FWIW, I am using port forwarding on Proton VPN succesfully on Gluetun 3.40. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
The application using the forwarded port is qBittorrent. I use the linuxserver.io image along with the gluetun synchronized port mod. I will often see the client report that it is firewalled, meaning the forwarded port is not reachable. In this situation the tracker site will typically also indicate that my client is indeed not reachable. At the time I posted here, though, qBittorrent was not up and running, so that explains why at that time. But when it is running and showing it's not reachable, I do confirm that the port in the client is correctly displayed as the same port that is in the gluetun logs. But I guess it's something happening in the qBittorrent container then, and not the gluetun container. |
Beta Was this translation helpful? Give feedback.
Answer selected by
jgeorgeson
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The logs seem to indicate that all is working well. We see 178.249.210.8 as your VPN IP and 64391 as the forwarded port.
Is whatever program you're needing to forward actually running and using that port? If you're not actively running the program that needs forwarding then a site like portchecker won't actually show as open.
FWIW, I am using port forwarding on Proton VPN succesfully on Gluetun 3.40.