Restarting SSH shows old shared hosting sitename invalid user
AnsweredHi,
I used to be on a shared server and all sites were under one plan and one main site.
Lets call that old shared site name for this example.
Then i moved from shared hosting to a VPS and my hostname is completely different, my OLD_HOSTING_NAME is just a domain now like the others, nothing special.
I noticed today that when i restart SSH i get the following example below, and my OLD_HOSTING_NAME is seen as a invalid user. I have a ticket open with my host, but they never tell me how to do stuff, they just do it, and i want to learn how to fix this myself.
I am thinking they forgot to change a file.
Here is what i get... i changed all the ports and private data for protection.
Startup Log
Aug 16 02:51:02 server5.example.com systemd[9]: Starting OpenSSH server daemon...
Aug 16 02:51:02 server5.example.com sshd[2222]: Server listening on 0.0.0.0 port 55.
Aug 16 02:51:02 server5.example.com systemd[9]: Started OpenSSH server daemon.Log Messages
Aug 16 02:50:58 server5 sshd[9999]: Connection closed by invalid user OLD_HOSTING_NAME 000.000.000 port 99999 [preauth]
Aug 16 02:50:58 server5 sshd[9999]: Invalid user OLD_HOSTING_NAME from 000.000.000 port 99999
Aug 16 02:50:34 server5 sshd[9999]: Connection closed by authenticating user root 000.000.000 port 99999 [preauth]
Aug 16 02:50:31 server5 sshd[9999]: Connection closed by invalid user OLD_HOSTING_NAME 000.000.000 port 99999 [preauth]
Aug 16 02:50:30 server5 sshd[9999]: Invalid user OLD_HOSTING_NAME from 000.000.000 port 99999
Why is it showing my old hosting name. Any suggestions would be great, then i can look at this before they fix it so i know what the issue was.
Thanks :)
-
Its because i changed usernames
Well here is what they (my host) said...
In such cases, you need to create a new SSH, you can use your old SSH key only if you use the same Username that was on the Shared hosting.
Here is a detailed illustrated guide on how to do that:
1 -
Anyway since i have SSH disabled for the server, i just had to go into WHM -> Security Center -> Manage Roots SSH Keys and create a new key and then authorize it and it seems like that has fixed the issue. :)
0 -
I'm glad the host was able to help clear things up!
0
Please sign in to leave a comment.
Comments
3 comments