Vesta Control Panel - Forum

I have tried this multiple times with the latest version of VestaCP (0.9.8-18) on CentOS 7.4 (DigitalOcean).
The installer works fine, and the vesta CP is on.
I tried everything from vesta restart to server reboot, but it didn't work and most funny thing was, in some instances the panel was accessible from other droplet from DigitalOcean using VNC.

In the end I disabled FirewallD: and it worked, can someone tell me what's wrong? is it a bug in vesta itself because I used Vesta 2-3 months before this and it worked fine.

This also happened to me. I tried FirewallD disabled but it did not work :'(

Oh! I forgot to mention that, I also changed the default port for CP:

https://www.plothost.com/kb/change-vesta-port/

shailendra wrote: ↑

Thu Apr 12, 2018 7:52 am

I have tried this multiple times with the latest version of VestaCP (0.9.8-18) on CentOS 7.4 (DigitalOcean).
The installer works fine, and the vesta CP is on.
I tried everything from vesta restart to server reboot, but it didn't work and most funny thing was, in some instances the panel was accessible from other droplet from DigitalOcean using VNC.

In the end I disabled FirewallD:

Code: Select all

service firewalld stop

There was a mass attack on vestacp in digital ocean couple fays ago. The malware use port 8083 as the entry port, so they still totally close that port in all their network, dont know when they will opened again.
https://www.digitalocean.com/community/ ... l-8th-2018
Meanwhile you have to use another port for your vestacp.