Contabo VPN: self-host WireGuard on a Contabo VPS (2026 guide)

How to run your own VPN on Contabo: step-by-step WireGuard setup on a Cloud VPS 4 (shown from €5.50/month on contabo.com, checked 17 Oct 2026). Bootstrap scripts, UFW, fail2ban, clients for every OS, honest limits vs a commercial VPN.

By Eric GerardFounder · VPNSmith - Self-host VPN & GDPR VPS specialist

Updated 18 min read18 min

Affiliate links: we may earn a commission, at no extra cost to you. Method

See the installation stepsGenerate my config

fig. 01 / self-host-vpnencrypted tunnelUDP 51820DEVICE10.8.0.2SERVER10.8.0.1INTERNETNATAllowedIPs = 0.0.0.0/0, ::/0ListenPort = 51820 (server)
fig. 01 / self-host-vpn

Contabo does not sell a VPN. It is a German hosting company that rents VPS and dedicated servers. A "Contabo VPN" means renting a Contabo Cloud VPS (from €5.50/month excl. VAT) and installing WireGuard on it yourself: about 20 minutes, an IP used by you alone, and a server you control. This guide gives every command.

Black Friday 2026VPN prices read on 16 Nov: Proton VPN Plus $59.76 for 24 months, Surfshark €67.23 for 27 months, next to a self-hosted VPS. See the dated comparison · Get the Proton VPN deal (affiliate link) · Proton Unlimited at $6.49 a month: the bundle, priced

fig. 01 / self-host-vpnencrypted tunnelUDP 51820DEVICE10.8.0.2SERVER10.8.0.1INTERNETNATAllowedIPs = 0.0.0.0/0, ::/0ListenPort = 51820 (server)
fig. 01 / self-host-vpn

Ordering in November? On Black Friday 2025 Contabo listed 25% off long-term VPS plans, about 33 € saved on a 24-month Cloud VPS 4 if 2026 repeats it. What the 2024 and 2025 pages actually said, and when waiting is not worth it: Contabo Black Friday 2026.

Every command below works the same on any Ubuntu VPS.

Tired of paying NordVPN €139.08 a year once the promo plan ends. You want an encrypted tunnel shared with no one, hosted in a GDPR jurisdiction, whose configuration you control line by line. Good news: it stands up in 20 minutes on a Contabo VPS at 5,50 €/month (contabo.com, 18 October 2026), and this guide gives you every command. No marketing, no abstraction - just the exact script.

Short on time? Once the VPS is up, our free WireGuard config generator writes the server wg0.conf and the client configs from your server IP, subnet and peer count, with keys generated in your browser. The steps below explain every command, so you know exactly what you are pasting. The generator is free with no account, up to 250 devices, and its ZIP export holds every client .conf and its QR code as a PNG, handy to set up a whole office or family in one go.

Generate your WireGuard configs here

Type your server address, choose the number of devices, then scan each QR code from the app.

All keys are generated in your browser (Curve25519 / X25519). Nothing is sent to our servers - your config stays 100% private.

Public IPv4 or domain of the machine that will run WireGuard. No server yet? Leave it empty and add it later.

Free, no account: up to 250 clients, each .conf with its QR code, and one ZIP with every file.

Everything the device sends to the internet goes through your server.

Advanced settingsTunnel subnet, DNS, site-to-site LANs. The defaults work for most setups.

Optional. Enter the LAN subnet behind the server and/or behind a client that acts as a site gateway (a router, a Raspberry Pi, a NAS). The generator adds each LAN to the server's AllowedIPs, gives every peer the routes to the other LANs, and writes the forwarding rules on the gateways. Leave a field empty for a normal client.

What you download

  • wg0.conf

    for the server

  • client1.conf

    one per device

  • QR (sample)

    for the phone app

Illustration only: the lines and the QR code are fictional, no real key. Your real files are generated in your browser when you click.

How do you self-host a VPN with WireGuard on a VPS?

Self-hosting a WireGuard VPN takes about 20 minutes: provision a Contabo Cloud VPS 4 (5,50 €/month, Ubuntu 24.04), run apt install wireguard, generate server keys, write a 10-line wg0.conf with subnet 10.66.66.0/24 on port 51820, enable IP forwarding, and add NAT via iptables. Cost: about €66/year vs ~€511 for NordVPN over 5 years.

Why self-host a VPN instead of paying for one?

A commercial VPN sells you a promise: no logs, shared IP across thousands of users, "no-logs friendly" jurisdiction (Panama, BVI, Switzerland). On paper it's solid. In practice:

  • Shared IP = shared reputation. When thousands of users exit through the same IP, you inherit their blacklists. Stripe will ask for an extra 3DS. Cloudflare will serve you endless challenges. You host your own VPN = your own clean IP.
  • No-logs unverifiable in real time. A PwC audit validates a policy at one moment. Between audits, court orders (US subpoenas, EU orders) can force temporary logging. On your VPS, you decide. You purge whenever you want.
  • Prices that double on renewal. NordVPN Basic 2-year plan: €94.23 for 27 months. Yearly renewal: €139.08. Over 5 years: ~€511 (nordvpn.com, 19 October 2026, excl. VAT). A Contabo Cloud VPS 4 over 5 years: ~€330. And you can host other services on it.

The honest tradeoff: you won't unblock Netflix US with a dedicated VPS (Netflix bans datacenter ASNs). For streaming, we document a hybrid solution in the DPI bypass guide.

Which Contabo VPS do you need for a VPN?

Contabo offers three relevant ranges for a personal VPN (list prices re-read on contabo.com on 18 October 2026, first 24 months, excl. VAT):

PlanPrice/movCPURAMStorageBest for
Cloud VPS 45,50 €48 GB100 GB SSDSolo VPN 1-3 devices
Cloud VPS 67,50 €612 GB100 GB NVMeFamily VPN 5-10 devices
Cloud VPS 814 €824 GB200 GB NVMeMulti-tunnel + extra services

Our default pick: Cloud VPS 4 at 5,50 €/mo. For most individual uses, more than enough. Contabo lists a 200 Mbit/s port for this plan (contabo.com, 19 October 2026): that is a ceiling, not a guarantee, and your tunnel will not go faster. If your home line is faster than 200 Mbit/s, the Cloud VPS 6 (300 Mbit/s port) or Cloud VPS 8 (600 Mbit/s port) is the step up. Run iperf3 yourself for real numbers on your connection. Check the current Cloud VPS 4 price on Contabo.

Recommended datacenter: Nuremberg (DE) for low latency from continental Europe. If you're in Canada/US, pick US Central (St. Louis).

How do you install WireGuard on a Contabo VPS?

Step 1 - Provision the VPS

On Contabo, pick Cloud VPS 4, Ubuntu 24.04 LTS, root password (we'll create a normal user later), Nuremberg datacenter. Pay via card or PayPal. Activation: email within ~5 minutes with the public IP and root password. If you would rather start from your own prepared system instead of Contabo's Ubuntu image, see Contabo custom images: formats and requirements.

Shortcut: Contabo also sells the same Cloud VPS 4 as a WireGuard Server, with WireGuard and the WGDashboard web panel installed by a 1-click Cloud-Init script at order time (same 5,50 € per month over 24 months, contabo.com, 20 October 2026). It replaces Step 3, not Step 2: harden the server anyway, then check the generated config (port, AllowedIPs, DNS) against Step 3 before adding peers.

Step 2 - Harden the server

First SSH connection:

ssh root@YOUR_PUBLIC_IP
# Password is in the Contabo email

Create a non-root user, add your SSH key, disable root login:

adduser ericg
usermod -aG sudo ericg
mkdir -p /home/ericg/.ssh
# Paste your public key (~/.ssh/id_ed25519.pub locally)
nano /home/ericg/.ssh/authorized_keys
chmod 700 /home/ericg/.ssh
chmod 600 /home/ericg/.ssh/authorized_keys
chown -R ericg:ericg /home/ericg/.ssh

# Disable root + password login
sed -i 's/^PermitRootLogin .*/PermitRootLogin no/' /etc/ssh/sshd_config
sed -i 's/^#PasswordAuthentication.*/PasswordAuthentication no/' /etc/ssh/sshd_config
systemctl restart ssh

Exit the root shell, reconnect via ssh ericg@YOUR_IP. If it works, continue.

Install firewall and fail2ban:

sudo apt update && sudo apt upgrade -y
sudo apt install -y ufw fail2ban
sudo ufw default deny incoming
sudo ufw default allow outgoing
sudo ufw allow 22/tcp
sudo ufw allow 51820/udp
sudo ufw --force enable
sudo systemctl enable --now fail2ban

Step 3 - Install and configure WireGuard

sudo apt install -y wireguard qrencode

# Server key generation
cd /etc/wireguard
sudo wg genkey | sudo tee server_private.key | sudo wg pubkey | sudo tee server_public.key
sudo chmod 600 server_private.key
SERVER_PRIV=$(sudo cat server_private.key)

Identify your public interface (often ens3 or eth0):

ip route | grep default
# default via X.X.X.X dev ens3 ...

Create /etc/wireguard/wg0.conf:

sudo nano /etc/wireguard/wg0.conf

Content (replace ens3 with your interface if different):

[Interface]
PrivateKey = PASTE_SERVER_PRIV_HERE
Address = 10.66.66.1/24
ListenPort = 51820
PostUp = iptables -A FORWARD -i %i -j ACCEPT; iptables -A FORWARD -o %i -j ACCEPT; iptables -t nat -A POSTROUTING -o ens3 -j MASQUERADE
PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -D FORWARD -o %i -j ACCEPT; iptables -t nat -D POSTROUTING -o ens3 -j MASQUERADE

Enable IP forwarding:

echo "net.ipv4.ip_forward=1" | sudo tee -a /etc/sysctl.conf
sudo sysctl -p

Start WireGuard:

sudo systemctl enable --now wg-quick@wg0
sudo wg show
# You should see "interface: wg0" and "listening port: 51820"

Step 4 - Generate a client

For each device:

cd /etc/wireguard
sudo wg genkey | sudo tee macbook_private.key | sudo wg pubkey | sudo tee macbook_public.key
CLIENT_PRIV=$(sudo cat macbook_private.key)
CLIENT_PUB=$(sudo cat macbook_public.key)
SERVER_PUB=$(sudo cat server_public.key)

Create /tmp/macbook.conf (on the server, to generate the QR - then delete):

[Interface]
PrivateKey = PASTE_CLIENT_PRIV
Address = 10.66.66.2/24
DNS = 1.1.1.1, 9.9.9.9

[Peer]
PublicKey = PASTE_SERVER_PUB
Endpoint = YOUR_PUBLIC_IP:51820
AllowedIPs = 0.0.0.0/0
PersistentKeepalive = 25

Add this peer to the server:

sudo wg set wg0 peer PASTE_CLIENT_PUB allowed-ips 10.66.66.2/32
# And persist:
sudo nano /etc/wireguard/wg0.conf
# Append at the bottom:
# [Peer]
# PublicKey = PASTE_CLIENT_PUB
# AllowedIPs = 10.66.66.2/32

For iOS/Android: generate the QR code

qrencode -t ansiutf8 < /tmp/macbook.conf

Scan with the official WireGuard app. Toggle on. You're done.

Step 5 - Verify no leaks

On your client connected to the tunnel:

  1. Go to ipleak.net - IP must be the Contabo VPS, not yours.
  2. Go to browserleaks.com/webrtc - no local IP exposed.
  3. Go to dnsleaktest.com - DNS resolved via 1.1.1.1 (Cloudflare).

If a WebRTC leak shows: enable kill switch in WireGuard mobile ("On-Demand"), or block WebRTC in Firefox (about:config → media.peerconnection.enabled → false).

How do you harden a self-hosted VPN server?

Two failures account for most "my self-hosted VPN is broken" reports, and both are measurable rather than guessable. If small requests work but large transfers stall, the interface MTU is wrong for the path, mtu-probe finds the largest packet your link actually carries, and you subtract 60 bytes for WireGuard over IPv4. If a second device joins and the first drops, the two configs collide, wg-clients-audit reads a folder of client configs and reports duplicate addresses, reused keys and over-broad AllowedIPs.

Recommended production hardenings:

  • Lynis audit: sudo apt install lynis && sudo lynis audit system. Target score: 80+/100.
  • SSH on custom port: change /etc/ssh/sshd_config port 2222, update UFW.
  • Disable IPv6 if unused: sudo sysctl -w net.ipv6.conf.all.disable_ipv6=1 (persist in sysctl.conf).
  • Minimum logs: by default, journald retains 4 weeks. Reduce to 7 days via /etc/systemd/journald.conf if threat model is strict.
  • Contabo backups: enable automatic snapshots in the Contabo panel (€1/mo, not for logs but for quick recovery after a mishap).

Can you automate the setup with Ansible?

Server racks lit in blue in a data center
Server racks lit in blue in a data center

If you plan to provision more than one VPS - or just want to rebuild your tunnel in a few minutes after an incident - automating via Ansible avoids retyping the commands above. Here is a playbook for that. It is idempotent (safe to rerun) and written for Ubuntu 24.04 LTS.

Local prerequisites

# On your laptop
pip install --user ansible
mkdir -p ~/vpn-ansible && cd ~/vpn-ansible

Create inventory.yml (replace the IP with the one Contabo emailed you):

all:
  hosts:
    vpn1:
      ansible_host: YOUR_PUBLIC_IP
      ansible_user: root
      ansible_python_interpreter: /usr/bin/python3

The playbook.yml

---
- name: Bootstrap VPNSmith WireGuard on Contabo
  hosts: vpn1
  become: yes
  vars:
    admin_user: ericg
    admin_ssh_key: "{{ lookup('file', '~/.ssh/id_ed25519.pub') }}"
    wg_subnet: "10.66.66.0/24"
    wg_port: 51820
  tasks:

    - name: Update apt cache
      apt:
        update_cache: yes
        cache_valid_time: 3600

    - name: Upgrade all packages
      apt:
        upgrade: dist
        autoremove: yes

    - name: Install hardening + WireGuard packages
      apt:
        name:
          - ufw
          - fail2ban
          - wireguard
          - qrencode
          - unattended-upgrades
        state: present

    - name: Create admin user
      user:
        name: "{{ admin_user }}"
        groups: sudo
        shell: /bin/bash
        password: "!"

    - name: Authorize admin SSH key
      authorized_key:
        user: "{{ admin_user }}"
        key: "{{ admin_ssh_key }}"
        state: present

    - name: Disable SSH root login + passwords
      lineinfile:
        path: /etc/ssh/sshd_config
        regexp: "{{ item.regex }}"
        line: "{{ item.line }}"
      loop:
        - { regex: '^#?PermitRootLogin', line: 'PermitRootLogin no' }
        - { regex: '^#?PasswordAuthentication', line: 'PasswordAuthentication no' }
      notify: restart ssh

    - name: Configure UFW default policies
      ufw:
        direction: "{{ item.direction }}"
        policy: "{{ item.policy }}"
      loop:
        - { direction: incoming, policy: deny }
        - { direction: outgoing, policy: allow }

    - name: Allow SSH + WireGuard through UFW
      ufw:
        rule: allow
        port: "{{ item.port }}"
        proto: "{{ item.proto }}"
      loop:
        - { port: 22, proto: tcp }
        - { port: "{{ wg_port }}", proto: udp }

    - name: Enable UFW
      ufw:
        state: enabled
        policy: deny

    - name: Enable IP forwarding
      sysctl:
        name: net.ipv4.ip_forward
        value: "1"
        state: present
        reload: yes

    - name: Detect public interface
      shell: ip -o -4 route show to default | awk '{print $5}'
      register: pub_iface
      changed_when: false

    - name: Generate server WireGuard keys
      shell: |
        umask 077
        wg genkey | tee /etc/wireguard/server_private.key | wg pubkey > /etc/wireguard/server_public.key
      args:
        creates: /etc/wireguard/server_private.key

    - name: Read server keys
      slurp:
        src: "/etc/wireguard/{{ item }}"
      register: wg_keys
      loop:
        - server_private.key
        - server_public.key

    - name: Render wg0.conf
      copy:
        dest: /etc/wireguard/wg0.conf
        mode: '0600'
        content: |
          [Interface]
          PrivateKey = {{ wg_keys.results[0].content | b64decode | trim }}
          Address = 10.66.66.1/24
          ListenPort = {{ wg_port }}
          PostUp = iptables -A FORWARD -i %i -j ACCEPT; iptables -A FORWARD -o %i -j ACCEPT; iptables -t nat -A POSTROUTING -o {{ pub_iface.stdout }} -j MASQUERADE
          PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -D FORWARD -o %i -j ACCEPT; iptables -t nat -D POSTROUTING -o {{ pub_iface.stdout }} -j MASQUERADE

    - name: Enable + start wg-quick@wg0
      systemd:
        name: wg-quick@wg0
        enabled: yes
        state: started

    - name: Enable + start fail2ban
      systemd:
        name: fail2ban
        enabled: yes
        state: started

  handlers:
    - name: restart ssh
      systemd:
        name: ssh
        state: restarted

Execution

ansible-playbook -i inventory.yml playbook.yml

Count a few minutes the first time (essentially apt upgrade). Tunnel is up. Your ericg user can SSH with the Ed25519 key. You can rerun the playbook as many times as you want without breaking anything - it won't overwrite the WireGuard keys (idempotence guaranteed via the creates: flag).

To add a client (handled in a second phase of the playbook, documented in the WireGuard config templates guide): generate client keys, render client.conf with Jinja2, push via QR encode.

Practical tip: version the playbook in a private Git repo (never public - the Ansible Vault keys aren't safe against public GitHub if the passphrase ever leaks). A self-hosted Gitea on the same VPS is one option.

How do you monitor that your VPN stays up?

If you want to know when your tunnel drops without refreshing manually, UptimeRobot covers most of the need for free. Free plan: 50 monitors, checks every 5 minutes, email + Telegram + Discord webhook alerts.

Monitor 3 distinct endpoints to disambiguate the failure type:

Monitor 1 - Server health (HTTPS ping of the IP)

UptimeRobot type "HTTP(s)", URL https://YOUR_PUBLIC_IP/healthz. To answer this check, install a lightweight Caddy on port 443:

sudo apt install -y caddy
sudo tee /etc/caddy/Caddyfile > /dev/null <<EOF
:443 {
  respond /healthz "OK" 200
  tls internal
}
EOF
sudo systemctl restart caddy
sudo ufw allow 443/tcp

If this monitor goes DOWN → the VPS itself is unreachable (Contabo network outage, or your VPS crashed).

Monitor 2 - Tunnel health (from Cloudflare Workers)

Set up a free Cloudflare Worker (100k req/day free tier) that fetches https://ifconfig.me with a custom user-agent. For the check to be meaningful, the Worker would need to traverse the WireGuard tunnel, which isn't directly possible with Workers - workaround with an UptimeRobot "Keyword" monitor hitting an endpoint you host that verifies the response contains the Contabo VPS IP (not a residential one).

Monitored URL: https://YOUR_PUBLIC_IP/whoami (Caddy proxies to ifconfig.me).

Keyword: the IPv4 of your VPS.

If routing breaks (DNS hijack, broken NAT), the returned IP would differ and the monitor would alert.

Monitor 3 - DNS health via 1.1.1.1

URL: https://1.1.1.1/cdn-cgi/trace, keyword "warp=off". This check verifies you can resolve Cloudflare from the VPS - i.e. that the VPS outbound route isn't broken.

Alert configuration

In UptimeRobot, set:

  • Primary email: you get pinged within 30s of detection
  • Telegram bot (free): push to your phone even off email
  • Threshold: "alert after 2 failed checks" to avoid network false positives

In practice this setup mostly alerts you on real events - a planned Contabo maintenance window, or a service crash (for example Caddy failing on a cert renewal). With the "2 failed checks" threshold, network false positives stay rare.

Total cost: €0. UptimeRobot free + Cloudflare Workers free + Caddy free.

How do you secure SSH on the VPN server?

Initial bootstrap disables SSH password, but in production you should go further. Here's the hardening to apply to every Contabo VPS, motivated by the constant automated SSH scanning that any internet-facing host receives (bots permanently scan hosting IP ranges, Contabo's included).

Step 1 - Custom SSH port

Changing the SSH port isn't "real" security (security through obscurity) but it cuts most of the log noise. Bots scan port 22 first.

sudo sed -i 's/^#Port 22/Port 2289/' /etc/ssh/sshd_config
sudo ufw delete allow 22/tcp
sudo ufw allow 2289/tcp
sudo systemctl restart ssh
# Verify from a separate terminal BEFORE closing the first:
# ssh -p 2289 ericg@YOUR_IP

⚠ Keep the old terminal open until you've confirmed the new-port connection works. Otherwise you lock yourself out.

Step 2 - Custom fail2ban SSH jail

fail2ban watches port 22 by default. Adjust:

sudo tee /etc/fail2ban/jail.d/sshd-custom.local > /dev/null <<EOF
[sshd]
enabled = true
port = 2289
maxretry = 3
findtime = 600
bantime = 86400
EOF
sudo systemctl restart fail2ban
sudo fail2ban-client status sshd

Policy: 3 failures in 10 minutes → 24h ban. Stricter than the default (5 failures / 1h ban) because we don't allow passwords anyway - an auth failure = a bot.

Step 3 - Audit fail2ban quota

An SSH jail on a public VPS bans addresses every day. To check what's happening:

sudo fail2ban-client status sshd
# Currently banned IPs: 47
# Banned IP list: 185.x.x.x 91.x.x.x ...
sudo zcat /var/log/fail2ban.log* | grep "Ban " | wc -l
# Total bans since the beginning

If the ban volume is high, you can stiffen bantime = 604800 (1 week) to limit IO load on the server.

Step 4 - Ed25519 SSH keys with passphrase

If you haven't generated your Ed25519 key on the laptop, now's the time:

# On your laptop
ssh-keygen -t ed25519 -C "ericg@laptop-2026" -f ~/.ssh/id_ed25519_vpn
# Pick a strong passphrase (typed once/day via ssh-agent)
ssh-add -t 10800 ~/.ssh/id_ed25519_vpn  # forgets it after 3h

Ed25519 > RSA 4096: faster signatures, shorter keys, state of the art in 2026. Every Ubuntu 24.04 Contabo VPS supports Ed25519 natively.

Step 5 - Disable ChallengeResponseAuthentication

Make sure these lines are in /etc/ssh/sshd_config:

PubkeyAuthentication yes
PasswordAuthentication no
ChallengeResponseAuthentication no
KbdInteractiveAuthentication no
UsePAM yes
AuthenticationMethods publickey

With AuthenticationMethods publickey, even if a 0-day CVE lets an attacker bypass PAM, they still need the key. Belt and suspenders.

After these 5 steps, the bulk of automated SSH brute-force attempts are blocked at the firewall and the rest can never authenticate (key-only login). None succeed. You can sleep.

Is a Contabo VPS cheaper than a commercial VPN?

Honest 5-year calculation (Contabo 5,50 €/mo, contabo.com, 18 October 2026; NordVPN Basic, nordvpn.com, 19 October 2026, excl. VAT). The NordVPN 2-year plan runs 27 months, so three yearly renewals cover the rest of the 5 years:

SolutionYr 1Yr 2Yr 3Yr 4Yr 5Total
NordVPN 2yr + renewals€94.23€0€139.08€139.08€139.08€511.47
Contabo Cloud VPS 4 (5,50 €/mo)€66€66€66€66€66€330

Savings: ~€181 over 5 years (35%). Bonus: you can host your Bitwarden, Nextcloud, Umami, whatever you want.

What are the downsides of self-hosting a VPN?

For completeness:

  • Netflix US streaming, BBC iPlayer, etc.: almost never works. Netflix detects datacenter ASNs (Contabo ASN 51167) and serves you the local catalog. For streaming, keep a NordVPN 1yr as a complement.
  • DPI bypass Iran/China: WireGuard on port 51820/udp in plaintext is detected by sophisticated DPI. For these cases, switch to V2Ray VMess/VLESS with REALITY on this same Contabo VPS - the same hardware, different protocol stack, designed to resist GFW detection.
  • No chat support: Contabo support goes through tickets opened from the my.contabo.com customer panel, so expect a delay. If you want live chat, check Hetzner Cloud (~2× the price, FR/DE/EN chat support).
  • You're the admin: if the VPS crashes, you debug. Opposite of a managed service.

A VPN changes your IP. It does not change your browser.

A tunnel replaces the address a service sees. It changes nothing about what your browser announces on its own - fonts, screen, time zone, graphics stack - and that combination is often stable enough to recognise you across sessions, tunnel or no tunnel.

Measure your own browser fingerprint - passive, no questions, no account, no email.

Article published 2026-06-02, last updated 2026-06-03 (added: idempotent Ansible playbook, free 3-endpoint UptimeRobot monitoring, fail2ban + Ed25519 SSH hardening). Bootstrap script written for Ubuntu 24.04 LTS. If the procedure breaks for you, open an issue on our GitHub or email contact@vpnsmith.com.

Commercial links carry the rel="sponsored nofollow" attribute; an affiliate commission may apply at no extra cost to you. Prices quoted are those observed in October 2026 and change without notice: check them on the provider's site before ordering.

Contabo is one option among several. Our cheapest-VPS comparison for WireGuard sets its pricing against the other providers on the same specs.

Other VPS head-to-heads: Contabo vs Hostinger (entry price against renewal price) and Contabo alternatives (which VPS to pick depending on why you are leaving Contabo).

Affiliate link

Checked 17 Nov 2026: €4.40 for the first 24 months, list price €5.50

Frequently asked questions

Does Contabo offer a VPN?
No - and this is the thing worth knowing before you buy anything. Contabo is a hosting company: it sells VPS and dedicated servers, not a consumer VPN subscription. When people search for a Contabo VPN they almost always mean the setup on this page: renting a Contabo VPS and installing WireGuard on it yourself, so the server is yours and the IP is yours alone. That is a different product from a commercial VPN - you get a dedicated IP and no shared-IP blocklists, but you also administer it, patch it, and you are the only user, which means it does not blend you into a crowd the way a commercial VPN does.
What's the total cost?
Contabo Cloud VPS 4 24 months = ~€132 incl. tax (5.50 €/mo, checked on contabo.com 17 Oct 2026). Traffic is unlimited (fair-use), no extra cost. Over 5 years: ~€330 vs ~€511 for NordVPN Basic (2-year plan, then yearly renewals; nordvpn.com, 19 October 2026, excl. VAT).
Is it legal in the EU?
Yes, self-hosting a VPN is legal in France and across the EU. You remain responsible for tunnel usage - a VPN does not decriminalize an unlawful activity.
How many devices can connect at once?
As many as you want. WireGuard doesn't charge per device. The practical limit is the link's bandwidth shared between active clients, so measure it under your own usage.
What if the VPS goes down?
Contabo advertises a 99.9% SLA and announces scheduled maintenance windows in advance. No provider guarantees 100% uptime, so for critical HA, plan a second VPS at another provider.
Can I automate everything with Ansible?
Yes, and it's actually recommended as soon as you plan to provision 2+ VPSes or want to rebuild in case of incident. An idempotent Ansible playbook is given below: it handles SSH hardening, WireGuard install, UFW, fail2ban, and generates the first client. Count a few minutes to go from bare VPS to tunnel up from your laptop.
How do I monitor the tunnel without paying for a service?
UptimeRobot gives 50 free checks at 5-minute intervals, plenty for a personal VPN. You monitor 3 things: HTTPS ping of the VPS IP (server health), DNS resolution via 1.1.1.1 through the tunnel (routing health), and a Cloudflare Workers `/healthz` endpoint that answers from the VPS IP (end-to-end tunnel health).
Is self-hosting a VPN safe?
Yes, if the VPS is properly hardened. The key steps are: disable root SSH login, use Ed25519 keys only, install fail2ban (3 failures in 10 min = 24h ban), open only ports 22/tcp and 51820/udp via UFW, and enable unattended-upgrades. Any internet-facing VPS receives constant automated SSH scanning, but with this config those attempts never authenticate.