Setting up a VPN server isn’t just for the pros—and trust me, I’m no Linux guru. But when a friend needed a secure way for his employee to work remotely, I stepped up to see what I could build with old hardware, free tools, and a bit of stubbornness.
The Setup
- Hardware: Old Toshiba i3 laptop, 8 GB RAM, SSD
- OS: Ubuntu 24.04 LTS (with GNOME desktop installed to help with navigation)
- Purpose: Enable one employee to work remotely from home
- Client Limit: OpenVPN’s free license allows two simultaneous connections—perfect for this use case
Once I had SSH configured, I shifted over to my Windows desktop to continue setup remotely. The goal: turn this aging laptop into a functioning OpenVPN Access Server.
Trial and Error (A Lot of It)
I started with various community guides to install OpenVPN manually:
- Added the OpenVPN repository
- Generated certificates
- Configured initial settings and user permissions
But every time I thought I was close, something would go sideways. I failed five times, each time trying to troubleshoot—but eventually I just wiped the system and started fresh. Each rebuild taught me a little more and gave me confidence with Linux commands.
The Turning Point: OpenVPN’s Official Installer
The real breakthrough came when I realized that OpenVPN offers a full installation script and web-based GUI—you just need to sign up for a free account on their site.
Lesson learned: Once you register on the OpenVPN website, they provide an official
.shinstallation script (openvpn-as-x.x.x.sh) that simplifies the entire setup process. It was a game-changer.
After running the script, I accessed the web-based admin panel and finished the configuration through the GUI. It was miles easier than doing it all manually.
Domain Setup & DNS
To make it more professional for the end user, I set up a subdomain:
- Created
vpn.theirdomain.com - Added a corresponding A record pointing to the public IP of the office connection
This made accessing the VPN service much cleaner and easier for the remote employee.
The One Real Challenge: Networking
The hardest part? Double NAT issues—which I wasn’t expecting.
Here’s what went wrong:
- My test environment and the employee’s home router both used the same common private IP range (
192.168.1.x) - When the VPN tunnel connected, there was a conflict with the overlapping networks
- Routing got confused, and nothing worked
The Fix:
We moved the OpenVPN Access Server into the actual office network, where the internal IP range was something different (10.x.x.x). Since that range doesn’t overlap with common home routers, the conflict disappeared.
Pro Tip: Avoid using
192.168.0.xor192.168.1.xfor test environments or internal networks if you’re setting up VPN tunnels—these are extremely common on home routers and will likely clash.
What I Learned
- Rebuilding is part of learning—each wipe and reinstall gave me more insight.
- The OpenVPN GUI and installer are beginner-friendly and saved hours of trial and error.
- Networking problems are the real beast, not the VPN software itself.
- Tech support matters—OpenVPN’s support team (via their ticket system) helped me understand the double NAT issue and walked me through a fix. They didn’t just fix it for me—they explained it in a way that helped me grow.
Final Thoughts
Would I recommend OpenVPN Access Server?
Absolutely. Especially if:
- You’re on a tight budget
- You want to repurpose aging hardware
- You need a secure, stable remote work solution for a small team
When I set one up for my own home network, I’m going straight to that .sh installer and leveraging everything I’ve learned through this journey. No question—it was worth the effort.