Can't Access Vesta Panel On Custom Port After Update

One of my hobby servers runs VestaCP on it. For some odd reason, after an update, I was unable to load the Panel using either the custom port I had set nor the default one.

The Vesta service was indeed running though, so I wasn't entirely sure what the issue was.

The solution was to add a firewall rule to the custom port again. I am not sure why the update would have removed the rules, but creating it again fixed my issue:

v-add-firewall-rule ACCEPT 8098 v-update-firewall

And just to be sure, restart the VestaCP service:

service vesta restart

For anyone wondering how to set a custom port for Vesta you simply have to change the port in the nginx config file located at: