Jump to content


SSH "Socket bind failed on local address"

Linux SSH

Best Answer Guest_MuYiXiao_* , 14 April 2016 - 12:26 AM

Neither of them.

Check your /etc/hosts for the proper IP address of "localhost", it should be 127.0.0.1.

 

Unless you have a line containing

127.0.0.1	localhost

in your /etc/hosts, on any *nix OS, things will behave abnormally.

 

Bingo!   I have to muck about with my hosts file all the time, and I apparently deleted the first two digits of "home".  I completely missed that.  OOPS!

 

Thank you.  It's so nice when the answer is simple and easy to fix

Go to the full post


  • Please log in to reply
4 replies to this topic

#1 Guest_MuYiXiao_*

Guest_MuYiXiao_*
  • Guests

Posted 13 April 2016 - 08:15 AM

Running Fedora 21, KDE

I'm in china

 

Trying to connect via SSH.  I tried all 4 port options listed.  Same error.

 

I know SSH works (I'm using it right now).   In the AirVPN client, I authorize, it gets to local forwarding, and then kills.  Is this a setting in the client or is something happening with Fedora that's blocking it?

 

Spoiler


#2 giganerd

giganerd

    I shall have no title

  • Members
  • PipPipPip
  • 2478 posts
  • LocationGermany

Posted 13 April 2016 - 08:37 PM

. 2016.04.13 16:00:03 - OpenVPN > MANAGEMENT: Socket bind failed on local address [AF_INET]7.0.0.1:3203: Cannot assign requested address

That's the error. It must be 127.0.0.1. How does that happen? :o


Always remember:
There's a guide to AirVPN,

Amazon IPs are not dangerous here,
running TOR exits is discouraged,

using spoilers for your logs is the proper way to heaven.
Same issues are rare! Search for solutions and if not successful open your own threads.

~ Furthermore, I propose that your paranoia is to be destroyed. ~

 


#3 Guest_MuYiXiao_*

Guest_MuYiXiao_*
  • Guests

Posted 13 April 2016 - 10:22 PM

. 2016.04.13 16:00:03 - OpenVPN > MANAGEMENT: Socket bind failed on local address [AF_INET]7.0.0.1:3203: Cannot assign requested address

That's the error. It must be 127.0.0.1. How does that happen? :o

 

Okay.... that makes sense.  :)   Any idea if this is a client issue or a Linux issue?



#4 zhang888

zhang888

    Donald Trump of IT/Security

  • Moderators
  • 2205 posts

Posted 13 April 2016 - 10:26 PM

Neither of them.

Check your /etc/hosts for the proper IP address of "localhost", it should be 127.0.0.1.

 

Unless you have a line containing

127.0.0.1	localhost

in your /etc/hosts, on any *nix OS, things will behave abnormally.


Occasional moderator, sometimes BOFH. Opinions are my own, except when my wife disagrees.


#5 Guest_MuYiXiao_*

Guest_MuYiXiao_*
  • Guests

Posted 14 April 2016 - 12:26 AM   Best Answer

Neither of them.

Check your /etc/hosts for the proper IP address of "localhost", it should be 127.0.0.1.

 

Unless you have a line containing

127.0.0.1	localhost

in your /etc/hosts, on any *nix OS, things will behave abnormally.

 

Bingo!   I have to muck about with my hosts file all the time, and I apparently deleted the first two digits of "home".  I completely missed that.  OOPS!

 

Thank you.  It's so nice when the answer is simple and easy to fix







Similar Topics Collapse


1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users

Servers online. Online Sessions: 14065 - BW: 44685 Mbit/sYour IP: 54.81.254.212Guest Access.