ANSWERED Solved! Port Forwarding > No route to host (113)

[anwnymos 0]

Have a working wireguard client AirVPN connection from my host and I set up port forwarding in order to allow incoming connections to a specific port.

When I press "Test open" I get the result: No route to host (113)

I think this error message hasn't anything to do with my setup specifics (open ports, firewall rules etc) but with the fact that the VPN peer I connect to cannot route traffic to the internal allocated address 10.x.x.x.

Am I missing something here?

(I can provide specifics but would prefer not to do it in public)
 

Edited ... by anwnymos

[Staff 10344]

2 hours ago, anwnymos said:

I think this error message hasn't anything to do with my setup specifics (open ports, firewall rules etc) but with the fact that the VPN peer I connect to cannot route traffic to the internal allocated address 10.x.x.x.

Hello!

Actually what you say is plausible, although puzzling. Please try to generate a new key in your AirVPN account "Devices" panel, adjust the "device" linked to the forwarded port accordingly and connect with the new key. Check whether the problem gets resolved or not. The new key will give you a different VPN IP address and this test could provide some clue.

Kind regards
 

[anwnymos 0]

Problem solved!

There might be some misconfiguration of the device private key because after successfully testing with the second key I edited/reviewed the connection details of the first key (on my side) and that worked too.
Now the Test shows: Open

Thank you for the help!

[Staff 10344]

44 minutes ago, anwnymos said:

Problem solved!

There might be some misconfiguration of the device private key because after successfully testing with the second key I edited/reviewed the connection details of the first key (on my side) and that worked too.
Now the Test shows: Open

Thank you for the help!

Thank you very much, we have scheduled an investigation on this strange issue. We're glad to know that the new key resolved the problem. If the problem re-appears, this time please do not touch the "problematic" key (just generate and use a new one), maybe it could help the investigation.

Kind regards