Offshore 1
$3.09/ month
3 mo $8.346 mo $14.8312 mo $25.95
- 1 vCPU
- 1 GB RAM
- 20 GB NVMe
- 2 TB traffic
Guide · Debian and Ubuntu
A WireGuard VPS gives you a VPN you control, on a server paid for only in crypto, with no ID. Here is how to install it in about ten minutes, add your phone with a QR code, test for leaks, and what it does not hide.
The setup in brief
To run WireGuard on a VPS you need a Linux KVM server, root access, one UDP port and about ten minutes. Offshore 1 (1 vCPU, 1 GB RAM, 2 TB of outgoing traffic a month, $3.09) is enough for one person. Install wireguard, generate a key pair, write /etc/wireguard/wg0.conf, turn on IP forwarding, add a NAT rule, and bring up wg0 with wg-quick. Your traffic then leaves from the VPS address. It is a private tunnel to a server you control, not Tor: the data center can still see what leaves the VPS.
A commercial VPN asks you to trust a company with your traffic. A WireGuard VPS server moves that trust to a machine you rent and configure. You choose the country, you are the only user, and nobody else shares your exit address. Paying for a VPS in crypto with no KYC means no ID document and no phone number on the account; the anonymous VPS page lists exactly what Nymhost keeps.
The path is simple: your device → encrypted WireGuard packets over UDP → your VPS → ordinary traffic → the website. Each point on that path sees something different.
| Point on the path | What it can see | What it cannot see |
|---|---|---|
| Your Wi-Fi, ISP or mobile carrier | That you send UDP packets to one IP address and port, how many and when | The sites you visit, your DNS lookups (when they go through the tunnel), the content |
| The VPS, where you are root | Every destination and DNS lookup, and any content that is not encrypted end to end | The content of HTTPS and other encrypted connections |
| The data center network | Encrypted packets arriving from your home address, and the traffic leaving the VPS for each destination; timing can link the two | What is inside the tunnel, and the content of HTTPS connections |
| The DNS resolver in your client config | Every name you look up, arriving from the VPS address | Your home address, as long as the queries go through the tunnel |
| The website or service | The VPS IP address, the same one on every visit | Your home IP address |
Nymhost keeps no connection logs, no traffic logs and no visitor IP addresses, but your traffic still crosses the data center network.
Typical good uses: a private exit on untrusted Wi-Fi, a fixed IP address to reach your own servers, access to your home network, and a different city for geo-restricted services you are allowed to use.
WireGuard runs inside the Linux kernel and uses little CPU or memory. Offshore 1 is enough for one person and a few devices. Choose a bigger plan only for the traffic quota or if the same VPS does other jobs; the personal VPS page lists what else fits on the same server and the plan each job needs.
The quota is the real limit. Traffic quotas on Nymhost count outgoing data per month, and going over never triggers an automatic charge. With a VPN, what you download leaves the VPS towards you, and what you upload leaves it towards the internet, so downloads and uploads both count. The quotas are listed below.
| Plan | RAM | Traffic per month | From (1 month) |
|---|---|---|---|
| Offshore 1 | 1 GB | 2 TB | $3.09 |
| Offshore 2 | 2 GB | 4 TB | $4.89 |
| Offshore 4 | 4 GB | 8 TB | $8.19 |
| Global 6 | 6 GB | 6 TB | $9.59 |
| Offshore 8 or Global 8 | 8 GB | 12 TB | $13.49 / $19.19 |
Every plan has a 1 Gbit/s port shared by the VPS on the same host, one dedicated IPv4 address and a routed IPv6 /64.
Pick the exit country you need, or the city with the lowest delay from where you are. Nymhost publishes no latency figures of its own; the table uses public city-to-city averages, which tell you how far apart two cities are on the internet, not how fast our servers are. Offshore plans run in Amsterdam, Reykjavik, Zurich and Bucharest; Global plans in London, Frankfurt, New York, Dallas and Los Angeles.
From most of Western Europe, an Amsterdam VPS, London or Frankfurt comes first. From Berlin and Madrid, a Switzerland VPS in Zurich is just as close. For Moldova, Serbia or Hungary, the Romania VPS in Bucharest is lowest. How the four offshore countries differ in law is on the offshore hosting page.
| From | Amsterdam | Reykjavik | Zurich | Bucharest | London | Frankfurt | New York | Dallas | Los Angeles |
|---|---|---|---|---|---|---|---|---|---|
| London | 8 | 35 | 21 | 44 | same city | 19 | 71 | 100 | 124 |
| Paris | 14 | 68 | 31 | 34 | 8 | 15 | 73 | 105 | 132 |
| Berlin | 16 | 49 | 14 | 36 | 22 | 14 | 90 | 122 | 151 |
| Madrid | 28 | 59 | 27 | 59 | 27 | 31 | 83 | 123 | 146 |
| Istanbul | 58 | 71 | 37 | 52 | 49 | 27 | 116 | 148 | 167 |
| New York | 76 | 104 | 91 | 113 | 71 | 86 | same city | 37 | 69 |
| Toronto | 96 | 109 | 101 | 139 | 81 | 93 | 14 | 33 | 51 |
| Singapore | 177 | 186 | 155 | 178 | 181 | 158 | 222 | 201 | 170 |
This WireGuard VPS setup works on Debian 12, Debian 13 or Ubuntu 24.04 LTS: create the VPS, log in as root over SSH, and follow these steps. The commands follow the WireGuard quickstart and the wg(8) and wg-quick(8) manual pages. In the examples the network card is eth0 and the tunnel uses 10.8.0.0/24 and fd42:42:42::/64; check yours with ip -o route get 1.1.1.1.
Install wireguard. The WireGuard install page lists Debian and Ubuntu as shipping the module and the tools with this one package.
Make a private and a public key for the server and for each device. Keep every private key secret.
Create /etc/wireguard/wg0.conf with the server address, the port and one [Peer] block per device.
Let the kernel route packets between the tunnel and the network card.
Masquerade the tunnel traffic so it leaves with the VPS address, and allow UDP 51820.
Bring up the interface with wg-quick, enable it at boot and read the status with wg show.
apt update && apt install -y wireguard nftables
umask 077
cd /etc/wireguard
wg genkey | tee server.key | wg pubkey > server.pub
wg genkey | tee phone.key | wg pubkey > phone.pub
wg genpsk > phone.psk[Interface]
Address = 10.8.0.1/24, fd42:42:42::1/64
ListenPort = 51820
PrivateKey = <contents of server.key>
PostUp = nft add table inet wgnat; nft "add chain inet wgnat post { type nat hook postrouting priority srcnat; }"; nft add rule inet wgnat post oifname "eth0" masquerade
PostDown = nft delete table inet wgnat
[Peer]
# phone
PublicKey = <contents of phone.pub>
PresharedKey = <contents of phone.psk>
AllowedIPs = 10.8.0.2/32, fd42:42:42::2/128printf "net.ipv4.ip_forward=1\nnet.ipv6.conf.all.forwarding=1\n" > /etc/sysctl.d/99-wireguard.conf
sysctl --system
# only if you run ufw:
ufw allow 51820/udp
ufw route allow in on wg0 out on eth0
systemctl enable --now wg-quick@wg0
wg showOn the phone or laptop, create a tunnel with its own key pair (the app can generate one, or use phone.key from above) and use a configuration like the next block. Replace 203.0.113.10 with your VPS IPv4 address. AllowedIPs = 0.0.0.0/0, ::/0 sends all traffic through the VPS; a narrower list sends only those networks. The PersistentKeepalive of 25 seconds keeps the tunnel open through a home router or mobile network; the WireGuard quickstart gives that value as one that works with a wide variety of firewalls.
[Interface]
PrivateKey = <contents of phone.key>
Address = 10.8.0.2/32, fd42:42:42::2/128
DNS = 1.1.1.1, 2606:4700:4700::1111
[Peer]
PublicKey = <contents of server.pub>
PresharedKey = <contents of phone.psk>
Endpoint = 203.0.113.10:51820
AllowedIPs = 0.0.0.0/0, ::/0
PersistentKeepalive = 25The DNS = line decides who answers your lookups, and that server learns every name you visit. With AllowedIPs = 0.0.0.0/0, ::/0 the queries travel inside the tunnel, so your local network no longer sees them; the resolver sees them arriving from the VPS address. Three reasonable choices:
On Windows, while its kill switch is on (one peer with a /0 in AllowedIPs), the WireGuard client lets DNS queries reach only the servers named in the config, so lookups cannot slip out to other DNS servers. Option 2 takes a few lines:
apt install -y unbound
cat > /etc/unbound/unbound.conf.d/wg.conf <<'EOF'
server:
interface: 127.0.0.1
interface: 10.8.0.1
interface: fd42:42:42::1
ip-freebind: yes
access-control: 10.8.0.0/24 allow
access-control: fd42:42:42::/64 allow
EOF
systemctl restart unbound
# only if you run ufw:
ufw allow in on wg0 to any port 53
# then, in each client config:
# DNS = 10.8.0.1, fd42:42:42::1Give each device its own key pair and its own tunnel address. Do not copy one client config to two devices: the server learns each peer's endpoint from where its authenticated packets come from, so two devices with the same key keep taking the tunnel from each other.
To add a laptop as 10.8.0.3, generate its keys on the server, append a [Peer] block to wg0.conf, and reload the interface without dropping the phone's session. The wg-quick(8) page gives wg syncconf with wg-quick strip for exactly that.
For the phone, write its client config to a file and print it as a QR code in the terminal with qrencode. The official WireGuard apps for Android and iOS have a Scan from QR code (Android) or Create from QR code (iOS) option, and their own tip suggests the same qrencode -t ansiutf8 command.
The QR code contains the client's private key. Scan it, then delete the file and the key from the server. Never send the code as a screenshot or keep it in a chat.
cd /etc/wireguard && umask 077
wg genkey | tee laptop.key | wg pubkey > laptop.pub
wg genpsk > laptop.psk
cat >> wg0.conf <<EOF
[Peer]
# laptop
PublicKey = $(cat laptop.pub)
PresharedKey = $(cat laptop.psk)
AllowedIPs = 10.8.0.3/32, fd42:42:42::3/128
EOF
wg syncconf wg0 <(wg-quick strip wg0)
wg show wg0 peersapt install -y qrencode
cd /etc/wireguard && umask 077
cat > phone.conf <<EOF
[Interface]
PrivateKey = $(cat phone.key)
Address = 10.8.0.2/32, fd42:42:42::2/128
# use a public resolver here if you skipped Unbound
DNS = 10.8.0.1, fd42:42:42::1
[Peer]
PublicKey = $(cat server.pub)
PresharedKey = $(cat phone.psk)
Endpoint = 203.0.113.10:51820
AllowedIPs = 0.0.0.0/0, ::/0
PersistentKeepalive = 25
EOF
qrencode -t ansiutf8 < phone.conf
# after scanning, remove the phone's private key from the server
rm phone.conf phone.keyEvery Nymhost VPS has a routed IPv6 /64. The setup above gives tunnel clients private fd42:42:42::/64 addresses and masquerades them behind the VPS IPv6 address, which works with no change to the provider network. Without IPv6 in the tunnel, a dual-stack client can leak IPv6 traffic outside it. Keep ::/0 in AllowedIPs so everything is routed through the VPS, or disable IPv6 on the client.
You can also give clients public addresses from your /64, but that needs extra routing or neighbor-proxy settings on the VPS and depends on how the /64 is routed to it. Ask support if you want that; masquerading is simpler and enough for one person.
On the server, wg show should list each peer with a recent latest handshake and growing transfer counters; the wg(8) page lists both among the peer fields. Then test from the client:
::/0 is in AllowedIPs.tcpdump -ni wg0 port 53 while the client opens a few sites. Queries from 10.8.0.2 show that DNS goes through the tunnel. If nothing appears, the client is asking another resolver directly.AllowedIPs. On Android 7.0 and later, turn on always-on VPN and Block connections without VPN in the VPN settings. On a Linux laptop, traffic goes out normally after wg-quick down; add a firewall rule if you need it blocked.A clean test shows that the tunnel carries your traffic at that moment. It does not show what the website, the resolver or the data center can learn: the table at the top of this page does.
Finally, confirm that the tunnel survives a reboot: reboot, wait, and run wg show again. The systemctl enable --now wg-quick@wg0 line made it start at boot.
wg show lists the peer but never a handshake. Check, in this order:
Endpoint IP and port are right, and UDP 51820 is allowed by every firewall on the way, including ufw and any firewall at the client side. Some public networks block UDP or most UDP ports: move ListenPort to another port, for example 443, then update the client Endpoint and the ufw rule.PresharedKey is identical on both sides, or removed on both.tcpdump -ni eth0 udp port 51820 on the server shows whether packets arrive at all.The tunnel is up, yet pages do not load. Check that sysctl net.ipv4.ip_forward prints 1, that the NAT rule exists (nft list ruleset), that oifname "eth0" matches your real interface name, and that the client AllowedIPs covers the destination. If you point clients at Unbound, check ss -lun | grep :53 shows it on 10.8.0.1.
Symptoms: small requests work, but large pages hang, or some sites stall. By default wg-quick picks the MTU from the endpoint addresses or the default route, which the manual page says is usually a sane choice. If it is wrong on your path, add MTU = 1380 to the client [Interface] section and lower it step by step; do not go below 1280 if you use IPv6, which has a 1280 minimum.
A VPN subscription paid by card puts your name next to the service; here crypto is the only way to pay, with no card, PayPal or bank transfer. With Monero, a block explorer shows neither the sender nor the amount, and the top-up is credited after 10 confirmations, about 20 minutes on the checkout; Bitcoin needs 2 confirmations, also about 20 minutes, but the payment stays readable on its public chain. The minimum top-up is $25 and the balance never expires, so it pays Offshore 1 for 6 months ($14.83) and leaves $10.17 toward the renewal. Billing still links your account number to the VPS address and the transaction ID of the payment, as the page on paying for a VPS with Monero explains.
Offshore 1 is enough for one person. Pick a longer rental to save up to 30%, and pay in any of 7 coins (8 coin and network options) from a prepaid balance (how to buy a VPS with crypto). The pricing page shows every plan and city.
Amsterdam · Reykjavik · Zurich · Bucharest
$3.09/ month
3 mo $8.346 mo $14.8312 mo $25.95
$4.89/ month
3 mo $13.206 mo $23.4712 mo $41.07
$8.19/ month
3 mo $22.116 mo $39.3112 mo $68.79
$13.49/ month
3 mo $36.426 mo $64.7512 mo $113.31
$20.49/ month
3 mo $55.326 mo $98.3512 mo $172.11
New York · Dallas · Los Angeles · London · Amsterdam · Frankfurt
$3.19/ month
3 mo $8.616 mo $15.3112 mo $26.79
$6.39/ month
3 mo $17.256 mo $30.6712 mo $53.67
$9.59/ month
3 mo $25.896 mo $46.0312 mo $80.55
$19.19/ month
3 mo $51.816 mo $92.1112 mo $161.19
$29.39/ month
3 mo $79.356 mo $141.0712 mo $246.87
Prices in US dollars, checked on 18 November 2026. Paid from a crypto balance (minimum top-up $25); 3, 6 and 12 months save 10, 20 and 30%. Every plan: KVM, root over SSH, 1 dedicated IPv4 + /64 IPv6, shared 1 Gbit/s port.
Any KVM VPS works, because WireGuard runs in the Linux kernel. Offshore 1 (1 vCPU, 1 GB, 2 TB outgoing traffic a month, $3.09) is enough for one person. Choose the plan by the traffic quota and the city, not by CPU.
Only partly. The account needs no ID and no email, and Nymhost keeps no connection or traffic logs. But every site sees the same VPS address, the data center sees traffic arriving from your home and leaving the server, and a non-Monero payment sits on a public blockchain. For several hops, use Tor instead of a one-hop tunnel.
Yes. The VPS is a full KVM server with its own kernel and root access, so you can install wireguard and load the tunnel. Debian 12, Debian 13 and Ubuntu 24.04 LTS all work with the steps above.
All the traffic you send through the tunnel counts as outgoing on the VPS, one way or the other. Offshore 1 includes 2 TB a month; Offshore 8 includes 12 TB. Going over the quota never triggers an automatic charge.
Yes. Every VPS has a routed IPv6 /64. The simple method is to give the tunnel private IPv6 addresses and masquerade them, as in the steps above. Keep ::/0 in the client AllowedIPs so IPv6 does not bypass the tunnel.
Generate a new key pair for it, give it the next tunnel address (10.8.0.3, then 10.8.0.4), add a [Peer] block to wg0.conf and reload with wg syncconf wg0 <(wg-quick strip wg0). For a phone, print its config with qrencode -t ansiutf8 and scan it in the app, as shown above.
WireGuard listens on whatever UDP port you set in ListenPort; 51820 is only the usual example. On a network that blocks it, try another port such as 443, change the client Endpoint to match and open the new port in ufw. WireGuard has no TCP mode, so a network that blocks all UDP blocks it too.
Yes. Tor relays, exits included, are allowed on every Nymhost VPS, and WireGuard uses little CPU. Both share the monthly outgoing traffic quota, so a busy relay can use up the traffic your tunnel needs; pick a plan with more traffic, such as Offshore 4 with 8 TB.
Yes. WireGuard was added in Linux 5.6, released on 29 March 2020. The WireGuard install page lists apt install wireguard for Debian and Ubuntu, with the module included, and points users of kernels older than 5.6 to separate packages.
Whichever you trust with every name you look up. A public resolver is the quickest; Unbound on the VPS keeps lookups away from resolver companies but sends them unencrypted from the server. Point DNS = at an address reached through the tunnel and check with tcpdump -ni wg0 port 53.