
29th December 2005, 14:57
|
|
Member
|
|
Join Date: Oct 2005
Posts: 63
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
SSH Remote Login Not Working Anymore!
For several months, I was able to login to my ssh account without any problems. I changed the default port to xxxx (do not want to reveal this port for security reasons).
Anyways, a couple days ago, I restarted my server, and now, I am unable to login to the SSH server. I am 100% sure I am connecting to the right port and ip address. I am also sure that the port is open to connections. I know this because I can go to to a port scanning site and it says that the ssh port is open.
I checked the sshd_config settings and the correct port is open.
What other settings should I check?
|

29th December 2005, 15:16
|
|
Super Moderator
|
|
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 31,872
Thanks: 689
Thanked 4,182 Times in 3,201 Posts
|
|
If you run "netsat -tap", is your sshd daemon listed there, listening on your custom port?
|

29th December 2005, 15:22
|
|
Member
|
|
Join Date: Oct 2005
Posts: 63
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
it shows the following:
tcp 0 0 *:xxxx <--this is my custom port *:* LISTEN 1928/sshd
Is that right?
Quote:
|
Originally Posted by till
If you run "netsat -tap", is your sshd daemon listed there, listening on your custom port?
|
|

29th December 2005, 15:30
|
|
Super Moderator
|
|
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 41,665
Thanks: 1,896
Thanked 2,591 Times in 2,443 Posts
|
|
Does your firewall maybe block that port?
|

29th December 2005, 15:56
|
|
Member
|
|
Join Date: Oct 2005
Posts: 63
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
To the best of my knowledge, it looks like the port is open and there is no firewall that is blocking that port.
Is there a way for me to verify this?
Quote:
|
Originally Posted by falko
Does your firewall maybe block that port?
|
|

29th December 2005, 17:53
|
|
Super Moderator
|
|
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 41,665
Thanks: 1,896
Thanked 2,591 Times in 2,443 Posts
|
|
Quote:
|
Originally Posted by kisong
To the best of my knowledge, it looks like the port is open and there is no firewall that is blocking that port.
Is there a way for me to verify this?
|
Please post the output of
|

30th December 2005, 20:45
|
|
Member
|
|
Join Date: Oct 2005
Posts: 63
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
PAROLE tcp --anywhere anywhere tcp dpt:ssh
That's not the whole output, but I think this should suffice.
Quote:
|
Originally Posted by falko
Please post the output of
|
|

30th December 2005, 20:54
|
|
Member
|
|
Join Date: Oct 2005
Posts: 63
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Solved!!
SOLVED. I added the xxxx SSH port to be opened within ISPConfig.
How did this setting get changed? Removed? Destroyed?
Does this happen every time the server is restarted?
Quote:
|
Originally Posted by kisong
PAROLE tcp --anywhere anywhere tcp dpt:ssh
That's not the whole output, but I think this should suffice.
|
|

30th December 2005, 23:36
|
|
Super Moderator
|
|
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 41,665
Thanks: 1,896
Thanked 2,591 Times in 2,443 Posts
|
|
Quote:
|
Originally Posted by kisong
SOLVED. I added the xxxx SSH port to be opened within ISPConfig.
How did this setting get changed? Removed? Destroyed?
|
What do you mean with that? You changed the SSH port, but you cannot expect the firewall to recognize that and adjust itself to the new port...
Quote:
|
Originally Posted by kisong
Does this happen every time the server is restarted?
|
If you've enabled the ISPConfig firewall, it will be started whenever the server boots (of course, with the settings you specified in the web interface). Just make sure that your system doesn't start a second firewall that interferes with the ISPConfig firewall.
|

3rd January 2006, 15:34
|
|
Member
|
|
Join Date: Oct 2005
Posts: 63
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
The reason I said this is because prior to restarting the server, the port was set to xxxx and the firewall for ISPConfig was set to the same port (again, I'm hiding the actual port number for security reasons).
Before restarting the server, I was able to login with no problems.
The problem started when I restarted the server. Somehow, ISPConfig lost the firewall settings I set and replaced it with a default firewall setting.
Does that make sense?
Quote:
|
Originally Posted by falko
What do you mean with that? You changed the SSH port, but you cannot expect the firewall to recognize that and adjust itself to the new port...
If you've enabled the ISPConfig firewall, it will be started whenever the server boots (of course, with the settings you specified in the web interface). Just make sure that your system doesn't start a second firewall that interferes with the ISPConfig firewall.
|
|
| Thread Tools |
|
|
| Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT +2. The time now is 01:18.
|
|
Recent comments
1 day 1 hour ago
1 day 3 hours ago
1 day 5 hours ago
1 day 6 hours ago
1 day 8 hours ago
1 day 9 hours ago
1 day 10 hours ago
2 days 2 hours ago
2 days 3 hours ago
2 days 7 hours ago