-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--start-exec fails with code exited, FAILURE status #59
Comments
The problem is that the config file doesn't carry over from the template to the proxyVM. When you run sudo journalctl -u qubes-vpn-handler in the proxyVM after doing all listed steps, you'll see that options error: must define TUN/TAP device comes up in the log file and also that the config file can't be found. The former is probably caused by the latter. UPDATE: I'm at an absolute loss. I've tried modding everything I could in the startup script to add --dev tun but nothing has worked. I've been at this for far too long, I'll sleep on it and update this about what's happened since I started working on this. |
I've started from fresh on each attempt I've made. First, I made a new template cloned from either fedora 32 or debian 10 on qubes 4.0.4. Then I set that template up according to the exact instructions given, services, files, config testing before install, the connection works when invoking openvpn with the config files as recommended but after install and shutdown is when everything goes wrong. I start the proxyVM based on the template that I made, then run the config and reboot. I've doubled checked that they both have vpn-handler-openvpn service enabled but I still get the error related to not passing --dev tun or --dev tap. |
I had the same issue, this is happening because the script is trying to redirect DNS traffic to IPv6 addresses if your VPN provider is issuing a IPv6 DNS Server. Pull this to skip over the IPv6 address (If the address given is a global/public IPv6 address) |
I'll try this and get back to you when I'm able. |
I've been trying to get this working for a few hours now and so far your solution is the easiest to implement (in theory) though I haven't been able to get it working.
I followed all the steps, made sure that my config file was copied and named correctly but when I run the
systemctl status qubes-vpn-handler
from inside the proxyVM, not the template, I get 5 processes, 4 of which report success, and a main PID that reports FAILURE. My notification message shows 'Ready to start link' repeatedly.I did all the install steps in the templateVM which is setup to use qubes-vpn-setup in the services menu. It's setup also to hand out network connection. The template is based on the default debian-10 in Qubes 4.0.4 and the proxyVM is using that template as a template.
Any help would be appreciated. I'm at a loss here. I can't think of what I might be missing other than some prerequisite. I should also mention that I'm trying to get this all working with PIA.
Thank you for putting this all together and if I get it figured out I'll let you know.
The text was updated successfully, but these errors were encountered: