Setting Up a VPN the Skeptical Way: Private Internet Access, Verified End to End

Most VPN guides are a download button wearing a tutorial costume. They tell you to click, log in, and trust that a green icon means secure. This one goes the other way: every step below has a reason attached, and nothing counts as "done" until you have proven with your own commands that traffic is actually leaving through a tunnel — not just that an icon changed colour.

What a VPN Actually Does (and Doesn't)

A VPN creates an encrypted tunnel between your machine and a server run by the provider. Everything in transit between those two points is unreadable to everyone on the path: the café Wi-Fi, your ISP's middleboxes, the office network. That part is real and worth having.

What it does not do is hide you from the sites you visit. Log into your email through a VPN and the mail service still sees your account, your device and your browsing habits — it just can't see which network you were sitting on. Your ISP can still see you are connected to a VPN server; they just cannot read what goes through it. A VPN is a tool for encrypting traffic in transit and changing which network your traffic exits from. It is not an invisibility cloak, and any guide that sells it as one is selling something else.

PIA states it keeps no logs of user activity. That is a quote of their policy, not an independent audit — read the privacy policy yourself and decide how much weight to give it before you hand over your traffic.

A photorealistic wide shot of a home desk at dusk with a laptop and a small Wi-Fi router on it, one soft desk lamp glowing from the left and blurred city lights through the window behind, calm and thoughtful mood, no visible text or letters.

Step 1 — Get an Account

Create the account at Private Internet Access's purchase page. They accept card, PayPal and crypto payments; pricing changes over time, so read what the page actually shows rather than trusting any number in a blog post. Disclosure: buying through the links on this site earns the site a commission; it does not change what I think of the product.

Step 2 — Download From the Domain, Verify the File

Download the client from PIA's website — and only from the privateinternetaccess.com domain. If a "PIA download" link arrived in an email or an ad, it is not this file. This is the part everyone skips: don't trust the download button; trust the hash. If a SHA-256 checksum is published next to the download, compute yours and compare:

certutil -hashfile PIA-installer.exe SHA256

certutil ships with Windows, so this runs on any machine. A mismatch means the file you got is not the file they built — stop, do not install it, and re-download from the official page.

Step 3 — Install (Yes, the Driver Prompt Is Normal)

Run the installer. At some point Windows will ask permission to install a network driver — a TAP adapter for the OpenVPN path. That is expected: an encrypted tunnel needs a virtual network interface to push traffic through, so approve it. The client may also register a service so it starts with the machine — normal for this kind of software, and confirmable in Device Manager and Services if you want to see what landed.

Step 4 — Log In With Your Account Credentials

Launch the app and sign in with the email and password from step 1 — not some separate "VPN username". PIA uses your account credentials directly, which is one fewer secret to lose track of. If the login page ever asks for a different set of details than the ones on your account, that is a reason to stop and re-check you are on the real domain.

A photorealistic close-up of a hand typing on a laptop keyboard at a tidy home office desk, warm overhead task-light glow, shallow depth of field with a coffee mug and a notebook softly blurred in the background, focused and methodical mood, no visible text or letters.

Step 5 — Prove It Is Actually Tunneling

This is the step every guide skips and the only one that matters. Before connecting, note your public IP address:

curl ifconfig.me

Windows 10 and later ship with curl, so this runs in a plain Command Prompt or PowerShell. Now connect from the client, wait for it to report connected, and run the same command again. The two addresses must be different — the second one is the VPN server's address, not yours. If they are identical, nothing on your network actually changed, and no amount of green icons means anything.

You can cross-check the same way from a browser: PIA's main site shows the IP address your traffic is exiting through while connected. Two independent checks agreeing is what "verified" looks like.

Step 6 — Turn On Disconnect Protection

In the client settings, find the kill-switch-style option (PIA's Windows client calls it disconnect protection) and enable it. Here is why: if the tunnel drops for a moment — a Wi-Fi hiccup, a server failover — your traffic has to go somewhere. With the protection off, it silently goes straight out over your real connection with your real IP still attached. With it on, traffic stops until the tunnel is back. You lose a few seconds of browsing; you do not leak.

Step 7 — Leave the Encryption Alone

The modern client negotiates strong defaults (WireGuard or OpenVPN depending on the version and the server) and there is no setting in here a normal user should be turning down. If you open the advanced encryption panel and start picking ciphers, you are not getting more secure — you are getting more likely to misconfigure. The one choice worth understanding is the protocol: if your client offers WireGuard it is a sensible default for everyday use, and OpenVPN remains a solid fallback where WireGuard is not available.

If the "trust no provider" itch is genuinely strong, there is an honest alternative: run WireGuard yourself on a small VPS you pay for directly. You own every byte of the path, and the setup is a few config lines instead of a GUI. It is more work and it is not for everyone — but it is the same protocol doing the same job with no middleman to read the policy on.

A photorealistic shot down a dim data centre corridor with a small server rack in the foreground, cool blue LED status lights reflecting off the polished floor, long perspective into the distance, quiet and serious mood, no visible text or letters.

What This Setup Will Not Do

Be clear-eyed about what you just built: traffic between your machine and the VPN server is encrypted, your exit point is a server you chose, and if the tunnel dies nothing leaks out unencrypted. That is it. Your accounts still know who you are, your ISP still sees the connection to the VPN, and any provider can be pressed by whoever has jurisdiction over it. The value is real — public Wi-Fi, travel networks, a landlord's router, an office that snoop on traffic — but it is a specific value, not blanket anonymity.

Set it up, run the two-IP check whenever something feels off, and you will have a working encrypted tunnel you actually understand. That beats a green icon you are just hoping for.


Luke Keam
Spot a bug or want a custom utility built? I'd love to hear from you. Get in touch
Luke Keam | techgeek.biz