Page 1 of 1

I can't access the Vesta Control Panel

Posted: Sun Apr 08, 2018 11:32 pm
by mrkidgrave
Hey everyone, today I did
apt-get update
apt-get dist-upgrade

This installed an update for Vesta CP. However, I can access all of my websites perfectly fine, but I can't access the Vesta Control Panel when I go to https://ipaddress.com:8083

Please help. Thanks!

Re: I can't access the Vesta Control Panel

Posted: Sun Apr 08, 2018 11:55 pm
by mrkidgrave
According to Digital Ocean, "Our Engineering and Trust & Safety teams took action to block TCP/8083 and stop outgoing traffic from affected Droplets. These mitigation efforts have fully resolved the networking issues impacting our NYC1 and SFO2 regions, and users should now be able to access the site normally. If you continue to experience issues, please open a ticket with our support team.

Though the networking issues have been resolved, TCP/8083 will remain blocked for now. Additionally, users with VestaCP software installed on their Droplets may be vulnerable to exploitation."

Re: I can't access the Vesta Control Panel

Posted: Mon Apr 09, 2018 2:23 am
by MAN5
Yes. As of now, DigitalOcean blocked the outbound 8083 from most of their droplets to prevent spam. Be patience, as long as still our websites are works well.

Or you need to change vestacp port of 8083 to something else to manage. But advisable not to do for couple of days as there is a severe exploit is going on.

Re: I can't access the Vesta Control Panel

Posted: Mon Apr 09, 2018 1:22 pm
by supersuphot
I use DigitalOcean and have this problem too, just wait or change to another port for now.

If you're using DigitalOcean check this post for more update
https://www.digitalocean.com/community/ ... l-8th-2018

Re: I can't access the Vesta Control Panel

Posted: Mon Apr 09, 2018 2:37 pm
by n0x
Yep, DigitalOcean blocked port 8083 across all zones - Took me ages to figure out that it wasn't my firewall!

Change the port by following: viewtopic.php?f=10&t=16585&p=68940&hilit=8383#p68940

Then you can access on the new port with no issues (also make sure you update to 0.9.8-20 before changing the port), you can do that with:

Check current version:

Code: Select all

v-list-sys-vesta-updates
If not, 0.9.8-20 then run the following from CLI:

Code: Select all

v-update-sys-vesta-all
That has the patch for the attack that was launched on Saturday 7th April that caused ports 8083 to be blocked in the first place.