Getting Started
Get Real IP gives you a dedicated static public IPv4 address routed through an encrypted WireGuard tunnel. This guide walks you from sign-up to a working tunnel.
What you’ll need
Section titled “What you’ll need”- A machine to run WireGuard on (Linux server, router, Raspberry Pi, etc.)
- About 10 minutes
WireGuard is supported on Linux, macOS, Windows, iOS, Android, and most homelab routers (pfSense, OPNsense, GL.iNet, MikroTik, UniFi). See the setup guides for device-specific instructions.
Step 1 — Sign up
Section titled “Step 1 — Sign up”Go to account.getrealip.net and create an account. You can sign up with Google or email.
Step 2 — Create a tunnel
Section titled “Step 2 — Create a tunnel”- From the dashboard, click Create Tunnel.
- Choose a region (US East or US West — pick the one closest to you).
- Confirm the subscription ($8/mo). Your static IP is assigned immediately.
Your new tunnel appears in the dashboard with your dedicated public IP address shown.
Step 3 — Download your WireGuard config
Section titled “Step 3 — Download your WireGuard config”Click Download Config on your tunnel to get a .conf file. You can also tap Show QR Code to scan directly into the WireGuard mobile app.
The config looks like this:
[Interface]PrivateKey = <your private key>Address = 134.49.198.16/32DNS = 1.1.1.1, 8.8.8.8
[Peer]PublicKey = <server public key>Endpoint = turnpike.getrealip.net:51834AllowedIPs = 0.0.0.0/0PersistentKeepalive = 25Step 4 — Install WireGuard
Section titled “Step 4 — Install WireGuard”Ubuntu / Debian:
sudo apt update && sudo apt install wireguardFedora / RHEL:
sudo dnf install wireguard-toolsmacOS: Download WireGuard for macOS from the App Store or via Homebrew:
brew install wireguard-toolsWindows / iOS / Android:
Download the official WireGuard app and import the .conf file or scan the QR code.
For router-specific installation (pfSense, GL.iNet, etc.) see the setup guides.
Step 5 — Import and connect
Section titled “Step 5 — Import and connect”Linux (wg-quick):
# Copy your config to /etc/wireguard/sudo cp ~/Downloads/getrealip.conf /etc/wireguard/getrealip.conf
# Bring the tunnel upsudo wg-quick up getrealip
# To start automatically on bootsudo systemctl enable --now wg-quick@getrealipmacOS / Windows / Mobile:
Open the WireGuard app, click Import Tunnel, and select the .conf file (or scan the QR code). Then click Activate.
Step 6 — Verify the tunnel is working
Section titled “Step 6 — Verify the tunnel is working”From a machine behind the tunnel, check your public IP:
curl https://api.ipify.orgYou should see your dedicated Get Real IP address — the same one shown in your dashboard.
You can also verify from the internet:
ping <your-static-ip>If ping responds, your tunnel is up and routing correctly.
Next steps
Section titled “Next steps”- Set a reverse DNS record — PTR Records guide
- Run a service — port-forward on your router, or bind directly on the machine running WireGuard
- Add a second IP — from the dashboard, click Add IP on your tunnel ($4/mo each)
- Router setup — Linux / Generic · pfSense · GL.iNet
Troubleshooting
Section titled “Troubleshooting”Tunnel connects but I see my ISP IP, not my Get Real IP address:
Check AllowedIPs in your config — it should be 0.0.0.0/0 to route all traffic through the tunnel. If you only want specific traffic routed, set AllowedIPs to specific subnets instead.
Can’t connect at all:
- Check that WireGuard is running:
sudo wg show - Verify the endpoint resolves:
nslookup turnpike.getrealip.net - Make sure UDP port 51834 isn’t blocked outbound by your ISP or firewall
Tunnel connects but services aren’t reachable from outside: The IP is routed to the machine running WireGuard. If your services run on other LAN devices, you’ll need to set up NAT or port forwarding on the WireGuard machine. See the Linux guide for details.