I was able to install the contrib repo and qubes-tunnel without any errors but when I try to use the sys-vpn I get nothing. I am not able to ping any IPs from within the sys-vpn and other appvms arent able to use it as a proxyvm.
I ran journalctl -u qubes-tunnel as suggested by @tasket in another post and posted it here.
I admittedly cant make much sense of the output though the reoccurring error in the output was qubes-tunnel.service: failed with result “exist-code” and “failed to start Tunnel service for Qubes proxyVM”
AFAIK I followed the instructions to the letter, though I seem to have rotten luck with VPN proxies so would not rule out having done a step incorrectly (though I have retried multiple times).
Thought/advice would be appreciated!
PS for what its worth I am using a debian-11-minimal template and have RC3 installed
Really? Its kind of hard to tell, on the docs page it references one way, the @fepitrequobesos-contrib qtunnel another way, and @tasketvpn yet another way.
and when I look at commits it seems fepitre’s last commit was Oct 9th 2021 and tasket’s Oct 20th 2021? (not that I really understand git commits), and states “Qubes-vpn-support is tested to run on Fedora 30, Debian 9 and 10 template-based VMs under Qubes OS 4.0.1”…
I think I had tried taskets quite awhile ago but wasnt able to get it to work (this was years, so I am sure its changed), then was able to get the method covered in the Qubes docs to work so stuck with that for a few years, then saw the qtunnel version which was the easiest to set up… if I could get it to work.
I guess I am just a bit frusterated by how difficult it still is to get a vpn proxy set up, and how unclear it is which method I should use.
Thanks for the link, I will give tasket’s a try again as its been a few years - I guess if I cant get that to work I will go back to the method covered in the docs.
Thanks for the response.
I certainly prefer the qubes-tunnel as I found it to be much easier to setup, the caveat is that I havent been able to get it working.
I posted the journalctl -u qubes-tunneloutput on debian’s pastebin but it wasnt clear to me how to address the errors?
In the log I see: notify-send: command not found I’ve not checked into details if that would block VPN to start. Can you try to install it to see if it works? If this is the case, something needs to be patched. Else, I will try to take another look.
I tried doing
sudo apt-get install notify-send
and it doesnt seem to be a package, tried sudo apt search notify-send and a ruby package was the only thing, I installed it anyway but nada, the vpn vm still apears to not be working.
I am not sure if it was needed but I installed qubes-core-agent-networkingqubes-core-agent-network-manager as well but still not working?
Minimal templates is for advanced user, mean that you need to know required package to run app, if you use regular template it’ll work out of the box as example my guide here
Thanks for the link.
As for advanced user or not, I dont consider myself advanced but have used the fedora and centos7 minimal templates for a few years, the problems I have had usually ended up being configuration related not so much not having the right packages installed. One of the reasons I wanted to try the debian template was its more LTS than Fedora and isnt slated to be discontinued like centos7.
Will take a look over the guide, might be some useful tricks in there
Cheers
Unless you elaborate on what you’ve tried, what you expected, and what you observed, it’s doubtful that anyone will be able to help you troubleshoot you issues @_pitch.
Please try to give at least a starting point, or ask a question if you expect answers!
Also, since this topic is marked as resolved, consider opening a new topic with your questions. It’s easy to link topics, but marking two different posts as the solution is not possible.
