Jump to content
Not connected, Your IP: 216.73.216.134
Sign in to follow this  
anwnymos

Port Forwarding > No route to host (113)

Recommended Posts

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)
 

Share this post


Link to post
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
 

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Security Check
    Play CAPTCHA Audio
    Refresh Image
Sign in to follow this  

×
×
  • Create New...