ANSWERED Connection refused (111)

[nekodesew 0]

I have a proxmox server that has a linux vm. That linux vm is hosting both my torrenting and plex services. When I tried to use airvpn, to open a port only the UDP options are open, the TCP isnt. TCP version says Connection refused (111). What do I need to do so I can open a port and assign it to plex? Since I'm renting I don't have control over my router settings, so I thought this would be a good alternate solution.

[Staff 10346]

2 hours ago, nekodesew said:

I have a proxmox server that has a linux vm. That linux vm is hosting both my torrenting and plex services. When I tried to use airvpn, to open a port only the UDP options are open, the TCP isnt. TCP version says Connection refused (111). What do I need to do so I can open a port and assign it to plex? Since I'm renting I don't have control over my router settings, so I thought this would be a good alternate solution.

Hello!

This message may help:
https://airvpn.org/forums/topic/57512-make-plex-server-available-externally-forever/?do=findComment&comment=253176

Moreover, keep in mind that Plex always listens to port 32400 of the VPN interface, no matter how you configure it: make sure that you can "re-map" the incoming packets. This option is available also in your AirVPN account port panel by filling the "Local" field of the remotely forwarded port.

"Connection refused" means that the attempted TCP connection to your node was actively rejected, i.e. reset through a TCP RST. This usually means that your system is configured to actively reject packets (instead of silently dropping them) to non-existing port, or your firewall is configured to reject packets (instead of silently dropping them). In the first case, it's likely that the VPN interface destination port simply doesn't exist, probably because Plex end-point is 32400 and not what you would expect. Try to "re-map", in the first place, your forwarded remote port to "local" 32400.

If the VM is attached to the host via NAT and it's the host the one connecting to the VPN, you also have to make sure that the incoming packets (which reach the host only in this scenario, of course) are then properly forwarded (by the host) to the final destination (IP address and port of the VM).

Kind regards