Restart VPN service: sudo systemctl restart qubes-vpn-handler.service
Check the log and find out which line of code is causing this issue sudo journalctl -u qubes-vpn-handler.service
Oct 20 14:00:58 crow-tmp systemd[1]: qubes-vpn-handler.service: Scheduled restart job, restart counter is at 1.
Oct 20 14:00:58 crow-tmp systemd[1]: Stopped qubes-vpn-handler.service - VPN Client for Qubes proxyVM.
Oct 20 14:00:58 crow-tmp systemd[1]: Starting qubes-vpn-handler.service - VPN Client for Qubes proxyVM...
Oct 20 14:00:58 crow-tmp qubes-vpn-setup[1406]: iptables: Bad rule (does a matching rule exist in that chain?).
Oct 20 14:01:00 crow-tmp qubes-vpn-setup[1409]: iptables: Bad rule (does a matching rule exist in that chain?).
Oct 20 14:01:02 crow-tmp qubes-vpn-setup[1419]: iptables: Bad rule (does a matching rule exist in that chain?).
Oct 20 14:01:02 crow-tmp qubes-vpn-setup[1403]: Error: Firewall rule(s) not enabled!
Oct 20 14:01:02 crow-tmp systemd[1]: qubes-vpn-handler.service: Control process exited, code=exited, status=1/FAILURE
Oct 20 14:01:02 crow-tmp qubes-vpn-setup[1420]: STOP-ing network forwarding!
Oct 20 14:01:02 crow-tmp systemd[1]: qubes-vpn-handler.service: Failed with result 'exit-code'.
Oct 20 14:01:02 crow-tmp systemd[1]: Failed to start qubes-vpn-handler.service - VPN Client for Qubes proxyVM.
Not sure what’s wrong with the iptables (I did not edit those, and it used to work). How can I figure out what’s wrong with the iptables?
Thank you @1choice! I was using fedora-37 (as vm running the vpn and providing network) and tasket script wasn’t working (as described in the original posting of this thread), but after switching to debian11, it works again! (I probably was using older debian before and switched to fedora during my Qubes upgrade without noticing).