Removed Mullvad VPN Wireguard configuration, but now cannot access websites

[2w16y]

I downloaded and installed the Mullvad VPN app - it allows me to see what is going on, allows for quicker shifting, I can set Shadowsocks, etc etc

I was already having issues, so I deleted my VPN qube, then created a standalone qube (so that I could save my account number)
I downloaded and installed Mullvad VPN, and it is up and running

I can ping IP addresses and qubes-os.org on the VPN qube
I can ping IP addresses on other qubes, but not URLs -qubes-os.org: Name or service not known
I cannot access any websites, on the VPN qubes or qubes which are set to use the Mullvad VPN qube for networking
Disconnecting from Mullvad allows me to access websites

What else do I need to do to get myself back onlin?

[bengee]

Hello, this similar sounding issue may or may not be related:

No internet in standaloneVM

No internet connection through sys-vpn, sys-firewall, sys-whonix, or sys-net. I tried manually entering the IP, mask, gateway, and DNS from sys-vpn and sys-firewall settings - connection was established, but there was no internet. I am using a Wi-Fi USB adapter. Internet issue is only in standaloneVM - I tried installing Ubuntu and Arch. I know about templates, but I need linux on standaloneVM as well. I couldn’t find a solution to the problem. Please help

That issue mentioned appears to be a possible bug in 4.2. Haven’t heard if anybody had time to trace it down since things are moving ahead towards 4.3

That’s all I’ve come across so sorry if doesn’t help out

[bengee]

In short, the workaround for that issue was put a random ip in the standalone gateway…It’s NIC settings, if I recall.

[unman]

I package the Mullvad VPN, available from https://qubes.3isec.org/tasks.html
The package provides a Mullvad proxy qube, as well as disposables loaded
with the Mullvad tool and the Mullvad Browser.

There are some changes to handling of traffic from downstream qubes,
particularly a rewrite rule in the qubes dnat-dns chain.
You can see the details in the source at
https://github.com/unman/shaker/mullvad. Look at the update-dns.nft
script. You will see that all DNS traffic is dnatted to the Mullvad
encrypted DNS servers at 10.64.0.1.
This may help you. If you want a turnkey solution install the package.

I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.

[bengee]

@unman Thanks for all your work along with the rest of the group to make setup of things in QubesOS easier! Much appreciated!!

[unman]

Thanks - in this case it’s thanks to the Mullvad support team who are
always ready to help and quick to provide answers.

I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.

[2w16y]

This may be the long-term solution

For now, I’ve reverted to using the Wireguard conf file. Thanks all