Can't login using putty after upgrading to 6110
-
I am using the Fog account. This has always been the account I use. I can log in using the same credentials as always to the web interface, just not putty.
-
@Scott-Adams Try logging in as root, or another account.
-
Don’t have another user. Should I add one using the web console and see if I can log in using that?
-
System users (like when you connect via putty) and FOG web console users are two different things!
How did you install FOG? Most probably you logged in via root if you don’t know about a different account.
-
Don’t know of a root password. Don’t remember using one/setting one up when I installed fog server almost a year ago. The fog user account has always been the account we use to access the putty session and it just no longer works after the update.
-
I’m pretty sure you have to enable root, which I didn’t do. As I just use the Sudo command to do root level stuff, and I always use the password for my fog account.
-
Is ssh actually running on the server?
Updating fog in any regard has NO impact on what happens with ssh. Either the FOG password changed, and was unknown to have changed, or the ssh service isn’t running. As you stated you can login using a console connection, it feels more like the ssh service simply isn’t running, or another configuration change occurred that’s breaking other things.
-
Well, I’m the only one that can make changes to fog. I updated to the 6110 on Monday, 1/25.
I have not made any password changes to the account. I have rebooted the server, hoping that would restart any service, but it still does not. I am unable to log into the fog server.
-
My understanding is that you use “fog” as your login account for ssh and what not. (I generally recommend having a user that is not fog to manage the system precisely in case something goes wrong)
The Webgui login is entirely unrelated to the login you use for ssh and what not.
So, the only thing left to do if that’s your only account is to boot into recovery mode and change the password or add a new account and login using that info.
If you still can’t SSH after that then your SSH is misconfigured or broken.
-
@Scott-Adams Look inside Storage Management -> Storage Node -> User and Pass
Try with those credentials.
-
Thanks @Quazz! I did reset using recovery mode and can now log in.
I’m going to do another SVN update to try to resolve the No Disk Passed error. What should the new version be after the upgrade?
-
@Scott-Adams While you have access, you should create a backup account… like “admin” or something.
-
I did. Created a backup user to avoid this in the future. Thanks everyone for your help! I am up and running again.