ANSWERED New ports aren't open

[purplebored 0]

Hi, I have 3 ports open currently and only one of them is working I tried deleting them and generating new ones but it doesn't seem to work. I just get a "Connection timed out (110)" and "Connection refused (111) ". I tried searching the forums for people with those issues but couldn't find a post. If there is a post about that issue then sorry for the duplicate. I would really appreciate some help with this issue.

Best regards, purplebored

[Staff 10014]

8 hours ago, purplebored said:

Hi, I have 3 ports open currently and only one of them is working I tried deleting them and generating new ones but it doesn't seem to work. I just get a "Connection timed out (110)" and "Connection refused (111) ". I tried searching the forums for people with those issues but couldn't find a post. If there is a post about that issue then sorry for the duplicate. I would really appreciate some help with this issue.

Best regards, purplebored

Hello!

We have checked from inside the VPN server you're currently connected to, and the ports are forwarded properly, but by trying to reach your system through the proper ports we always get an almost immediate connection refused.

Can you please test different servers and check whether the problem appears on specific servers? If so, can you please give us the list of servers and then add a new WireGuard key and test again with the new key?

If the above does not solve the problem, let's go back to the basic check list. Please make sure that:

• the listening programs are really running and listening to the correct ports
• the listening programs do not bind to the physical network interface, or any other wrong interface (if a bind option is available in the listening program settings)
• the listening programs have been launched after the VPN connection had been established successfully
• no packet filtering tool or antimalware tool block packets to or from the listening programs

Kind regards
 

[purplebored 0]

Hello, the problem exists on the Latvian, swiss, and swedish servers. I tried new wireguard keys, I even attempted to use OpenVPN. I will attempt later to once again create new wireguard keys I doubt something any tool is blocking them as I checked those ports on windows Linux and android.

[Staff 10014]

3 hours ago, purplebored said:

Hello, the problem exists on the Latvian, swiss, and swedish servers. I tried new wireguard keys, I even attempted to use OpenVPN. I will attempt later to once again create new wireguard keys I doubt something any tool is blocking them as I checked those ports on windows Linux and android.

Hello!

No problems are reported on the CH and SE servers and everything appears just fine. What are the listening programs?

Kind regards
 

[purplebored 0]

10 minutes ago, Staff said:

Hello!

No problems are reported on the CH and SE servers and everything appears just fine. What are the listening programs?

Kind regards
 

I for now only tried using soulseekqt and qbittorrent it works with the one open port but the other two don't work with it. I also tried checking if the port is open on your website and I tried a third party website too. Like I said in my initial post there is one port working it's just the fact that all those other don't want to work.

[Staff 10014]

6 minutes ago, purplebored said:

I for now only tried using soulseekqt and qbittorrent it works with the one open port but the other two don't work with it. I also tried checking if the port is open on your website and I tried a third party website too. Like I said in my initial post there is one port working it's just the fact that all those other don't want to work.

Hello!

We see that the packets are correctly sent to your node on every port but either they get a TCP RST or no reply is received, except for one port (we presume the one that you report as working). We confirm no problems on the server side. On top of the mentioned check list please review again the firewall rules and/or disable any anti-malware or packet filtering tool for a quick test.

Kind regards
 

[purplebored 0]

On 11/27/2024 at 4:47 PM, Staff said:

Hello!

We see that the packets are correctly sent to your node on every port but either they get a TCP RST or no reply is received, except for one port (we presume the one that you report as working). We confirm no problems on the server side. On top of the mentioned check list please review again the firewall rules and/or disable any anti-malware or packet filtering tool for a quick test.

Kind regards
 

Yeah no I checked all things which could be causing the issues and it still does not work. Now even the one working port seems to be broken.

[purplebored 0]

it seems that it started working after a while? I am not exactly sure what fixed them but it seems like most of them work

[dsiu98 0]

hi, just letting you know i had the exact same experience, and the newly opened port started working the next day for seemingly no reason.

[ss11 20]

The "working" is not something related to the VPN server.
When you register a port and configure port forwarding, immediately when you connect to the VPN the rule to port forward as per your configuration is applied immediately.

If you don't see the port actually opened from a remote side, there can only be two reasons:

- the application/daemon that is listening on that port (opening that port) is not yet up and running and/or not aware of the client VPN tunnel interface (tun0, wg0, whatever) or lacking the permissions to bind to that interface or some faulty binding configuration (binding to other IP addresses or interfaces or binding to IP addresses that do not belong to the VPN tunnel interface - they change in OpenVPN at every connect for example).

- if you try to test the port using the dyndns hostname provided by AirVPN (airdns*) , when you switch servers it takes time for the hostname to match the new server IP address(es) -you should clear the DNS cache from the device where you are trying to probe the port.

[purplebored 0]

10 hours ago, ss11 said:

The "working" is not something related to the VPN server.
When you register a port and configure port forwarding, immediately when you connect to the VPN the rule to port forward as per your configuration is applied immediately.

If you don't see the port actually opened from a remote side, there can only be two reasons:

- the application/daemon that is listening on that port (opening that port) is not yet up and running and/or not aware of the client VPN tunnel interface (tun0, wg0, whatever) or lacking the permissions to bind to that interface or some faulty binding configuration (binding to other IP addresses or interfaces or binding to IP addresses that do not belong to the VPN tunnel interface - they change in OpenVPN at every connect for example).

- if you try to test the port using the dyndns hostname provided by AirVPN (airdns*) , when you switch servers it takes time for the hostname to match the new server IP address(es) -you should clear the DNS cache from the device where you are trying to probe the port.

Ooh alight. Thanks for letting me know