Firewall Caused Massive Issues - Lost ssh login ability

[marijuanatech]

I updated Vesta yesterday and had a few issues right off the bat that were fixable. I then realized that one of my other services wasn't working, so I added a rule to the firewall...

I didn't notice that the ssh port pre-configured in the firewall was incorrect.

I didn't notice that the vestacp port pre-configured in the firewall was incorrect.

I've changed the default port for both of these.

I've now lost access to both of these services. How do I go about fixing this? I can reboot the server into a Ubuntu recovery console if needed.

Uggh

[marijuanatech]

Fixed my issue my utilizing a backdoor I left myself. Hopefully nobody else runs into this issue! The upgrade should really check your current VestaCP port and maybe ssh port before making iptable rules that specifically block it!

[Milka]

SO basically what happened is you changed your firewall rules without paying attention to the existing rules, shut yourself out of your system, and now you blame Vesta for your own mistake? lol

;-)

[marijuanatech]

No, this all happened by running apt-get upgrade. The upgrade reset the port values and blocked me before I could even login once. I'm not blaming vesta, I'm documenting a problem that knocked out two of my servers.

[Milka]

you changed the ports though.

[marijuanatech]

Months ago, following instructions on here. I'm just saying it should allow the port that's currently being used, rather than filling those with defaults on upgrade.

[Milka]

Months ago, following instructions on here. I'm just saying it should allow the port that's currently being used, rather than filling those with defaults on upgrade.

true.

[marijuanatech]

Trust me, I'm not blaming vesta for shit. It's amazing software and the fact that it's open source is beautiful! Thanks for your input, Milla, I'll be more careful in the future.

[Milka]

Cool!

Please be careful with that backdoor you left open; you wouldn't want anyone else but you using that!