Multiple qubes cannot connect to the internet

User Support
1

Multiple of my qubes cannot connect to the internet nothing has changed in my networking set up.

I have four protonvpnapp qubes running concurrently providing network connectivity to different sets of qubes. Each instance of protoVPN is signed in separately to my account.

I’m getting “temporary failure in name resolution” when I ping in any of the qubes that are having connectivity issues but zero packet loss in the proton app vms themselves.

things connected directly to sys-net are working fine.

any help would be greatly appreciated. the qubes are all derived from debian-12 or fedora-41 templates

2

I restarted my system and they seem to be working now. but any insight into why this might happen would be helpful.

prior to a full system restart I had shut down and restarted each individual qube multiple times

3

How do you redirect your DNS requests to the VPN?
If you have any nftables rules associated with a static internal IP address, that address may change at some point, which could block all further requests.

4

i have no nftable rules associated with the qubes in question. because I ran into that issue. each protonVPNAPP has access to the network-manager and qubes-firewall service and it works fine. if I do a dns leak test I only see proton servers so it seems to be working

5

I’m not familiar with ProtonVPN, so I don’t know much about how it works. However, since you have NetworkManager enabled in the VPN qubes, a script (/usr/lib/qubes/qubes-setup-dnat-to-ns) runs on networking-related events and automatically sets the DNS IP(s).
Maybe when you change servers or connect/disconnect, the script doesn’t set the DNS properly for incoming qubes requests?

1 Like
6

Could be that. i’ll pay closer attention to it. I’m also unsure how Proton VPN does it under the hood.

7

Have no problem with sys-protonvpn qubes and multiple of them at all.
And I use 4 to 6 of them simultanesly.

8

neither have I generally have 4-6 running all of the time too. yesterday was the first time i ran into the issue i was having.

9

Maybe some uncomplete template upgrade