@Daz

The first time it did login. But it doesnt login anymore. It was late in the night yesterday when it worked the first time, and I thought I will do the key generation part today. However after a long wait, it doesnt seem to work now though. SSH and sftp doesnt login. Is it something like a one time login?

@Daz

I finally had no choice. I typed the public key manually. Beat that Took a solid 1 hour of patient effort for 2 people, one to read out and one typing, with a verification to cross check. Now it works like a charm. Thanks a lot.

Hello. I'm new to the forum, but found this post which applies to us. We have been using SFTP for about an year and no issues. All of a sudden we can't get in. Site is accessible via SSH, but SFTP is dead.

Any ideas? I went through some steps w/ linode support, but still no good. Please help! Thanks

@rsamee

Did u try this? This is what solved the problem for two of us facing this problem

The workaround is simply to use puttygen to generate keys. Have a google around.

Then in your home directory if one does not already exist, create a directory .ssh

The key that goes on the server needs to be pasted into a file authorized_keys in the .ssh directory.

Then reconfigure putty or whatever you are using to use the keys to auth.

Mine goes straight in, no problems.

Its far more secure anyway, you can then go on to switch of password authentication later if you wish.

Let me know if you need any help.

@maxim. Thank you for the response.

I haven't tried that yet. What's strange is:

1) worker in Pakistan = can no longer access
2) worker in Dominican Rep = can no longer access
3) worker in China = CAN access with no issue

I checked the firewall, nothing. No IPs blocked


How would I access my home directory now to paste those files, etc. Are you able to continue using SFTP via FileZilla? Thanks again!

@rsamee

We had the exact same problem. People from India, Pakistan, UAE couldnt access it. It was not an issue with the network from which you were trying to connect. As a matter of fact, we even had our linode migrated to another location on the same datacenter and that didnt solve the issue either. We are still not sure what caused the issue, but we do have a workaround for it. We use sftp too and it was blocked due to the problem.

And after you have done the steps mentioned above, you can use the key with any ftp such as filezilla or winscp to login.

And regarding your question how to access the console since you cant access ssh. I believe you are using linode. In the linode manager, you have a lish console under remote access section, which would work even if you are facing the issue.

If you need help add me on gmail chat at maxim@inovvorx.com and I will guide you over chat.

@rsamee

I didnt read that you had mentioned that you can access SSH (my access to SSH was also denied). If that is possible, you can create the file using commands over your console and paste the contents there.

Our server admin from Ukraine reinstalled ssh/pam. Everything works again. Victory!

Let me know if someone needs his services. He might be able to do it for like $25 per box.

Spot a problem with this one:

Someone joins a high value hosting company forum attracted to a topic about ssh issues and two days later suggests a sysadmin from Ukraine to fix the problem.

My apologies to said someone if he or she is legit, it's just that the above sentence, especially if read aloud, made me rofl.

@maxim

Strange thing is my developer in China can access it w/ no problems. I can access SSH also via putty, but filezilla and winscp won't connect. I was also reading online and someone said that filezilla servers are hosted on comcast, which could be causing the issue.. but I don't know about that.

@cbrands
I contacted my db guy already, but if you could get your server admin in touch w/ me that would be great! I can't afford to lose any more time as I have a live site deadline in less than 2 weeks! Please PM me his/her info.

Appreciate all of the help! Glad to know you can 'lean' on community members

@Azathoth

Well at least they FIXED the problem.

The rest of this thread is all about ignoring the actual problem and their exciting new workaround called "keys" (wow, who'd a thunk there was a better way of securing SSH). Nothing like putting a bandaid on your box and calling it done.

If someone manages to solve this can you please share it. I need the fix

Who's putting bandaids on and calling it done then?

My server admin restarted SSH and that resolved the issue. Not sure why it needed to be restarted, but it worked for me!

I know others haven't had that luck, but all the best figuring this out if you don't have a resolution yet.

You're easily amused.