Locked myself out of my VestaCP GUI and firewall CLI cmds ain't working ?
Posted: Mon Apr 30, 2018 7:31 pm
Got a new modem from my ISP, that comes with a new IP. If I had known upfront (and should have) then I would have done things differently ... obviously :P As I find myself stuck right now by not being able to login on my VestaCP as I limited access on a /32 range.
I follow the guidance in this VestaCP post: Add Firewall Rules via Vesta CLI, however everytime I run a cmd CLI cmd through SSH, like this:
I tried my own IP, also tried 0.0.0.0/0 ... but no matter what I try through CLI, I get an error saying:
with the new correct values, and then reboot the server. Thusfar unable to gain access.
What am I doing wrong? And how can I regain access?
I follow the guidance in this VestaCP post: Add Firewall Rules via Vesta CLI, however everytime I run a cmd CLI cmd through SSH, like this:
Code: Select all
/usr/local/vesta/bin/v-add-firewall-rule allow X.X.X.X/32 11111 TCP blabla any
What I also tried is editing:Error: invalid action format :: ALLOW
Code: Select all
/usr/local/vesta/data/firewall/rules.conf
What am I doing wrong? And how can I regain access?