I install update version HestiaCP 1.4.1 on VPC Server. All everything is ok except iptables service. When i restart vpc then iptables service stopped then need to start manually by click start or restart button from panel. Also start by this command “/usr/local/hestia/bin/v-update-firewall”
How to solved this problem “iptables service automatic start after reboot vpc”?
[Sun May 16 01:11:19.794162 2021] [ssl:warn] [pid 813:tid 140467802911872] AH01909: 10.255.255.248:443:0 server certificate does NOT include an ID which matches the server name
[Sun May 16 01:11:19.794390 2021] [mpm_event:notice] [pid 813:tid 140467802911872] AH00489: Apache/2.4.46 (Debian) mod_fcgid/2.3.9 OpenSSL/1.1.1d configured – resuming normal operations
[Sun May 16 01:11:19.794399 2021] [core:notice] [pid 813:tid 140467802911872] AH00094: Command line: ‘/usr/sbin/apache2’
[Sun May 16 01:11:20.056531 2021] [mpm_event:notice] [pid 813:tid 140467802911872] AH00493: SIGUSR1 received. Doing graceful restart
[Sun May 16 01:11:20.114853 2021] [ssl:warn] [pid 813:tid 140467802911872] AH01909: 10.255.255.248:443:0 server certificate does NOT include an ID which matches the server name
[Sun May 16 01:11:20.115200 2021] [mpm_event:notice] [pid 813:tid 140467802911872] AH00489: Apache/2.4.46 (Debian) mod_fcgid/2.3.9 OpenSSL/1.1.1d configured – resuming normal operations
[Sun May 16 01:11:20.115215 2021] [core:notice] [pid 813:tid 140467802911872] AH00094: Command line: ‘/usr/sbin/apache2’
[Sun May 16 01:11:20.258505 2021] [mpm_event:notice] [pid 813:tid 140467802911872] AH00493: SIGUSR1 received. Doing graceful restart
[Sun May 16 01:11:20.316835 2021] [ssl:warn] [pid 813:tid 140467802911872] AH01909: 10.255.255.248:443:0 server certificate does NOT include an ID which matches the server name
[Sun May 16 01:11:20.317105 2021] [mpm_event:notice] [pid 813:tid 140467802911872] AH00489: Apache/2.4.46 (Debian) mod_fcgid/2.3.9 OpenSSL/1.1.1d configured – resuming normal operations
[Sun May 16 01:11:20.317117 2021] [core:notice] [pid 813:tid 140467802911872] AH00094: Command line: ‘/usr/sbin/apache2’
[Sun May 16 01:12:30.557522 2021] [mpm_event:notice] [pid 813:tid 140467802911872] AH00493: SIGUSR1 received. Doing graceful restart
[Sun May 16 01:12:30.614001 2021] [ssl:warn] [pid 813:tid 140467802911872] AH01909: 10.255.255.248:443:0 server certificate does NOT include an ID which matches the server name
[Sun May 16 01:12:30.614236 2021] [mpm_event:notice] [pid 813:tid 140467802911872] AH00489: Apache/2.4.46 (Debian) mod_fcgid/2.3.9 OpenSSL/1.1.1d configured – resuming normal operations
I have same problem as original poster. Iptables being disabled after reboot. I will wait for fix to be applied, but what i realized in meantime is that if i enable iptables from administration, i can not update my system:
I hope it is OK to reply to this (older) thread, but my issue is identical with the OP (iptables seems stopped in Web UI - I can start it from UI but after a reboot of the server it’s stopped again).
In my case, I have a fresh install of Hestia v1.4.3, on Ubuntu 20.04, in an OpenVZ VPS, that is having the issue. The thing is, this installation does not have the directories mentioned:
/usr/lib/networkd-dispatcher/
nor /usr/lib/networkd-dispatcher/routable.d.
I tried creating these directories and copying the file 10-hestia-iptables I found on another installation (a KVM VM if that matters). I also changed the contents of the 10-hestia-iptables file from: if [ "$IFACE" = "eth0" ] to if [ "$IFACE" = "venet0" ] to match the name of the interface and also the line: [ -x "/usr/sbin/ipset" ] to [ -x "/sbin/ipset" ] to match the location of the ipset executable.
Please note that I can temporarily start iptables, either from the UI or by running the command v-update-firewall
Unfortunately, I had no luck correcting the issue. Does anyone have any other ideas I can try?