shell problem, can't log in anymore. can anyone help?

[kigoobe]

Well, this is what happened. I was reading different posts here and there, and then did the following changes in my server

1. Changed the IP to shell
2. Change the port
3. Denied direct root access

Now I wanted to get something installed in my server thro' the server guys, and so decided to put everything back, to make things easier for them, so

1. I commented out the direct root access line
2. Changed the port back to 22
3. Changed the IP back to what I was given at the beginnig
4. /etc/rc.d/init.d/sshd restart

I then did exit to come out from my putty and tried to log in again by double clicking on my desktop putty icon. Result: I am getting this >

Any help guys? I am blocked since this morning, its more than 13 hours now ...

Something more. Earlier I have added a list of IPs in the allow list. IPs that my host company gave me for my dedicated server. Now can this be an issue, that I not able to enter my account as my firewall is refusing everyone who do not belong to that IP? And my home computer with dynamic IP is not in the list of course.

Any idea? Thanks for your time guys, I appreciate that.

 

[kigoobe]

Hi JayH38, thanls for the link (it's not working for the moment). I will have a look at it as soon as it's available. Thanks a lot once again.

 

[jayh38]

Try this first... if it doesnt work, you will need to contact your data center.

http://11.22.33.44:2086/scripts2/doautofixer?autofix=safesshrestart

 

[jayh38]

Hi JayH38, thanls for the link (it's not working for the moment). I will have a look at it as soon as it's available. Thanks a lot once again.

Ahhh.. I did not think I would have to explain.. But you put your own server IP address in place of 11.22.33.44

try that

 

[kigoobe]

Hi Jayh, thanks, in fact I overlooked the port and thought you are giving me a tutorial link. Sorry about that.

I had to contact my datacenter guys who fixed the problem, and told it was because of my iptables ...

 

[jayh38]

Hi Jayh, thanks, in fact I overlooked the port and thought you are giving me a tutorial link. Sorry about that.

I had to contact my datacenter guys who fixed the problem, and told it was because of my iptables ...

Ahh.. Glad you are back running. In the mean time, you can do yourself this favor and install this little gem for future mishaps like this.

http://www.configserver.com/cp/cse.html

 

[kigoobe]

Thanks Jayh. I am using their mailscanner ... but this may be a bit risky ... but still a very useful tool ...

thanks a lot.

 

[jayh38]

I am curious why you would consider a file browser risky?