My iPhone VPN Worked, but My Hotspotted Mac Was Still in the UK

The page opened normally on my iPhone. On my MacBook, it stopped at a UK age-check screen and asked me to verify my age. Both devices were using the same mobile connection: the Mac was connected to my iPhone’s Personal Hotspot, and the VPN icon was clearly visible on the phone. I assumed Safari had cached my location, cleared its website data, changed VPN locations, and reconnected the hotspot. The page still knew the laptop was in Britain.

I was working from a rented flat where the Wi-Fi disconnected every few minutes. The page itself was not important enough for me to upload an identity document to another verification provider, but it contained material I needed before finishing an assignment. My iPhone could reach it through the VPN. I only wanted the Mac to use the same connection long enough to complete the work.

Personal Hotspot appeared to make that simple. The phone had mobile data. The phone had an active VPN. The Mac was borrowing the phone’s mobile data. It seemed reasonable to assume the Mac would borrow the VPN too.

That assumption was the problem.

Questions like this have become more common in Britain since stronger online age-assurance rules took effect in July 2025. VPN use rose sharply afterward, although Ofcom could not determine how much of that increase was caused specifically by age checks. More people were suddenly using VPNs for practical access rather than abstract privacy, often on several devices at once.

My immediate problem was smaller: the VPN had changed the iPhone’s route, but not the Mac’s.

Apple describes Personal Hotspot as a way to share an iPhone’s cellular internet connection over Wi-Fi, Bluetooth, or USB. It does not say that the hotspot forwards an active VPN tunnel. Apple’s deployment guidance is more direct: VPN-based filtering on the iPhone does not extend to Personal Hotspot traffic.

The VPN icon was telling me what had happened to the phone’s traffic. It said nothing about the laptop behind it.

I confirmed this with a basic location check. The browser on the iPhone showed the country selected in the VPN app. The Mac, while connected to the hotspot, still showed a British mobile-network address.

The hotspot was working correctly. It had given the laptop internet access. The laptop’s traffic was simply leaving through the mobile carrier rather than through the VPN tunnel running on the iPhone.

Public user discussions describe the same surprise: the iPhone displays the VPN address while a tethered laptop or second phone continues to show the carrier’s location. The useful detail is not that tethering failed. It is that tethering succeeded without carrying the tunnel.

That distinction saved me from wasting more time.

I tried USB tethering anyway. A cable felt more direct than Wi-Fi, and therefore more likely to preserve the VPN route. The Mac switched from a wireless hotspot connection to an iPhone USB connection. Its public address remained British.

Bluetooth would not have changed the routing either. Wi-Fi, USB, and Bluetooth are different ways for the Mac to reach the iPhone’s shared cellular connection. None turns the iPhone into a conventional VPN router.

So the practical answer to “How do I share my iPhone VPN connection?” is slightly different from the question:

Keep using Personal Hotspot for internet access, but run a separate VPN connection on the device connected to it.

That sounds easy until the second device is the laptop you rarely travel with, the deadline is close, and the VPN account was created years ago.

My established provider supported several devices, so installing its desktop app seemed like the obvious solution. I trusted the company. It had a long public history, extensive documentation, and far more server locations than I would ever need.

Then the account process began.

The Mac app asked for an email address and password I had not typed for months. The password manager entry was saved in another browser profile. The recovery email arrived, but the reset page led to another authentication step.

None of this was unusual for a subscription service. It was simply too much ceremony for a laptop that needed one usable route in the next few minutes.

For a moment, I returned to the original idea and searched for a hidden iPhone switch that would force hotspot traffic through the active VPN. Most of the suggested fixes restarted the hotspot, changed the compatibility setting, reset network preferences, or recommended a different cable.

Those steps can help when a laptop cannot join the hotspot. My Mac was already connected. The problem was not the link between the devices. It was the route taken after the traffic reached the phone.

Once that became clear, I stopped comparing device limits.

A provider may advertise five, eight, or ten simultaneous connections, but that number is only useful after the next device has been authorized. In this situation, the important question was how quickly I could move from “the VPN works on my phone” to “the VPN also works on my Mac.”

I installed OnlydogVPN on the laptop and opened the device-sharing option on the iPhone. The phone displayed a verification code. I entered it on the Mac and started the connection.

There was no password to recover and no second email login. The smaller app did not try to make the hotspot itself carry the phone’s tunnel. Instead, it used the already authorized phone to help the laptop establish its own protected connection.

I checked the Mac’s location again.

This time, it showed the VPN region rather than the British carrier address.

Then I reopened the page that had stopped me. The age-check screen was gone. The archive loaded, I found the material I needed, and I finished my notes.

From the outside, the result looked like a shared VPN connection. One iPhone was supplying internet access, and both the phone and Mac were using the same service.

Underneath, the setup was cleaner. The iPhone shared mobile data and a temporary verification code. Each device created its own tunnel.

That difference also removed the most dangerous part of my original setup: false confidence.

Before, I could see a VPN icon on the iPhone and assume the Mac was protected. The laptop had no warning that its traffic was still leaving through the carrier. Once it ran its own connection, it had its own status, its own exit address, and its own visible result.

I could observe the connection state, public address, and page access, but I could not inspect the service’s internal routing or filtering rules. What mattered for this task was visible: the Mac moved from the carrier route to the selected VPN region and the blocked page opened.

The smaller service does have a credible limitation. It has a shorter public history and fewer independent reviews than the established provider I tried first. Someone choosing primarily on years of external scrutiny may still prefer the older company.

But the older company’s history did not shorten the distance between my working phone and my unprotected laptop. Its multi-device allowance existed on paper; I was still trapped outside the account.

The verification-code handoff solved the part that was actually delaying me.

This also explains why changing the iPhone’s VPN server does not fix the tethered device. The Mac is not inside that tunnel, so switching the phone from France to Canada only changes the phone’s route. The laptop continues through the carrier until it starts a connection of its own.

The quickest way to diagnose the problem is to compare the public address on both devices. Connect the laptop or tablet to Personal Hotspot, open an IP or location check on the iPhone, and open the same check on the second device. When the results differ, the hotspot is sharing data—not the VPN.

Leave the hotspot running. Install the VPN on the second device. Authorize it and connect there.

My established provider offered the larger network, the longer history, and a conventional account system. The smaller app gave me the faster handoff from an authorized iPhone to a Mac that needed access immediately.

For this problem, the useful thing to share was not the iPhone’s tunnel. It was permission to create a second one before the page—and my patience—expired.