iMessage stops working when on VPN

For ExpressVPN, until an update comes out that allows Advanced Protection features, this is the workaround:

1. Go into Preferences
2. Turn off all features in Advanced Protection
3. Select IKEv2 under Protocol

Akal1967 wrote:

Since upgrade to Sequoia, IMessage is blocked when Express VPN is on. Missed IMessages are also not shown after deactivating the VPN

Other people have reported similar problems with ExpressVPN. Everything seems to work fine in NordVPN.

Try turning off the Firewall and then try them. If they work then it's the bug in the Firewall

Turning Firewall off in Settings/Network fixes that particular VPN problem.

Turn you VPN OFF

Just a quick update on my side as to share what has worked and what has not.

• Checked config and i had a Profile for DNS SEC which def seems to break the imessage function
• I also noticed the MullvadVPN when running somehow it stops the imessage to get throguh.
• Adding Message and Mullvad to the FW did not resolve the issue i still have the same issue.
• However, it seems that incoming message does work which is a bit odd.

If apple can get on to this and fix this i would very much appreciate it.

Well I guess you going to have stop using a VPN while using Messages.

I'm using the latest build of macOS, version 15.0.1 (24A348), and I'm experiencing the same issue with Mullvad VPN. This functionality worked correctly in previous versions of macOS, but it's no longer working after the update.

I have the same issue with ExpressVPN ever since upgrading macOS.

I've tried opening the FW to allow incoming connections to the vpn, have restarted the machine, and disabled/re-enabled Messages through iCloud. Nothing has worked. I still can't send Messages. My iPhone is the only device I have that will reliably send/receive messages now. It's very frustrating.

Same issue with PIA VPN; driving me nuts!

I also cannot send/receive iMessages with my VPN activated... but missed messaged do load in once the VPN is deactivated.

me, too!!

Do you know which rule causes the message to fail? Can you please pinpoint to FW rule?