It's not often that I find a very complete setup guide that covers many aspects of what I want to achieve. However, digitalocean's guide for setting up an openvpn server is excellent and very well written. It covers many (most) of the things I implement on any openvpn server I setup.
In this writeup I'll simply cover some of the things that aren't in digitalocean's guide and that I usually implement to meet specific use cases.
If you're setting up an openvpn server, please check out their guide and follow along. Much of what I cover here would depend on a setup similar to what is outlined by digitalocean.
Generating client configurations
This is covered well in the digitalocean guide, but I thought I would note down the commands used here as it's something I use/do often.
First, generate the client key by cd'ing into your openvpn-ca (cert authority folder) and sourcing the variables required:
Do NOT run
./clean-all unless you really want to remove all client keys (seriously, I've done this by mistake and you will then need to recreate or restore previous keys).
Then simply generate a client key with
replace <client-key-name> with the name of the client key you want
If you followed the digitalocean guide you'll now be able to generate an
ovpn client config that contains the key and everything needed for a client to securely connect to your openvpn server by
This will create a client key in
~/client-configs/files that can be transferred to the client.
Assigning static IP addresses to particular client configurations
You might want/need to map certain client configurations to a static ip address in the openvpn ip pool. For this use case you would generally have a ip range for static ip addresses, and a separate (non-conflicting) range for dynamic ip address assignment (i.e. standard clients connect and receive an dynamic ip address subject to availability).
Such a configuration requires several changes to
server.conf and the creation of a folder which holds a client-name config file (which contains the static ip address to assign) for each config you wan to assign a static ip address to.
Here we'll do two things, define an ip address range for dynamic assignment, and enable the folder to hold client static ip address files.
Let's start with changing the dynamic ip range. For this example we're going to set the dynamic ip range from 10.8.0.100 to 10.8.0.200:
Next, let uncomment the
You'll note that I give the absolute path to the ccd folder (just my preference).
Don't forget to actually create the ccd folder:
Let's now restart openvpn
Create files for each client you want to assign an ip address to
Here we simply add a file, which must have the same name as the client configuration.
For example, suppose we have a client configuration named "client1" which has the ovpn file "client1.ovpn", that we want to assign the ip address "10.8.0.1" to. We would do the following:
and then add the following line
You DO NOT need to restart the openvpn server after adding client configs. Each time a client connects openvpn will check for a corresponding (named) file in the ccd folder.
Overriding DNS settings for server in client configutation
server.conf allows you to define DNS addresses such as addresses for OpenDNS etc. These addresses with then be pushed to the client to implement when it connects to the server.
However, you might want/need to use different DNS servers for your client. This can be done easily by rejecting the server's pushed DNS addresses and implementing your own directly in your .ovpn config file.
Add the following to you .ovpn config (replacing
y.y.y.y with your preferred DNS addresses).
y.y.y.y with your preferred DNS addresses above.
If OpenVPN doesn't reconnect after wake
On one of my laptops (running Manjaro) the openvpn client wouldn't reconnect after waking from sleep. As outlined in the Arch wiki, you can quickly add a systemd service which sends a
SIGHUP signal to OpenVPN which forces a reconnect to occur:
then enable the service:
Recovering after an accidental
Using port 443 for OpenVPN & other applications (like a webserver)