Series: Policy > Usability
I run a VPN all the time — by choice. Not because I’m doing anything shady, but because I prefer reducing tracking, metadata collection, and exposure on networks I don’t control.
On newer iPhones, that choice now comes with friction. Every time I get home and the phone switches from cellular to Wi-Fi, the VPN experience turns into something I have to babysit.
What should happen
When a phone changes networks, a VPN should renegotiate automatically or fail loudly if it can’t. The expectation is simple:
- Reconnect without user intervention
- Keep traffic flowing
- Clearly indicate failure if something breaks
What actually happens
After arriving home, the VPN often still shows as “connected” — but traffic stops working. No error message. No warning. Just silence.
The only reliable fix: turn the VPN off… then back on. Every single time.
Why this is Policy > Usability
This isn’t user error. This is the operating system trying to be “smart” about preserving network connections during transitions and ending up in a fragile state where user intent is ignored.
My intent: VPN always on.
Reality: a preserved session that looks connected but doesn’t actually work.
If the OS overrides a setting you explicitly enabled and forces manual intervention, that’s not usability — that’s policy.
The practical workaround
Until this behavior changes, the most reliable workaround is using an iPhone Automation to force a clean state:
- Open Shortcuts → Automation
- Create a new automation for Wi-Fi
- Trigger: When connecting to your home Wi-Fi
- Action: Set VPN → Off
- Disable Ask Before Running
Optional: create the inverse automation so the VPN turns back on when you leave home.
Watch the Short
This post accompanies a short video in my Policy > Usability series, where I document situations where software decisions override user intent.
▶ Add the YouTube Short link here: [PASTE LINK]
SEO Tags
🔒 VPN Always-On… Until iOS Decides Otherwise
Series: Policy > Usability
I run a VPN all the time — by choice. Not because I’m doing anything shady, but because I prefer reducing tracking, metadata collection, and exposure on networks I don’t control.
On newer iPhones, that choice now comes with friction. Every time I get home and the phone switches from cellular to Wi-Fi, the VPN experience turns into something I have to babysit.
What should happen
When a phone changes networks, a VPN should renegotiate automatically or fail loudly if it can’t. The expectation is simple:
- Reconnect without user intervention
- Keep traffic flowing
- Clearly indicate failure if something breaks
What actually happens
After arriving home, the VPN often still shows as “connected” — but traffic stops working. No error message. No warning. Just silence.
The only reliable fix: turn the VPN off… then back on. Every single time.
Why this is Policy > Usability
This isn’t user error. This is the operating system trying to be “smart” about preserving network connections during transitions and ending up in a fragile state where user intent is ignored.
My intent: VPN always on.
Reality: a preserved session that looks connected but doesn’t actually work.
If the OS overrides a setting you explicitly enabled and forces manual intervention, that’s not usability — that’s policy.
The practical workaround
Until this behavior changes, the most reliable workaround is using an iPhone Automation to force a clean state:
- Open Shortcuts → Automation
- Create a new automation for Wi-Fi
- Trigger: When connecting to your home Wi-Fi
- Action: Set VPN → Off
- Disable Ask Before Running
Optional: create the inverse automation so the VPN turns back on when you leave home.
Watch the Short
This post accompanies a short video in my Policy > Usability series, where I document situations where software decisions override user intent.
▶ YouTube Short link here: VPN Limited
