The console does not require any additional software but will use a random port to connect the HTML client with the vnc service. Since multiple services are run per-hypervisor the port used is a random one usually in the 6000-7000 range.

Okay, thanks - it’s still rejecting the request when I attempt to connect - with the above mentioned error.

Same problem also. I cannot open console from office due to this as office only allows port 80 and 443, this is disadvantage for me

Is there a workaround to pass through with the corporate firewall(proxy, user settings) & access console.

Any help is much appreciated.

+1 Also having this issue. I locked myself out with the firewall.

I had this problem. I forgot my user password for one droplet, but knew the root. Root login was disabled through SSH, so my only option was to login under root user using the console.

It turned out that my ISP is blocking 5000 port. I had to use Wi-Fi hotspot on my phone and access Internet via cell operator. Only then I was finally able to use the console.

I’m thinking about setting up some VPN on one of my droplet and use it for Internet access for such cases.

P.S. To test port 5000 connectivity you can simply use this site http://portquiz.net/