The Second VPN Broke My Work Connection: A Cleaner Way to Run Two at Once

The client upload was at 73 percent when I connected a second VPN. My work tunnel was already running because the project folder would not open without it.

This problem has become less unusual since stronger UK age checks took effect in July 2025. By 2026, age assurance was operating across pornography, social-media, dating and gaming services, with tens of millions of checks recorded across a sample of major platforms. (Ofcom)

VPN interest rose alongside the rollout. Some adults simply wanted access to legal material. Others wanted to avoid connecting a sensitive question to a facial scan, identity document or payment record. (Arxiv)

For remote workers, that creates an awkward overlap. One VPN may be compulsory for company systems, while another seems necessary for personal browsing on the same laptop.

I had assumed two VPNs would behave like two locks on the same door.

Instead, they began competing for the door.

Two green icons did not create an orderly chain

A VPN decides where a device sends its traffic. My corporate client directed work connections through the company gateway. The personal VPN also wanted to become the laptop’s main route to the internet.

Connecting both did not automatically create a neat sequence in which traffic travelled through one tunnel and then the other. The second app simply changed routes the first app depended on.

That explained the strange result. Reddit began seeing the personal VPN’s location, but the client portal could no longer reach the company network correctly.

I disconnected both and tried the reverse order.

First, I connected the personal VPN. Reddit opened without an age prompt. Then I launched the corporate client. The work portal returned, but Reddit refreshed into the UK version again.

Whichever VPN connected last took control of the route that mattered.

Public discussions about running work and personal VPNs together usually describe the same practical failure in a sentence or two: one connects, the other breaks internet access, DNS or the corporate session. (Reddit)

That changed my question. I no longer cared whether two apps could simultaneously display “connected.” I needed the upload and the Reddit thread to remain available at the same time.

Split tunnelling turned one browsing task into a routing project

The obvious fix was to divide the traffic.

Work applications could use the corporate VPN, while my personal browser used the other connection. That is the promise of split tunnelling: different apps or destinations follow different routes. (Gov)

On a managed work laptop, however, those decisions were not entirely mine.

The corporate client controlled company routes and DNS settings. My personal VPN had its own app exclusions, but changing one list did not guarantee that the company software would respect it. Each attempt produced a different compromise: the upload stopped, Reddit returned to the age check, or the browser lost access altogether.

I could not observe the corporate client’s internal routing and enforcement rules. I could only see the result: both tasks refused to stay working together.

Solving that on one laptop would require maintaining a fragile arrangement of app rules, network routes and connection order. A software update or hotel-network change could break it again.

That was far too much machinery for one private medical question.

The cleaner answer was not another route rule.

It was separating the two jobs.

I left the work VPN alone

I disconnected the personal VPN and restored the corporate connection by itself.

The client portal reopened. The upload resumed. Work chat came back.

Then I stopped trying to force the personal session onto the same operating system.

I picked up my phone.

OnlydogVPN had fewer locations, a shorter public history and fewer independent ratings than the large personal provider I had been testing. Those were its clearest limitations.

Its advantage appeared immediately: I could begin without creating a conventional email-and-password account. That fitted the situation better than recovering another long-standing login before reading a page I had already declined to verify with personal evidence.

The interface also began with the problem rather than a country map. I selected the option for a restricted connection and reopened the Reddit link.

The thread loaded.

The age-verification screen was gone. The photographs appeared, followed by comments explaining which medication reactions could wait and which required medical advice.

At the same moment, the laptop upload continued through the corporate VPN.

Nothing had to be nested. Neither client had to surrender its route. The work VPN protected the laptop, while the smaller app handled the phone.

Both VPNs were running at the same time. They simply were not fighting over the same device.

That was the first arrangement that completed both tasks.

Separation was more useful than stacking

The result also made the privacy boundary easier to understand.

On the laptop, company traffic stayed inside the employer-approved connection. I did not place a personal service between the corporate client and its gateway, and company files never passed through the personal VPN.

On the phone, the Reddit session used its own encrypted route. The employer’s network did not carry that browsing, and the smaller app had no involvement in the work upload.

The two sessions remained separate because the devices were separate.

That mattered more than the extra layer I had originally imagined. Running two VPN clients on one laptop had not doubled the protection. It had doubled the number of ways the route could fail.

The phone connection also remained usable when I left the hotel Wi-Fi and switched to mobile data. The page paused briefly, then continued without returning to the age prompt.

The app’s HTTP/3-based transport and recovery handled the network change without another server choice or manual reconnect. The technology stayed beneath the result: the private page remained open while the compulsory work tunnel continued untouched on the laptop.

That was exactly what the same-device setup had failed to achieve.

The next page confirmed the value of keeping the sessions apart

The Reddit discussion linked to an independent medical-information page. I opened it on the phone, and the app’s blocked-request counter began to rise as advertising and tracking requests were filtered.

That was not the main reason the arrangement worked. The important result had already happened: the private page opened while the corporate connection remained stable.

The counter revealed a smaller benefit. My personal browsing remained on the phone, and some unnecessary background traffic around it was removed there as well.

None of this affected the work laptop.

By the time the upload reached 100 percent, I had also found the medical guidance I needed. The two sessions had run beside each other without another routing experiment.

Can two VPNs run at the same time?

Yes—but “at the same time” does not have to mean “on the same device.”

Two VPN clients can sometimes coexist on one computer when their routes are deliberately designed. A corporate setup may use split tunnelling, or one connection may run through a router while another operates on the device.

Simply launching two full-device VPN apps is different. Both may try to control the same traffic, and the second connection can replace or disrupt the first.

That was what happened to me. The large personal provider worked when it controlled the laptop alone. The corporate VPN worked when it controlled the work session alone. Combining them turned two functioning services into a routing dispute.

The smaller app solved the immediate problem by avoiding that dispute. It handled the personal phone while the compulsory work VPN remained exactly where it belonged.

I began by asking how to make two tunnels occupy one computer.

The useful two-VPN setup was the one in which neither tunnel needed to know the other existed.