After Latest Update: No SSH Access Anymore

O

open4biz

Verified User
Joined
Mar 22, 2009
Messages
125
I seem to have lost SSH access to my server. My environment is CentOS 6.4 64-bit, DirectAdmin and ConfigServer Firewall. I have the SSH access port set to something non-standard. Every time I try to connect I receive the following error from kitty:

"Server unexpectedly closed network connection"

After the latest DA update (1.43), it no longer wants to work. I checked the firewall settings and the correct inbound port shows that it should be open.

Any thoughts how I can restore access via SSH?

Thank you in advance,

Ansel Taft
 
Try to restart it through da admin. If not you have to contact your hosting provider to have them fix it.
 
SSH, the firewall, and DA services have all been restarted. I tried a full reboot later... none of which proved to be a fix.
 
Set the config firewall to test and restart it. Try to login. If it does not work try to get your noc to install a kvm for investigation.

I can initiate a console session right into my boxes without the need for a kvm because i use a remote access card (drac5) on all my servers which are dell poweredges servers that i colocate. That way i can work on the server in such an event, as if i was sitting in front of it with a crash cart. :o

Im also using the same exact setup as you Centos 6.4 x64 16gb ram on the new box and i dont think DA touches your sshd_config file after the inital setup/installation. So root and admin should still be present at the end of the file.
 
Last edited:
You could see if the log viewer in directadmin has access to /var/log/messages which is where sshd would be dumping its errors to. But there probably isnt much you can do to fix it.
 
The errors in /var/log/messages seemed to be for Apache, not SSH?

I was able to get a console to connect via my host's control panel. I grabbed a copy of the SSH error log here: /var/log/secure

Does this look funny?

Mar 27 13:07:12 server sshd[3092]: Server listening on 0.0.0.0 port [edited].
Mar 27 13:07:12 server sshd[3092]: Server listening on :: port [edited].
Mar 27 13:15:03 server sshd[3822]: refused connect from [work-ip] ([work-ip)

I'm not sure if something's wrong since it's "listening on 0.0.0.0" or "listening on ::"
 
"Set the config firewall to test and restart it. Try to login."

Test mode did not improve anything. I feel like the connection is passing through the firewall and for some reason SSH is hiccuping on the server end.
 
I am terribly sorry, and thank you all for your help, but it looks like somehow my work IP was in the /etc/hosts.deny list. I don't exactly know how it happened but I'm going to guess that I typed in the wrong password too many times and CSF/LFD locked me out. Sorry for [mostly] wasting your time.

Ansel
 
You must log in or register to reply here.
Back
Top