By cloudnine
I have been successfully running a Ubuntu 14.04 production server on D.O for nearly six months now. I couldn’t be happier with the level of support received from D.O staff and the excellent tutorials that helped me get going from scratch.
However, I cannot but think that D.O’s web based console access is its major problem area. In all these months of trying, I have only been able to get it working once or twice. Having reliable out-of-band access to the server is absolutely essential for an unmanaged service like D.O where the staff can’t login to your server when you are locked out of SSH.
Yesterday, I spent several hours trying to get console access to work without success after I was locked out of SSH. D.O Support were courteous and helpful, as always, but they obviously couldn’t login to fix the issue. I tried everything - accessing from a desktop, a laptop, a Macbook Pro, trying through Firefox, Safari and Chrome, adding incoming and outgoing rules in the Windows firewall to allow the suggested port range of 6000-7000, restarting my router to get a different dynamic IP for the internet connection to work around my IP being blocked by the server firewall - the works. Nothing helped until I was finally able to connect to SSH after restarting the router for the nth time.
D.O staff suggested that my ISP was blocking those ports, but I doubt it. The irony of the situation is that I am able to launch the web console of Linode (Lish) where I have a couple of servers without any issue at any time on any browser on the same ISP connection. It simply works.
So, my question is, why is D.O’s console access so troublesome and error prone when Linode can offer a similar service that works out of the box? And, why has this issue gone unresolved for so long? You only have to do a google search to find dozens of complaints on this issue going back two or three years.
I am not posting this as a rhetorical question but as a genuine concern. Heaven forbid running into a situation where I need out of band access to the production server and the console doesn’t work.
Is anyone using any tips or tricks to get console access working reliably?
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!
I personally never had any issues with DO’s Console - Ability to copy/paste would be nice though.
Few things I leant overtime about the console is,
- Some browser extensions can cause problems, such as AdBlock.
- If the screen is black, you can try clicking on the screen. If that doesn’t work you can try typing something. That usually fix the black screen issue for me.
- Looks like DO Console makes a connection on port 5000, you can try adding this to your firewall. - Not sure why 6000-7000 was suggested, maybe something internal?
- A reboot of the Droplet can help too if the server is out of sync for some reason.
What exactly happened when you tried to access the console?
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.