Thank you all, the problem has been resolved, there was an issue with the operation method, after retesting a few times it finally succeeded, and as for the reason I couldn’t figure out, it seems consistent with the previous operation method.
1 Like
Everything’s messed up. It says the reset was successful, the password has been sent to the email, the test is finished, and the email module is delayed or broken, so the email isn’t received.
Try key login
Haha, the email crashed, it’s been like this for a long time. Let’s create a key.
If the key worked, I wouldn’t be coming out to ask for help; the key has never successfully logged in.
The key can’t log in either; what’s the situation? We’ll have to get a senior to take a look for you.
Emails often fail to send; it’s best to use a key.
Everyone logs in with a secret key, why do you insist on using passwords?
This email is indeed very abnormal.
I previously reset it around 1 a.m., and the email was sent successfully, but I’m not sure if that’s relevant.
You might receive the email tomorrow; the mail service may have sent it when it automatically restarts at midnight often delayed by half a day, up to a day.
Time is the best way to solve problems, wait for email to send the login password, log in, rather than creating this SSH key now.
SSH keys are safer and more convenient, right?
You might be wrong. My emails often get lost. Even if it’s already midnight, they may not be sent from the previous backlog; most likely they are discarded.
I was using an SSH key for my shell, but suddenly I couldn’t log in anymore. Since I hadn’t enabled root login, I had to delete it and start over!
Also, what tool do you use for SSH? When refactoring, choose key‑based login, then copy the key and save it in a notepad.
When using the tool, import your key.
to watch
You probably forgot to select SSH when you rebuilt; I had the same issue when I rebuilt yesterday.
1 Like