• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Devaka Cooray
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Knute Snortum
  • Bear Bibeault
Saloon Keepers:
  • Ron McLeod
  • Tim Moores
  • Stephan van Hulst
  • Piet Souris
  • Ganesh Patekar
Bartenders:
  • Frits Walraven
  • Carey Brown
  • Tim Holloway

ERR_CONNECTION_REFUSED

 
Ranch Hand
Posts: 78
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi guys,

I am novice in linux.

I'm trying to access a linux machine.

https://187.84.228.66

But it returns the error message. ERR_CONNECTION_REFUSED

I used the a command to iptables -F and iptables -X. Even so, when I try to access it still gives the same error = ERR_CONNECTION_REFUSED

What can I do?

Thank.

Fernando
 
author
Posts: 23833
140
jQuery Eclipse IDE Firefox Browser VI Editor C++ Chrome Java Linux Windows
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

There may be various reasons for connection refused... possible reasons are...

  • The IP address does not exist
  • There is no route to that IP address (mis-configuration)
  • There is a firewall which is blocking access
  • There is no service listening on the port. For "https", the default port is 443.


  • Unfortunately, the error message does not provide enough information to tell you what the issue is. The error message simply states that it doesn't have access.

    Henry
     
    Ranch Hand
    Posts: 561
    1
    VI Editor Chrome Linux
    • Mark post as helpful
    • send pies
    • Quote
    • Report post to moderator
    Wow, something I actually know something about.

    My head ain't right at the moment but that error means 1 of 2 things:

    1)  You can't access that IP address
    2)  You're hitting a port where nobody is listening.

    How to fix:

    1.  Ping the IP.  If you can reach it goto step 2.  Otherwise figure out why you can't ping it.
    2.  On the remote system (note:  remote could be the same box if your IP is 127.0.0.1, commonly known as localhost.  Hint:  this is a great way to debug your stuff) ensure your server is running.
        a)  It's not.  Start it.
        b)  It is.  Debug it  That is, debug the server, not the client.
        c)  You don't own the IP address.  This is a whole 'nuther issue I won't touch here.  But, um, cough, nmap -sP IP/8 could be a start.
     
    • Post Reply Bookmark Topic Watch Topic
    • New Topic
    Boost this thread!