NC port command not working from within VPN

[WetSocks 0]

Hello,

I'm currently working on setting up a monitoring script to keep track of a particular service. I'm using the "nc" command within the gluetun docker container for this purpose. As part of this configuration, I've successfully established port forwarding, and the port is functioning as expected.

However, I'm encountering an issue that I'd like to clarify. When I attempt to check the status of the port from within the VPN, I consistently receive a timeout error. I'm using the following command:
 

nc -vz -w5 VPN-IP PORT

Strangely, running the same command outside the VPN environment shows that the port is indeed open.

I'm unsure whether this could be due to a firewall rule with AirVPN or some other factor. Is anyone else facing a similar problem? Or is this an isolated event with my setup? Any advice would be greatly appreciated. Thank you all. Edited ... by WetSocks

[OpenSourcerer 1441]

On 8/17/2023 at 10:54 PM, WetSocks said:

VPN-IP

Is this the interface or the public address?