Can't open VestaCP after VPS Reboot - clean install Topic is solved

[blackside]

Hi there!

Yesterday I did several clean installs on Vultr and Digitalocean:

Latest versions of CentOs + Latest VestaCP version
I've tried both Nginx+Apache and Nginx+Php-Fpm configurations

Everything works fine ......until I reboot my VPS!
All my browsers say: "Can't establish a connection" or "Connection timed out"..... while trying to access VestaCP.

although vesta, nginx etc. have "active" status while checking via terminal.

I know that Digitalocean has changed port from 8083 to 5600 - so I used Vesta on 5600, but still no success :(
Adding new domains, setting up SSL etc. also won't help...

Anything changed in the latest VestaCP update? Why does it brakes after clean installs just after Restarting the VPS?

Many Thanks for your help!

[gmalets]

Hi,
Looks like all this threads are related to your question.

viewtopic.php?f=10&t=17257
viewtopic.php?f=10&t=17236
viewtopic.php?f=10&t=17207
viewtopic.php?f=28&t=17218

In short, try to manually restart iptables "systemctl restart iptables"

[blackside]

Worked for me!
Many thanks! :)