You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I opened the port on the AirVPN server and configured the container according to the instructions by placing the correct port in the deluge, I added the forwarded port in the container but the port still appears as closed.
The text was updated successfully, but these errors were encountered:
You shouldn't do the last step you mentioned: adding "the forwarded port in the container". Do you mean VPN_INPUT_PORTS? Quoting the readme:
IMPORTANT
Please note 'VPN_INPUT_PORTS' is NOT to define the incoming port for the VPN, this environment variable is used to define port(s) you want to allow in to the VPN network when network binding multiple containers together, configuring this incorrectly with the VPN provider assigned incoming port COULD result in IP leakage, you have been warned!.
Or did you add it via -p PORT:PORT arguments to the run command? That's also wrong.
The port forwarding is done by the VPN provider (AirVPN in your case), and it goes through the VPN tunnel, so you just open the port on the AirVPN server and configure deluge Incoming Port in Network preferences accordingly. I don't use AirVPN, but similar steps work fine with AzireVPN, I don't see how your case would differ.
I opened the port on the AirVPN server and configured the container according to the instructions by placing the correct port in the deluge, I added the forwarded port in the container but the port still appears as closed.
The text was updated successfully, but these errors were encountered: