Related

LAMP CSS broken after installing SSL Question Question
How do I log into console with SSH key with passphrase. It keeps saying incorrect login. I'm trying to login from DO console not putty. Question Question

Question

WHY I can't login with SSH key after create droplet from snapshot?

Posted June 26, 2020 699 views
LAMP StackUbuntu 18.04

I’ve created a droplet using a snapshot from the old droplet. (use ssh same as existing droplet)
But I can’t log in with the same credentials.
But I’m able to log in control panel’s access console. (I’ve checked with ufw status. But found not an issue)
But I need to login in with that same credentials to use as SFTP login in WinSCP.
After log in my old droplet there shows Your LAMP website: http://157.xxx.xxx.42 . But after login in access console in the newly created droplet (snapshot of old one), there is nothing like that.
I think it will show up the ip of the droplet where I can see doplet default page (http://ipaddress/index.html)
But I can’t found any ip see screenshot.

plz let me know why this is happening? and better way to do my task (clone droplet)
advance thanks.

see image

Add a comment
alaminShark
By:
alaminShark

Related

LAMP CSS broken after installing SSL Question Question
How do I log into console with SSH key with passphrase. It keeps saying incorrect login. I'm trying to login from DO console not putty. Question Question

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
1 answer
alexdo June 27, 2020

Hello, @alaminShark

What you can do is to check if your ssh_key is added in the authorized_keys file on your new droplet. You can access the droplet via the console in your DigitalOcean account and from there cat the file:

`cat ~/.ssh/authorized_keys

If your ssh key is not present then you can add it by following this tutorial:

https://www.digitalocean.com/docs/droplets/how-to/add-ssh-keys/to-existing-droplet/

If you’re still experiencing some issues to access the droplet via a ssh client you can double check if the Droplet is not blocking connections on port 22 by using telnet for example:

telnet IPaddr 22

As for your other question, the best way to clone your droplet is to use the snapshots option (basically what you’ve done). The content of your new droplet should be identical to your production one. If you see some differences, I will recommend you to take another snapshot and repeat the process again.

Regards,
Alex

Reply Report

Related

Looking for something else?

Ask a new question Search for more help