Many services don't work in MacOS Sequoia

[63045]

Is it a bug?

• I know this is an issue with the app, and contacting Mullvad support is not relevant.

I have checked if others have reported this already

• I have checked the issue tracker to see if others have reported similar issues.

Current Behavior

When connected to Mullvad on MacOS Sequoia, I cannot send or receive messages on iMessage, even with split tunneling enabled and iMessage excluded.

Expected Behavior

I expect to be able to send/receive messages.

Steps to Reproduce

Self-explanatory

Failure Logs

No response

Operating system version

macOS 15.0 Beta

Mullvad VPN app version

2024.4

Additional Information

Some other iCloud-related services seem to work. iCloud Drive, Apple Mail, etc.

[nocturne1]

Apple news fails as well - all sources are grayed out when tunnel is active.
I also am unable to establish any connection when split tunneling is enabled for any app, so there appears to be an issue there too.

[drpoutine]

Has more issues on Sequoia as well. Such as Mullvad not starting up when you login/restart the OS
Lot of macOS issues on 15.0 and 15.1 (similar issues on both)

[nocturne1]

The messages app issue continues to exist on 2024.5-beta1 running on the latest macOS 15.0 Beta (24A5331b).
Interestingly enough, the Apple News issue I mentioned above was resolve a few macOS betas ago.

[63045]

FaceTime is broken as well. Incoming calls don't appear and outgoing calls just hang.

[BionicBison05]

Any update on this? macOS 15 is due to release in a week, and I'd like to able to upgrade when it does.

[nocturne1]

I haven't tried it with today's beta release, but I've found that using the Wireguard app works just fine. So I've been using that for now.

[raksooo]

Hi, thanks for reporting this issue. We are aware of it and will look into it soon.

[Irv72]

Any update on this? macOS 15 is due to release in a week, and I'd like to able to upgrade when it does.

Still not working in the Release Candidate, so don't upgrade unless something changes.

I submitted the bug to Mullvad about a month ago, through the VPN app, and received an acknowledgement. So they've known about it for a while. Hopefully, a fix is coming, because it's very annoying.

[m-c-program]

Beating a dead horse since I'm pretty sure it's exactly the same networking wise as 15.0 RC, but 15.1 build 24B5035e also has the same issues.

[notDavid]

hey @raksooo are you aware Sequoia will be publicly available / released today?

[no-usernames-left]

Hi, thanks for reporting this issue. We are aware of it and will look into it soon.

It has been released to the public. Is there any movement on this issue internally?

[Serock3]

Hello. I am chiming in to say that this is a high priority issue and that we are actively investigating possible solutions. We have no time-frame for a fix yet, unfortunately, but we are taking it seriously.

[drpoutine]

There's multiple things that are just broken.

I've noticed it has something to do with Lockdown Mode on my side but its difficult to replicate the issue. I can try to run some scenarios in a macOS vm to see if i can pinpoint the issue later this week or so if i have time.

[luisillo26]

I've been having issues with the new iPhone notifications shown on MacOS Sequoia and Messages

[notDavid]

@raksooo @Serock3 PS. Not sure if related, but did you guys see the mentions of macOS Firewall Regressions in Sequoia ?

[JohnMiltonSr]

macos 15 sequoia, apple silicon, using latest version of mullvad.

messages app is the only one that seems affected. i cannot send or receive messages. news, mail, and weather apps all unaffected for me.

the only way to get the messages app to update with new messages is to manually sync through icloud settings (not in messages app). only then do the messages from iphone load into the mac messages app. however, if i try to do the same thing via the messages app (messages app also has an option to manually sync with icloud), it doesn't work.

edit: also wanted to add that i'm using wireguard protocol and split tunneling the messages app does nothing. split tunneling does work for me with firefox thought.

[faridchaouki]

Same issue here with the official release of MacOS Sequoia 15.0.
Split Tunneling is Off and problem persists with Messages not being able to send or receive.

[bwrightkc]

Issue also exists in 15.1 Beta 4 build 24B5046f. Not resolved by disabling quantum tunneling either.

[user733626]

Same problem here! I had to uninstall the official mullvad app and install wireguard which seems to be working fine with all icloud services such as messages etc...
Any progress on the bug @raksooo ?

[ccconcrete]

Same problem here! I had to uninstall the official mullvad app and install wireguard which seems to be working fine with all icloud services such as messages etc... Any progress on the bug @raksooo ?

Wait so u can download the official Wireguard App and use your mullvad account through it ?

[user733626]

Same problem here! I had to uninstall the official mullvad app and install wireguard which seems to be working fine with all icloud services such as messages etc... Any progress on the bug @raksooo ?

Wait so u can download the official Wireguard App and use your mullvad account through it ?

yep you can, you just have to download the file with all the servers while logged-in to your account in browser + you can even choose which DNS content blockers you wanna use as well before downloading the file

[JohnMiltonSr]

wanted to add that the only significant change to messages in macos 15 is the addition of the RCS protocol (for android/non-iphone texting). because no other mac apps seem to be affected, maybe this is connected to the bug? @Serock3

[MarkusPettersson98]

@ccconcrete Yes, you can use the vanilla Wireguard App with Mullvad. Please note that doing so can risk your privacy because it does not have the firewall integration that the Mullvad app does.

[mdl054]

Experiencing the same issues here, Messaging is the obvious piece, however I'm now unable to turn off Lockdown Mode. Disabling does nothing, internet still blocked while disconnected. Kind of a big deal as obviously some sites will no longer work while connected to Mullvad and now you no longer have the option of disconnecting. Hopefully this gets a priority.

[JohnMiltonSr]

Same problem here! I had to uninstall the official mullvad app and install wireguard which seems to be working fine with all icloud services such as messages etc... Any progress on the bug @raksooo ?

Wait so u can download the official Wireguard App and use your mullvad account through it ?

yep you can, you just have to download the file with all the servers while logged-in to your account in browser + you can even choose which DNS content blockers you wanna use as well before downloading the file

do you know if split tunneling on a per app basis is possible using the official wireguard app or a fork? i had mullvad split tunnel enabled for firefox so i could use no proxy for certain websites that don't like mullvad vpn and it would be nice to get this feature back while we wait for a fix

[banister]

Same problem here! I had to uninstall the official mullvad app and install wireguard which seems to be working fine with all icloud services such as messages etc... Any progress on the bug @raksooo ?

@user733626 are you sure the WireGuard app has a firewall? the issue seems to be that Apple forcibly bind iMessage to the physical interface so the killswitch will block its traffic. Obviously if you don't have a killswitch (which blocks off-VPN traffic) then iMessage will work, but it's also leaking like crazy out the physical, so not a good solution.

[qwertyasdfasdfqwerty]

MacOS 15.0.1 MullvadVPN 6 beta1 Apple Services Bypass: ON
AirDrop, iMessage, Facetime working with this combo as of now, will report if it stops after a while.

Update: very shaky, kind of works, kind of doesnt sometimes, definitely not fully resolved.

Basically sums it up. It's inconsistent to the point of straight up being broken, and honestly is a liability to use.

I'm not sure what the ETA is on the other potential fix that was mentioned a couple days ago, but I'd maybe even go so far as to say that I kind of think this update should be pulled/rolled back. Using the official Wireguard app is the only real "solution" as things currently stand.

[ldexterldesign]

👋

Sorry if I've missed it here, if a Mullvad (MV) version exists where this issue doesn't then please let me/us know so I/we can rollback?:

• If yes then MV please enhance your testing before releases - issue is very 😞
• If no then will assume blame is fully on Apple (i.e. Sequoia will break any version of MV)

Hope to hear back and good luck with fix

🤞

[raksooo]

I'm not sure what the ETA is on the other potential fix that was mentioned a couple days ago, but I'd maybe even go so far as to say that I kind of think this update should be pulled/rolled back.

The current plan is to release a new beta this week (2024.6-beta2) which will include a real fix and it won't contain the current bypass toggle. That will hopefully become a stable release in a couple of weeks.

[qwertyasdfasdfqwerty]

A new MacOS 15.1 beta (Beta 6) was just released. Will be testing it shortly.

[qwertyasdfasdfqwerty]

Upon initial testing, I think this MAYBE is resolved at least with the latest MacOS beta 15.1 (24B5070a).

I used the Mullvad app as per usual, actually turned OFF Apple Services Bypass, had a text message sent to me, and it immediately came through on the Mac. Hesitant to fiddle with too many other settings in the meantime, but that's what I got.

Anyone else have any luck or any other noticeable issues with the latest beta?

[bedesv]

I've also updated to 15.1 beta 6 and the Apple services are working for me with Mullvad active even with Apple Services Bypass turned off.

I did have some issues with not being able to access the internet when I first installed the beta, but Tailscale and Mullvad had both opened automatically so I think it was an issue with multiple VPNs fighting each other and everything works after a reboot. Interestingly the Apple services worked during this time, indicating that the Apple services are back to not using the VPN. Hopefully Mullvad 2024.6-beta2 fixes this.

[drpoutine]

https://developer.apple.com/documentation/macos-release-notes/macos-15_1-release-notes#Messages

I can confirm that it is indeed fixed. all the weird handoff issues and other icloud services related bugs have been resolved as of macOS 15.1 beta 6 build 24B5070a on Mac15,6 . running smoothly using Mullvad for Mac v2024.5.

using wireguard only with multihop and so far everything seems to be functioning OS-wide. No split app configuration was required. just the local network access for bonjour (its turned off when not at home)

imessage and facetime calls all functioning as expected.

[jordanful]

The new MacOS beta allows iMessage and FaceTime, but does not work with Continuity Camera / Mic (i.e. I am unable to use my phone as a camera/mic when Mullvad is turned on). Previously this worked.

[ianclarksmith]

I tether to my phone often and noticed after the update that, at least with my current combination of iOS 18.0 (22A3354) and macOS 15.0.1, I am only able to use the web with the VPN/Mullvad enabled. Lockdown mode is disabled. Split tunneling is off. Both devices have been restarted numerous times during testing.

This leaves me in a funny position where I can use Apple services only while using a regular wifi network with Mullvad switched off. On the go, I can not use Apple services at all and Mullvad is the only thing which makes my other connections work.

Are there any logs or things I should observe to see if the Mullvad app is somehow involved, lockdown setting being enabled and persisting without showing in the UI or something like that? I can open a separate issue if desired but given the nature of the issue I'm mentioning it here on the theme of "macOS Sequoia things not as expected while using Mullvad".

[bwrightkc]

I tether to my phone often and noticed after the update that, at least with my current combination of iOS 18.0 (22A3354) and macOS 15.0.1, I am only able to use the web with the VPN/Mullvad enabled. Lockdown mode is disabled. Split tunneling is off. Both devices have been restarted numerous times during testing.

This leaves me in a funny position where I can use Apple services only while using a regular wifi network with Mullvad switched off. On the go, I can not use Apple services at all and Mullvad is the only thing which makes my other connections work.

Are there any logs or things I should observe to see if the Mullvad app is somehow involved, lockdown setting being enabled and persisting without showing in the UI or something like that? I can open a separate issue if desired but given the nature of the issue I'm mentioning it here on the theme of "macOS Sequoia things not as expected while using Mullvad".

Had this issue in 15.0.1 as well, no longer happening in 15.1 beta 6.

[drpoutine]

The new MacOS beta allows iMessage and FaceTime, but does not work with Continuity Camera / Mic (i.e. I am unable to use my phone as a camera/mic when Mullvad is turned on). Previously this worked.

its entirely possible this is a bug within macOS itself. I've noticed restarting the network daemon til it works seems to be the move

[raksooo]

We've now released 2024.6-beta2. It has a fix that forces Apple apps/services traffic to go inside the tunnel instead of being blocked due to trying to go outside the tunnel. Please try it out and let us know how well it works!

[longlantom]

The 2024.6-beta2 didn't work for me!

[no-usernames-left]

The 2024.6-beta2 didn't work for me!

@longlantom Did you reboot after installing it?

[ccconcrete]

We've now released 2024.6-beta2. It has a fix that forces Apple apps/services traffic to go inside the tunnel instead of being blocked due to trying to go outside the tunnel. Please try it out and let us know how well it works!

My Reply as of now, is that it works, but imessage seems to have a significant delay. ie: It feels like its trying and failing to go through and is stuck for a few seconds attempting to send and then it goes through. So it's working but doesn't seem optimal/fast.

[davidkamayor]

I'm on 2024.6-beta2 and I can report that iMessage does work on my Mac, but iPhone mirroring does not.

[drpoutine]

We've now released 2024.6-beta2. It has a fix that forces Apple apps/services traffic to go inside the tunnel instead of being blocked due to trying to go outside the tunnel. Please try it out and let us know how well it works!

not noticing much of a difference between Mullvad v2024.5 and v2024.6-beta2 on macOS 15.1 beta 6 build 24B5070a with Mac15,6

Fixes on the networking stack are still in progress by Apple on 15.1 betas but if i'm not mistaken these fixes are not available to the public yet on macOS 15.0.1 according to the changelogs and probably won't be until 15.1 is public

macOS 15.0.1 changelog

This update provides important bug fixes for your Mac including:
● Messages may unexpectedly quit when replying to a message with a shared Apple Watch face.
● Improves compatibility with third-party security software.

The fix is coming soon™ per post here

iCloud services started to work as soon as 15.1 beta 6 was installed on v2024.5

For those who are asking about iPhone Mirroring not working while connected to mullvad, this requires local network access as it relies on Continuity to function. Please be informed that there is currently a privacy bug when using iPhone Mirroring

also yes its weird it doesnt work when the iphone is wired into your mac 0-0

[yasoobkhalid1]

Can also confirm that iMessage is finally working on the v2024.6-beta2 version on macOS 15.0.1! And as drpoutine mentioned above, iPhone Mirroring also works once local network access is turned on in Mullvad.

Unfortunately, when I set up tcpdump and listened to 17.0.0.0/8, traffic still seemed to be leaking to Apple over the physical interface (like we discovered earlier in this thread) 😞

Am I doing something wrong? Want to make sure we avoid being similar to some of the other VPNs (like Proton) where iMessage was working, but that was just because they were leaking all their traffic to Apple.

@banister would you able to check and see if the new version still leaks on your end?

[buggmagnet]

Hi @yasoobkhalid1
Can you tell us what's your setup for running tcpdump ?
Here's the setup I used to confirm that we're not leaking traffic.

• Run v2024.6-beta2 on macOS Sequoia 15.0.1
• Turn on Mullvad
• Connect to a router I control, and that is connected to internet
• On the router, I run tcpdump which I then pipe into Wireshark. You can do this without Wireshark, but it makes for a nicer UX
• In wireshark, I then use the filter not wg to filter out all the WireGuard traffic, since I want to see what goes outside of the tunnel
• I start sending messages via iMessage from my mac computer to another iPhone that is only using 4G to make sure I'm not on the same network as the mac computer.

With this setup, I can see that Apple's iMessage traffic is not leaking outside of the tunnel.

For good measure, I was also running Wireshark on the mac computer itself, and using the same filter (not wg) I could not see traffic leaving the tunnel.

Can you share your setup, and repro steps as well ?
Did you mean to say that iPhone mirroring is leaking traffic to Apple ?

[yasoobkhalid1]

Hi @yasoobkhalid1 Can you tell us what's your setup for running tcpdump ? Here's the setup I used to confirm that we're not leaking traffic.

• Run v2024.6-beta2 on macOS Sequoia 15.0.1
• Turn on Mullvad
• Connect to a router I control, and that is connected to internet
• On the router, I run tcpdump which I then pipe into Wireshark. You can do this without Wireshark, but it makes for a nicer UX
• In wireshark, I then use the filter not wg to filter out all the WireGuard traffic, since I want to see what goes outside of the tunnel
• I start sending messages via iMessage from my mac computer to another iPhone that is only using 4G to make sure I'm not on the same network as the mac computer.

With this setup, I can see that Apple's iMessage traffic is not leaking outside of the tunnel.

For good measure, I was also running Wireshark on the mac computer itself, and using the same filter (not wg) I could not see traffic leaving the tunnel.

Can you share your setup, and repro steps as well ? Did you mean to say that iPhone mirroring is leaking traffic to Apple ?

Hi @buggmagnet

Ah sorry, my process was much simpler tbh. I simply ran tcpdump with the following command: sudo tcpdump -i any -s0 net 17.0.0.0/8 and after sending an iMessage, I was able to see a few packets captured. I'm now wondering if those packets being captured was WAI since they were just on wireguard 🤔

Please let me know if I'm doing something wrong in this case! But glad to know that your (much more extensive) testing found no leaks - hopefully this issue should now be fixed :)

[kp-john-mair]

You're filtering on every interface, but it's only a leak if your 17/8 packets are appearing on the physical interface (typically en0 or en1)

[Malachai7]

I think I figured out the issue now....

For Mac users what I did was log out of Mullvah , quit the program then uninstalled it from my machine. Once that was done I restarted the macbook . Went to the Mullvah site and downloaded the software .Once that was done I entered my info then log in. Once that was done I did my test and iMessage started working without any issue.

Hopefully that helps because I was pissed today when I upgraded my mac.

One last thing before you remove the software take down your account number. you will need that when you log back in.

[synfinner]

After doing an uninstall and reinstall of the 2024.6-beta2 (didn't matter how I changed settings), I kept getting 0 networking activity on (15.0.1 (24A348)). Switching back to release 2024.5 and can connect to services normally. Will try and get a packet dump later.

[magidandrew]

Can confirm that the 2024.6-beta2 WORKS on macos 15.0.1 with the apple services bypass 🎉

[yasoobkhalid1]

Can confirm that the 2024.6-beta2 WORKS on macos 15.0.1 with the apple services bypass 🎉

I believe the 2024.6-beta2 version removes the bypass? I think they intend for the VPN to work on that version without it.

[MarkusPettersson98]

Can confirm that the 2024.6-beta2 WORKS on macos 15.0.1 with the apple services bypass 🎉

I believe the 2024.6-beta2 version removes the bypass? I think they intend for the VPN to work on that version without it.

It is true that we removed the bypass in 2024.6-beta2, and it will not be included in the upcoming stable release.

[jhariani]

Just an FYI that the macOS Sequoia 15.1 RC Release Notes has this note:

Messages
Resolved Issues
Fixed an issue preventing iMessage and other third-party notifications from being received while your device is connected on a VPN. (136775545)

[kminevskiy]

After updating to 15.1 today, I can confirm that iMessage works with the non-beta Mullvad desktop app.