-
Notifications
You must be signed in to change notification settings - Fork 338
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
Outgoing connections not working after 2024.6 update #7058
Comments
I can confirm the issue for Macos 15.0.1 (24A348). After trying for OpenVPN/wireguard and sub-internal options, I couldn't fix the issue temporarily and was downgraded to 2024.5, and it seems to work fine. |
I have these symptoms when I point Mullvad at 127.0.0.1 for custom DNS with dnscrypt-proxy. I don't have any issues with a public custom DNS server or no custom DNS server though, so maybe that's a different issue. 2024.5 worked perfectly for me as well. |
I'm having the same problem. I might need to revert back to 2024.5. Tailscale and Mullvad were working fine together before on my mac, but now I keep getting dns-forward-failing and no-derp-connection errors. |
I am here for this! More: I have downloaded 2024.05 from github; uninstalled 2024.6 and installed 2024.5 on my macos and now I have internet back |
Same here, uninstall & reinstall by Homebrew, full access granted, macOS 14.7, can connect to any server, has IN IP, never get OUT IP for some reason, lead to all internet blocked. |
I confirm with Sequoia 15.0.1 and Mullvad app 2024.6 : connectivity completely lost. I switched back to 2024.5. |
Same. MacOS 15.0.1. Uninstalled 2024.6 and reinstalled 2024.5. 🫠 |
Reverted back to wireguard-tools/mullvad to regain connectivity that was lost due to the app update 2024.6. |
Hello everyone, thanks for reporting. We have been made aware of the issue with the 2024.6 release on macOS and we are investigating it. |
Here we go again...
Will be contacting support for a refund - unable to use my VPN properly for ages Regards |
Hi! We have a potential fix that we would appreciate if you all could help us try out! It's somewhat difficult to reproduce so we can't reliably test it on our computers. Here's a test build that includes the fix: https://releases.mullvad.net/desktop/builds/2024.6-dev-8e55ad%2Btest-20247/MullvadVPN-2024.6-dev-8e55ad%2Btest-20247.pkg Let us know how well it works for you! |
Seems to work for me -- in the 30 second test I gave it. Loaded multiple browsers and ran a couple 3rd party "speed tests" |
Thanks for the hasty feedback, it is very much appreciated! 💛 |
Can you share what the fix is that’s in the test build? |
It works here with Sequoia 15.0.1, Split tunneling (Safari can't be excluded, but it was already the case before) and LittleSnitch 6.1.2. I tried multiple browsers and after reboot. Good job |
Works |
No more issues with my custom DNS setup after updating to the dev build. |
This works. To note, Windows 11 running via Parallels encounters issues. States no Internet connection in Taskbar tray, and internet doesn't connect reliably in browser. |
This version fixes the issue for me, too. |
Just checked this build out for myself, and I am still running into DNS problems only when trying to run custom DNS outside of Mullvad. I am testing on Sequoia 15.1 (24B82). Specifically, trying to run Cloudflare WARP through their desktop application alongside Mullvad breaks all DNS resolution. However, defining a custom DNS within Mullvad does work properly. AFAIK everything else works, including split tunneling and Win11 Parallels (someone mentioned it not working above). |
Seems to fix the issue on macOS 15.0.1 for me as well. I have another computer running macOS 15.0 (not yet upgraded to 15.0.1) with Mullvad 2024.6 and there are no issues on that one. |
I'm seeing this as well. I switched to Bridged Network for the time being and it works, but this means no VPN for the VM. |
this works however it shows a security warning: "Your privacy might be at risk with this unsupported app version. Please update now." |
Working here. I had the current issues with the 2024.6 beta and now with the release as well, but this build is working without noticeable issues. |
I was just sent this version via email by support, has fixed the issue for me too but I needed to update my macOS or restart for it to work, not sure which one as I just updated. |
I've just tried on MacOS Sonoma 14.7 (23H124) with the latest 2024.7-beta1 and the issue seems to be the same than 2024.6. Ingoing is ok but outgoing never gets filled. I get lots of really weird behaviors on the UI such as impossible to switch to another location, switches seem to not be visually responding, like the UI thread was overloaded with something and never gotten CPU time back. Pretty strange. Had to downgrade to 2024.5 for it to work. Behavior when connecting is quite different on 2024.5 than 2024.6+, whereby "creating quantum connection" takes a good 10 seconds before the "out" field gets filled, whereas on 2024.6+, it is very quick, but it never gets filled. Not sure whether this extra info helps or not. |
We've now released 2024.7-beta1 which contains the same fix as in the dev-build posted above. Please try out the beta! Thanks to everyone who helped test the dev-build! If you run into any issues on future betas, please report the issue either with the "Report a problem" function in the app or here. @nicolasembleton Could you send a problem report in the app and write that it is in response to this issue, and we'll take a look! |
Looks good at my end, thanks @raksooo. There's still the issue of Shared Network no longer working in Parallels (Win 11 VM, Edge returns DNS_PROBE_FINISHED_NO_INTERNET). |
When using 2024.5 release, I was able to run Tailscale as an exit node on my computer using Mullvad VPN. I just tried to run Tailscale with 2024.7-beta1, and I'm still seeing dns-forward-failing on the Tailscale side. As this is the case, I will need to revert back to 2024.5 again. |
macos 15.1 (24B82) AirDrop (still) broken Regards |
i can confirm that in the 2024.6-devbuild Airdrop works |
This fix worked for me as well (M1 Pro Sonoma 14.7). For the time being, until this is incorporated in a new release, should I revert back to 2024.5? I got a warning message in the app saying this test version is unsupported. |
The fix has been released in the current beta: https://github.com/mullvad/mullvadvpn-app/releases/tag/2024.7-beta1 |
Please ignore this I neglected to turn on Apologies |
2024.7 has been released as stable: https://github.com/mullvad/mullvadvpn-app/releases/tag/2024.7 🚀 |
I have just updated to 2024.7. At first glance, my problem appears to be solved. Thank you, @MarkusPettersson98, for such a quick fix. ❤️ |
Sorry for the late reply. I just did and mentioned the symptoms (but forgot to mention this particular issue#). I tried the latest stable version and I'm still having the same issue on Sonoma. |
Problem solved. Thanks for your great support. |
I've tested the 2024.7 release on the same device, and everything is fine. Thanks for the quick fix. |
My apologies, but I've just tested the final release of 2024.7, and I'm still having issues while running a Tailscale exit node on my Mac while running Mullvad VPN. If this requires a new request, please let me know and I will be happy to share steps to reproduce this behavior. This does not happen on the 2024.5 release of Mullvad VPN. The error on the Tailscale client side is |
2024.7 still not working for me with local development setup. Using Valet and TLD .test. |
2024.7 is not working for me either. I'm using dnsmasq with local web development. When connected to the VPN, my local development environment doesn't respond as expected. I see the "this site can't be reached" with a After downgrading to 2024.5, my local development site responds as expected. |
Can confirm no outgoing connections working while using shared networking in Parallels, irrespective of platform used (linux, mac, windows, etc) on 2024.7. As with other people, downgrading to 2024.5 seems to repair this functionality. |
Using manual DNS within host, as indicated on this page : https://mullvad.net/en/help/dns-over-https-and-dns-over-tls#win11 But it's a lot slower than automatic DNS. |
Is it a bug?
I have checked if others have reported this already
Current Behavior
Outgoing connections not working after 2024.6 update
The app also shows no outgoing ip
These are the only out of place logs I found, idk if related
[DEBUG] no one is waiting for ICMP packet (V4(Icmpv4Packet { ...
[DEBUG] error decoding ICMP packet: MalformedPacket(NotIcmpv4Packet)
Expected Behavior
Expect it to work and show outgoing ip
Steps to Reproduce
Failure Logs
No response
Operating system version
macOS 15.0.1 (24A348)
Mullvad VPN app version
2024.6
Additional Information
Everything still functional on 2024.5 so its definitely 2024.6
The text was updated successfully, but these errors were encountered: