Skip to content
A simple VPN allowing mesh-like communication between nodes, over websockets
Branch: master
Clone or download
skx Minor update.
Fixed bug in #17, confirmed #19 is a non-issue.

Buffering in the logs is to blame for the apparent omission.
Latest commit 5057921 Apr 7, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Updated tests to run linter/variable shower. Mar 24, 2019
_media Added simple overview image Nov 21, 2018
config Imported source now I'm happy. Nov 23, 2018
etc Mention how the IPv6 stuff works. Feb 23, 2019
shared Updated to resolve linter-errors Feb 28, 2019
systemd Added systemd-files for the vpn-server Nov 21, 2018
.gitignore Ignore generated binary Nov 21, 2018
LICENSE Imported source now I'm happy. Nov 23, 2018 Document installation Mar 24, 2019
cmd_client.go Minor update. Apr 7, 2019
cmd_server.go Minor update. Apr 7, 2019
go.mod Added go module files. Mar 24, 2019
go.sum Added go module files. Mar 24, 2019
main.go Imported source now I'm happy. Nov 23, 2018

Go Report Card license Release


This project is a VPN-server, written in golang, using websockets as a transport. The idea is that multiple-nodes each connect to a central VPN-server, and once connected they can talk to each other securely, regardless of their location.

The following image illustrates the expected setup:

  • Three hosts each connect to the central VPN host.
  • Once they're connected each of those hosts can then talk to the other machines which are also connected.
    • (Their private traffic is routed to the central hub, from there sent back out.)


While it is possible to use this software to mask your laptop's IP while traveling, instead showing the IP of the VPN-server as being the source of connections that is not the expected use-case. (Nor is it documented!)

It should be noted that the VPN-server will become a single point of failure if you're using it to join (say) a database-host located at Hetzner with a number of webserver-nodes split between Linode and Digital Ocean, but being a simple service, easy to deploy, it should be trivial to spin up a replacement in a hurry.


There are two ways to install this project from source, which depend on the version of the go version you're using.

Alternatively you can download the latest release from our releases page if you're running upon AMD64-GNU/Linux host. (Unfortunately we use CGO, and the water-library, which makes our code non-portable for now.)

Source Installation go <= 1.11

If you're using go before 1.11 then the following command should fetch/update overseer, and install it upon your system:

 $ go get -u

Source installation go >= 1.12

If you're using a more recent version of go (which is highly recommended), you need to clone to a directory which is not present upon your GOPATH:

git clone
cd simple-vpn
go install

Encryption & Overhead

The VPN-server does not implement any kind of encryption itself, nor does it handle access-control beyond the use of a shared-secret. Is this insane? Actually no.

The expectation is that you'll host the VPN-server behind an nginx/apache proxy and you'll add TLS there (i.e. Let's Encrypt). Providing all the clients connect to the server over a TLS/SSL-protected socket then things are secure:

  • The use of TLS prevents traffic from being sniffed.
    • This means that the connections made from one host, to another, over their private network will be unreadable to hosts in the same location.
  • The use of a shared-secret prevents rogue agents from connecting to your VPN-server.
    • This means a user cannot join your private network and attempt to sniff traffic that way.

I believe this solution is "secure enough", but if you have concerns you can ensure that all the traffic you send over it uses TLS itself, for example database-connections can use TLS, etc.

Because traffic routed between two nodes on their private IP addresses has to be routed via the VPN-server expect to see approximately 50% overhead.

VPN-Server Setup

Configuring a VPN server requires two things:

  • The simple-vpn binary to be running in server-mode..
    • This requires the use of a simple configuration-file.
  • Your webserver to proxy (websocket) requests to it.
    • You must ensure that your webserver uses TLS to avoid sniffing.

A minimal configuration file for using simple-vpn in server-mode looks like this:

With your configuration-file you can now launch the VPN-server like so:

 # simple-vpn server ./server.cfg

To proxy traffic to this server, via nginx, you could have a configuration file like this:

server {
    listen [::]:443  default ipv6only=off ssl;

    ssl on;
    ssl_certificate      /etc/lets.encrypt/ssl/;
    ssl_certificate_key  /etc/lets.encrypt/ssl/;
    ssl_dhparam          /etc/nginx/ssl/dhparam.pem;

    ssl_prefer_server_ciphers on;
    ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
    add_header Strict-Transport-Security "max-age=31536000";

    proxy_buffering    off;
    proxy_buffer_size  128k;
    proxy_buffers 100  128k;

    ## VPN server ..
    location /vpn {

       proxy_set_header      X-Forwarded-For $remote_addr;
       proxy_pass  ;
       proxy_http_version    1.1;
       proxy_set_header      Upgrade $http_upgrade;
       proxy_set_header      Connection "upgrade";
       proxy_read_timeout    86400;
       proxy_connect_timeout 43200000;

       tcp_nodelay on;
  • You don't need to dedicate a complete virtual host to the VPN-server, a single "location" is sufficient.

VPN-Client Setup

Install the binary upon the client hosts you wish to link, and launch them with the name of a configuration-file:

# simple-vpn client client.cfg

There is a sample client configuration file here:

The configuration file has two mandatory settings:

  • key
    • Specifies the shared key with which to authenticate.
  • vpn
    • Specifies the VPN end-point to connect to.

Advanced Configuration

The server will assign each client which connects the next unused IP address from the range it is configured to serve.

Because each client identifies itself with the hostname of the local system it is possible to map static IP addresses to any remote host, which is useful if you wish to setup DNS entries, etc.

To setup a static IP see the commented-out sections in the server.cfg file.

Github Setup

This repository is configured to run tests upon every commit, and when pull-requests are created/updated. The testing is carried out via .github/ which is used by the github-action-tester action.

Releases are automated in a similar fashion via .github/build, and the github-action-publish-binaries action.


You can’t perform that action at this time.