Jump to content


Photo

Port-forwarding "Error 111 - connection refused"


  • Please log in to reply
6 replies to this topic

#1 blueruin39

blueruin39

    Newbie

  • Members2
  • Pip
  • 7 posts

Posted 05 January 2019 - 10:43 PM

Not reachable on server IP over the external port [xxxxx], tcp protocol. Error : 111 - Connection refused.

Why am I getting this error message when I test forwarded ports? I've tried troubleshooting by eliminating variables such as changing servers, creating new forwarded ports, restarting, ect., but when I test forwarded ports I continue to get the above error message (when I hover over the black circle after the test).

 



#2 Staff

Staff

    Advanced Member

  • Staff
  • PipPipPip
  • 7792 posts

Posted 07 January 2019 - 12:00 PM

Hello!

 

Error 111 means "connection refused" and you get that error when packets from the Internet through our VPN server reach your node properly and are actively refused. The most common cause is a firewall dropping packets.

 

Kind regards



#3 blueruin39

blueruin39

    Newbie

  • Members2
  • Pip
  • 7 posts

Posted 07 January 2019 - 03:04 PM

Hello!

 

Error 111 means "connection refused" and you get that error when packets from the Internet through our VPN server reach your node properly and are actively refused. The most common cause is a firewall dropping packets.

 

Kind regards

 

A firewall on my end? Because I don't have one running. What steps should I take to troubleshoot this from here?



#4 go558a83nk

go558a83nk

    Advanced Member

  • Members2
  • PipPipPip
  • 1699 posts

Posted 07 January 2019 - 03:16 PM

Hello!

 

Error 111 means "connection refused" and you get that error when packets from the Internet through our VPN server reach your node properly and are actively refused. The most common cause is a firewall dropping packets.

 

Kind regards

 

A firewall on my end? Because I don't have one running. What steps should I take to troubleshoot this from here?

 

 

Are you using Eddie and is the listening server on the same machine running Eddie?



#5 blueruin39

blueruin39

    Newbie

  • Members2
  • Pip
  • 7 posts

Posted 07 January 2019 - 09:36 PM

I am using Eddie, yes.

 

The listening server is whatever server that AirVPN uses to test open ports on the Portforwarding page, but I also used canyouseeme.org.

 

The weird thing is that this problem is replicated across two of my systems (Linux and Mac), but on a third system (Linux), three ports are currently open and green.

 

So I am able to port-forward on one system, but not on the other two?

 

What is the common factor that would cause this to occur...



#6 go558a83nk

go558a83nk

    Advanced Member

  • Members2
  • PipPipPip
  • 1699 posts

Posted 07 January 2019 - 10:04 PM

I am using Eddie, yes.

 

The listening server is whatever server that AirVPN uses to test open ports on the Portforwarding page, but I also used canyouseeme.org.

 

The weird thing is that this problem is replicated across two of my systems (Linux and Mac), but on a third system (Linux), three ports are currently open and green.

 

So I am able to port-forward on one system, but not on the other two?

 

What is the common factor that would cause this to occur...

 

 

No, the listening server is whatever you're trying to forward a port to.  :)  If that's not up and running and listening on the port you've assigned in the port forwarding rule the test will fail.



#7 blueruin39

blueruin39

    Newbie

  • Members2
  • Pip
  • 7 posts

Posted 08 January 2019 - 12:01 AM

Roger that...because the port test cannot tell if the port is open if no traffic is flow through it?







Similar Topics Collapse

1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users

Servers online. Online Sessions: 13662 - BW: 49600 Mbit/sYour IP: 34.228.143.13Guest Access.