Page 1 of 1

Locked myself out of my VestaCP GUI and firewall CLI cmds ain't working ?

Posted: Mon Apr 30, 2018 7:31 pm
by rhyker2u
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:

Code: Select all

/usr/local/vesta/bin/v-add-firewall-rule allow X.X.X.X/32 11111 TCP blabla any 
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:
Error: invalid action format :: ALLOW
What I also tried is editing:

Code: Select all

/usr/local/vesta/data/firewall/rules.conf
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?

Re: Locked myself out of my VestaCP GUI and firewall CLI cmds ain't working ?

Posted: Mon Apr 30, 2018 7:55 pm
by rhyker2u
And ... fixed! :-D was scouring through the /etc folder, and ...

Code: Select all

nano /etc/iptables.rules
editted it there, rebooted server (not in the mood to master good ol' iptables cmds). And it works!

Still doesn't explain why the vesta firewall CLI cmds don't work. @skurudo can you enlighten us?

Re: Locked myself out of my VestaCP GUI and firewall CLI cmds ain't working ?

Posted: Wed Jun 06, 2018 7:46 pm
by vestabel
What am I doing wrong?