Unable to login through ssh

I am unable to login through ssh.An error screen shot is attached for reference.kindly look into it.

7 Replies

Hey @gotoserver - sorry to say that I'm not seeing any screenshots on your post. That said, if you're having trouble logging into your Linode via SSH, there are a few things you can do to help troubleshoot.

We have another Community post that covers troubleshooting SSH issues in pretty good detail (Why can't I connect to my Linode via SSH?), but I'll try to give you a quick rundown of some options:

  • Reset your root password: If you're trying to log in as the root user, you can reset your root password from your Linode's summary page in the Cloud Manager. If you still can't login with your new password, there might be something else going on.

Tip: If you're trying to SSH as a limited user, you can reset the limited user password while logged in as root. Here's a link to a Nixcraft article that walks you through the process.

  • Restart your SSH service: If you know your username/password combo is correct, you can try logging into your Linode via the Lish console in the Cloud Manager and restarting your SSH service with the following command:
systemctl restart sshd

Once you've done that, close Lish and try connecting via SSH again.

  • Run a verbose SSH login attempt: If you're still running into issues after resetting your password(s) and restarting your SSH service, try running a verbose SSH attempt to get more detail on where the connection is breaking down. A verbose SSH command output will display each step of the login attempt and will give you some clues to work from:
ssh -vvv <user>@<IP address>

We have some nice documentation on how to connect to your Linode via SSH in our Getting Started guide. Should you still run into problems, you can also follow up with our Support team in a Support ticket.

I changed the password and after that hit the ssh commands and received the following error "Connection closed by 172.105.99.109 port 22".Error image link is here Click Here.
One more thing when i launch console from Linode strang error appear like this Click Here.Linode weblish required hostname and password for login. From where I get the se things?

@gotoserver --

I changed the password and after that hit the ssh commands and received the following error "Connection closed by 172.105.99.109 port 22".

It's very common (maybe even the default) to not allow root logins via ssh(1). You don't say what distro you're using so it's hard to tell. This is a security measure.

One more thing when i launch console from Linode strang error appear like this.

These are the normal console messages about the start of services at boot time. They're left over from boot time…not "errors" at all. lish/glish is the system console for your Linode.

Linode weblish required hostname and password for login. From where I get the se things?

I don't know what you're talking about here…

-- sw

Hi,
When you launch the console,it ask for hostname and password. unable to to login that. Please help my website is down and i am lossing client

You log into the console just like you log in at any other terminal or ssh(1) session…with your account name and password. On my console, I have:

Debian GNU/Linux 10 dave ttyS0
 
dave login: stevewi
Password: **********
 
Last login: Thu Oct 29 10:03:05 PDT 2020 from <IP address redacted>
 
Welcome to Dave -- <identifying info redacted>
12:13:47 up 10 days, 3:58, 0 users, load average: 0.03, 0.03, 0.00
Thu Oct 29 12:13:47 PDT 2020
 
<messages redacted>
 
[email protected]:~$

dave is the hostname; stevewi is my login. If you have disallowed root logins in ssh(1) you need to use root for your login and use root's password (because the only place you can log in as root is the console).

If you're going to try to repair your website, you probably want to log in as root (DANGER WILL ROBINSON! DANGER! DANGER!).

Logins at the console (which lish/glish represent) are accomplished no differently than logging in anywhere else or with ssh(1). Maybe the only difference is, that if you have public-key authentication set up, sshd(8) is supplying your login/password information for you. You cannot use public-key authentication to log in at the console because sshd(8) is not involved in that process at all.

Unless ssh(1) is down, you could accomplish the same thing as using your normal login account to login with ssh(1) and become root with su(1) or sudo(8).

-- sw

I have implemented the step that you are saying but still getting incorrect username and password. Can you please help me out and reset my username and password. My website is down and we are closing clients. Please help me out.

Just for your infromation we are using linode for 10 other website as well. We are not facing this issue on any other.

Please help us and reslove this issue ASAP

I don't know what to tell you… If you don't know your username and password, it's kind of hard for me to advise you on what to do next.

You probably rely on public-key authentication so you don't routinely enter your username/password (I do that too) so my best advice is to ask the person who set that up for you what your username/password are.

You can change the root password in the Cloud Manager. Perhaps changing this will give you access through the console as root so you can change your own password with usermod(8)

You write:

Just for your information we are using linode for 10 other website as well. We are not facing this issue on any other.

So? The fact that you have 10 other websites spread across a plethora of other Linodes is not really useful information.

You also write:

Please help us and resolve this issue ASAP

I don't work for Linode. I'm a volunteer here. I understand your predicament but I'm not responsible for it…and your urgency about "closing clients" does not encumber me at all. Your password didn't change itself (if, in fact, it actually changed)… I am metaphysically certain that you or someone else in your organization are responsible for your current situation.

I'm doing the best I can with the limited information you've provided.

Did you file a support ticket as jdutton suggested above? I suggest that be your next step…

-- sw

Reply

Please enter an answer
Tips:

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct