So as the tittle says, the integrated HestiCP firewall doesn’t actually block or open the ports I would need or don’t want to be exposed, my machine is essentially running without any firewall at the moment.
I just recently installed Microbin and noticed that I could access it instantly on port 81, port 81 isn’t in the firewall list of HestiaCP, so now I’m kinda worried that I’m running my Ubuntu 24.04 server without any kind of firewall, IP tables are showing up in the list but literally nothing is happening I even tried blocking port 22, and I still can ssh into the server.
I’m using UFW normally, so maybe it’s just because I don’t know how iptables itself works, but it still seems really weird.
Here is the ssh command result for iptables and the second is the Hestia firewall page
Show the output of these commands (don’t share an screenshot, copy/paste the output, select it and click on button </> to format it):
iptables -S -t nat
iptables -S
Are the hidden IPs the ones used by your server, or is one of them the public IP you are using to connect to your server? Because that would explain why you can connect to port 81 from an external network.
By going to the Pastebin itself, then it struck me that I never opened the port, but I could access it, it does the same if I go with the IP and when I test it on
the port checker
Hmm! I didn’t spot it before yeah must be it, now that I think about it, their thing is basically a 1 time run installer script that uses docker hub (from what I understood from the GitHub) so it must be it yeah, thanks, but what about port 22 for ssh ? Shouldn’t I lose access to ssh if I block port 22 on Hestia CP ? Or is there yet another rule I missed
Yeah i don’t know much with iptables I’m just starting out in using a control panel like Hestia or any for the matter, and was only doing docker and directly on the machine for the nginx or panels like Pterodactyl using UFW or firewalld, so thanks for your help
If you are already connected, no. If you try to connect using a new session, yes, you should be blocked. Indeed right now port ssh is not open.
❯ check_ports 5.175.249.234
[...]
PORT STATE SERVICE REASON
21/tcp open ftp syn-ack ttl 52
80/tcp open http syn-ack ttl 52
81/tcp open hosts2-ns syn-ack ttl 51
443/tcp open https syn-ack ttl 52
8083/tcp open us-srv syn-ack ttl 52
