Build a VPN between Servers; with cloud solutions like Kubernetes, securing data between datacenters and disconnected servers is critical. Even for a simple WordPress website there are reasons to have VPN. For example, LDAP authentication. My current site https://wp.alshowto.com uses FreeIPA and an LDAP authenticator to allow me to setup a single sign on with users that I have in FreeIPA. So, this article “WordPress 101: Step 4 – Build a VPN between servers” addresses that scenario with VpnCloud. Oh, and this should be run after WordPress 101: Step 3 – Vanilla Baseline Server Install as that process sets up all needed deb packages.
What is a VPN?
It is a virtual private network. So, to the servers they look like they are on the same lan even though one is in California and another is in New York. Now remember, vpn’s do not have to be secure. However, why bother then? All the data would be scannable and in some cases free text passwords are sent in URLs. So, in best practice. It is best to always secure your vpn with encryption. Then all the data sent can be in the clear without worry about hackers sniffing the network and getting passwords or credit card info. Point to point encryption is easy to set up in vpnCloud.
What is vpnCloud?
Simply, one of many options to secure point to point traffic between computers. In this scenario, it is a peer to peer network with static configuration between nodes. There are many different modes and ip levels VpnClound can run in allowing some complex setups that even share DHCP info to assign addresses. Now, for our setup that is not needed. Remember, this is WordPress 101 and so examples here are to get the basics going.