The “control panel” option is not even showing up when logging into Digital Ocean. When trying to SSH into website server using Cyberduck I get a timeout. How can I even access Ubuntu to be able to fix the upgrade and complete it? Cannot access website.
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.
Sign up for Infrastructure as a Newsletter.
Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Thank you. Perhaps you were referring to the following information, but I just needed more detail, as I did not realize that there was more than one way to access the console from the droplet. I was trying the “more” dropdown that displays on the right hand side of the screen for the droplet, but when clicking the dropdown, the word “console” was not even displayed.
This was a link we were sent from a ticket to help us. Which is probably what you were referring to.
https://www.digitalocean.com/community/tutorials/how-to-use-the-digitalocean-console-to-access-your-droplet
In addition to this link above, I am adding just a little more information that might help someone else in the future or me again if I forget.
By clicking on the droplet highlighted name when logging into Digital Ocean, another screen is displayed showing various options including “access”. By clicking the word “access”, the information referred to in the community tutorial is displayed allowing direct access to the console. What a relief. Thank you.
Simply use the console on your droplet information page. Type something in that window and if the console doesn’t come up close it and try again.
Thanks again to those who helped put us on the right track. For those struggling with this in the future: After being able to “access” the console as described above. We did:
sudo apt-get update sudo dpkg --configure -a sudo apt-get upgrade -f sudo service apache2 restart
All is now up and running. Thanks a lot for the help!!