Firstaval, thanks for your work it's impressive ! :)
Everything is working execpt one little thing which is annoyning me a bit.
For information, I'm using the container on a Synology 918+.
I can download through the VPN wihtout issue but the little icon which indicating if the port is open show a "!".
I created a Forwarding Port from AirVPN and it's configured in the .rtorrent config file.
I made a TCP check on the public IP from the VPN with the Forward Port targeted and it says LISTENING.
But when I check the supervisord.log file I can see:
[info] Application does not require port forwarding or VPN provider != pia, skipping incoming port assignement"
But it seems that I need to enable the Port Forwarding with AirVPN.
So I check the iptables rules (inside the container) and I can't see any reference to the Port Forwarding port that I get from AirVPn. It seems logic because the container didn't know it during his creation.
I made a final test by doing a tcp check inside the container to check if the internal VPN IP has the Forwarded Port open, it says:
nc -zvw3 VPN_INT_IP FORWARDED_PORT
Warning: Host to VPN_INT_IP isn't authoritative! (direct lookup mismatch)
VPN_INT_IP -> CONTAINER_ID BUT CONTAINER_ID -> CONTAINER_INT_IP
VPN_INT_IP FORWARDED_PORT open
So it seems that the port is opened.
I can't figured out why the verification port icon is still displaying "!".
Even I recreate the container with argument "-e ADDITIONAL_PORTS FORWARDED_PORT" I can imagine that this argument will not be taking care because of the " =! pia" message above.
Hi,
Firstaval, thanks for your work it's impressive ! :)
Everything is working execpt one little thing which is annoyning me a bit. For information, I'm using the container on a Synology 918+.
I can download through the VPN wihtout issue but the little icon which indicating if the port is open show a "!".
I created a Forwarding Port from AirVPN and it's configured in the .rtorrent config file. I made a TCP check on the public IP from the VPN with the Forward Port targeted and it says LISTENING.
But when I check the supervisord.log file I can see:
[info] Application does not require port forwarding or VPN provider != pia, skipping incoming port assignement"But it seems that I need to enable the Port Forwarding with AirVPN.
So I check the iptables rules (inside the container) and I can't see any reference to the Port Forwarding port that I get from AirVPn. It seems logic because the container didn't know it during his creation.
I made a final test by doing a tcp check inside the container to check if the internal VPN IP has the Forwarded Port open, it says:
So it seems that the port is opened.
I can't figured out why the verification port icon is still displaying "!".
Even I recreate the container with argument "-e ADDITIONAL_PORTS FORWARDED_PORT" I can imagine that this argument will not be taking care because of the " =! pia" message above.
Do I miss something ? Thanks for your help!