Clean install arm64 does not start after reboot (v-start-service iptables)

Community Support Firewall
1

Hey! Thank you for what you are doing. This is very cool.
On a clean installation, the web server does not start after a reboot. Only manual v-start-service iptables helps.

Version 1.4.13~alpha (arm64)
Hestia error.log

2021-08-30 12:42:50 v-list-web-domain ‘admin’ ‘my-instance’ ‘plain’ [Error 3]
2021-08-30 12:42:50 v-list-web-domain ‘admin’ ‘my-instance’ ‘plain’ [Error 3]
2021-08-30 12:42:50 v-add-web-domain ‘admin’ ‘my-instance’ [Error 2]
2021-08-30 12:48:12 v-list-dns-records ‘admin’ ‘my-instance’ [Error 3]
2021-08-30 12:48:29 v-list-dns-records ‘admin’ ‘my-instance’ [Error 3]
2021-08-30 12:48:29 v-add-letsencrypt-domain ‘admin’ ‘my-instance’ [Error 15]
2021-08-30 12:48:29 v-add-letsencrypt-host [Error 19]
2021-08-30 13:25:24 v-start-service [Error 1]

Can I fix this? Thanks!

2

What is your provider and OS?

3

oracle cloud and Canonical-Ubuntu-20.04-aarch64-2021.07.20-0

4

When you reboot:

Run: systemctl status hestia-iptables.service as root What do you see?

5

Error is probably:

Jul 21 19:00:22 xxxx systemd[1]: Starting Loading Hestia firewall rules…
Jul 21 19:00:22 xxxx iptables-restore[702]: Another app is currently holding the xtables lock. Perhaps you want to use the -w option?
Jul 21 19:00:22 xxxx systemd[1]: hestia-iptables.service: Main process exited, code=exited, status=4/NOPERMISSION

To solve this issue:

nano /lib/systemd/system/hestia-iptables.service
And edit ExecStart=/sbin/iptables-restore /etc/iptables.rules to

ExecStart=/sbin/iptables-restore --wait=10 /etc/iptables.rules

And reboot the server…

1 Like
6

● hestia-iptables.service - Loading Hestia firewall rules
Loaded: loaded (/lib/systemd/system/hestia-iptables.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2021-07-21 22:00:22 EEST; 1 months 10 days ago
Main PID: 711 (code=exited, status=4)

Jul 21 22:00:22 my-instance systemd[1]: Starting Loading Hestia firewall rules…
Jul 21 22:00:22 my-instance iptables-restore[711]: Another app is currently holding the xtables lock. Perhaps you want to use the -w option?
Jul 21 22:00:22 my-instance systemd[1]: hestia-iptables.service: Main process exited, code=exited, status=4/NOPERMISSION
Jul 21 22:00:22 my-instance systemd[1]: hestia-iptables.service: Failed with result ‘exit-code’.
Jul 21 22:00:22 my-instance systemd[1]: Failed to start Loading Hestia firewall rules.

7

It worked! Now everything is all right. Thanks!