New to WireGress? Start with our Product Overview to understand how WireGress works.

WireGress Setup Guide

Step-by-step instructions to connect your devices, servers, and services to WireGress

Each customer gets a dedicated gateway and IP setup — no sharing, full isolation.

📱 Personal Device 🖥️ Server/Service ⚙️ CI/CD ☸️ Kubernetes 📥 Inbound Access

Prerequisites

  • WireGress account created (request access if needed)
  • Gateway provisioned in your WireGress dashboard
  • Peer configuration downloaded from dashboard

Connect Your Personal Device

Route your device's traffic through a fixed, secure IP

Setup Steps

  1. 1

    Install the WireGuard app on your device

    Download from wireguard.com/install

  2. 2

    Download your peer configuration from WireGress

    Available in your WireGress dashboard after approval

  3. 3

    Import the configuration into the app

    Import Tunnel(s) from file

  4. 4

    Activate the tunnel

    Toggle the connection on in the WireGuard app

Supported Platforms

  • Windows
  • macOS
  • Android
  • iOS

What Happens After Connecting

  • • Your outbound traffic uses a fixed WireGress IP
  • • External services see WireGress instead of your local network
  • • You can access systems that require IP allow-listing

Important Notes

  • • Each configuration works for one device only
  • • Keep your configuration file secure and private
  • • Once imported, you can connect or disconnect anytime using the WireGuard app
  • • If you regenerate your configuration, re-import it into the app

Connect Servers & Services

Route server and application traffic through WireGress

Linux Server Setup

  1. 1

    Install WireGuard

    # Ubuntu/Debian

    sudo apt update && sudo apt install wireguard

    # CentOS/RHEL

    sudo yum install wireguard-tools

  2. 2

    Download peer configuration from WireGress dashboard

    Save as /etc/wireguard/wg0.conf

  3. 3

    Start the tunnel

    sudo wg-quick up wg0

    # Enable on boot

    sudo systemctl enable wg-quick@wg0

  4. 4

    Verify connection

    sudo wg show

    curl ifconfig.me # Should show WireGress IP

Docker Container Setup

Run WireGuard in a sidecar container or use host networking mode.

# docker-compose.yml example

services:

wireguard:

image: linuxserver/wireguard

cap_add:

- NET_ADMIN

volumes:

- ./wg0.conf:/config/wg0.conf

network_mode: host

Enable Inbound Access (Core Plus)

Forward approved inbound traffic through your dedicated public IP to a connected peer

Setup Steps

  1. 1

    Confirm your plan includes inbound

    Inbound forwarding requires Core Plus or a Custom deployment — Core plans are outbound only

  2. 2

    Connect the target peer

    The device, router, or host you want to reach must run WireGuard with an active tunnel — same steps as the server setup above

  3. 3

    Add an inbound forwarding rule

    In the WireGress dashboard, map a public port on your dedicated IP to the peer's IP and port, choosing TCP or UDP

  4. 4

    Restrict sources

    Limit the rule to approved source addresses where supported

  5. 5

    Test access

    Connect from an authorized external host to your WireGress IP on the mapped port

How It Works

  • • Connections to your WireGress IP on the mapped port are forwarded through the tunnel to the peer
  • • Works behind CGNAT because the tunnel is initiated outbound
  • • Peers without a forwarding rule remain outbound-only

Keep in Mind

  • • Only configured mappings forward — a public IP alone does not expose your peers
  • • Keep the peer's own firewall and application authentication in place
  • • Sessions can be interrupted if the underlying uplink changes

Important Notes

  • • Inbound access applies only to the mappings you configure
  • • A known public IP is part of an access policy — continue using authentication, encryption, and least-privilege access
  • • For custom inbound requirements beyond standard port forwarding, contact us

Advanced Setups

Integration guides for CI/CD, Kubernetes, and other infrastructure

CI/CD Pipelines

Prevent failures caused by changing IPs in automation workflows

  1. a. Create a peer in WireGress UI
  2. b. Download the configuration
  3. c. Install WireGuard on runner environment
  4. d. Import the configuration
  5. e. Activate tunnel before pipeline execution
  6. f. Run deployment/API steps through tunnel

API Integrations

Maintain a consistent outbound identity for external APIs

  1. a. Create a peer in WireGress UI
  2. b. Download the configuration
  3. c. Install WireGuard on application server
  4. d. Import the configuration
  5. e. Activate the tunnel
  6. f. Use WireGress IP in API allow-lists

Vendor Allow-listing

Ensure external vendors always recognize your system's IP

  1. a. Create a peer in WireGress UI
  2. b. Download the configuration
  3. c. Install WireGuard on your server
  4. d. Import the configuration
  5. e. Activate the tunnel
  6. f. Add the WireGress IP to vendor allow-list

SaaS Infrastructure

Control outbound communication from backend systems

  1. a. Create a peer in WireGress UI
  2. b. Download the configuration
  3. c. Install WireGuard on backend services
  4. d. Import the configuration
  5. e. Activate the tunnel
  6. f. Route outbound service traffic through WireGress

Cloud Simplification

Avoid complex NAT gateway configurations

  1. a. Create a peer in WireGress UI
  2. b. Download the configuration
  3. c. Install WireGuard on cloud instances
  4. d. Import the configuration
  5. e. Activate the tunnel
  6. f. Route outbound traffic via WireGress instead of NAT

Kubernetes Egress

Provide a fixed outbound IP for Kubernetes workloads

  1. a. Create a peer in WireGress UI
  2. b. Download the configuration
  3. c. Install WireGuard on cluster nodes
  4. d. Apply the configuration
  5. e. Activate the tunnel
  6. f. Route pod traffic through WireGress

Troubleshooting

Common issues and solutions

Connection not establishing

  • • Verify WireGuard is installed correctly
  • • Check that the configuration file is valid
  • • Ensure firewall allows UDP traffic on WireGuard port
  • • Confirm peer is active in WireGress dashboard

Traffic not routing through WireGress

  • • Verify tunnel is active: sudo wg show
  • • Check routing table configuration
  • • Test with: curl ifconfig.me (should show WireGress IP)
  • • Review AllowedIPs in configuration

Inbound forwarding not working

  • • Confirm your plan includes inbound (Core Plus or Custom)
  • • Verify the peer tunnel is active: sudo wg show
  • • Check the rule's port, protocol, and destination peer IP
  • • Ensure the peer's local firewall permits the service port
  • • Test from a source permitted by the rule's restrictions

Need additional help?

Contact our support team for assistance:

Contact Support

Ready to Connect?

Follow these steps to get your systems connected to WireGress.

← Back to Product Overview Request Access