My droplet keeps giving me 500 error. I reset the root password and when I try to login it forces me to set a new password. Right after setting the new password I get the following message:
Connection to [my.domain] closed.
When I try to access using the console, it shows the same process of password resetting, but after typing the new password, the concole blacks out and restarts, asking for login over and over again
After that I made a snapshot and it used up 25.8 GB, so it seems my droplet is full. I thought the login issue was related to error on saving logs or something like that, but…
Upgraded the droplet to increase its disk space (now it has more than enough) and sill get the same behavior.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
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.
Click below to sign up and get $200 of credit to try our products over 60 days!
Opened a ticket and the support team got the exact thing I had to do:
Now it is working fine. Got to extract my files and database content :D
If you type directly into the console, it may initially read your number keys incorrectly, as if the SHIFT key is pressed. For example, pressing the 2 key may enter @.
This happens only when typing. You can avoid the problem by copying the text, then pasting it into the console by pressing CTRL + v. You can also reset this behavior and ensure that your keystrokes are being received correctly by pressing SHIFT and CTRL a few times, then testing your number keys again.
Also, you can try disabling any add-block-related extensions in your browser or try loading the recovery console using an alternative browser.
This seems like an issue you’ll need to resolve using the Recovery Console. It’s possible the disk didn’t extend itself and it’s still full. In such cases, using the Recovery Console should be the only option:
Let me know how it goes.