Deployment: Linux / Debian / Ubuntu / Raspberry Pi

Prerequisites

• Docker 24+ and docker-compose
• Host must be on the same L2 segment as the target LAN devices (for WoL)
• Admin rights for NET_ADMIN + NET_BIND_SERVICE capabilities

Steps

1. Create a Gateway peer in the GateControl UI

   UI → Peers → "New peer" → enable the "Home Gateway" checkbox → API port 9876 (default) → Save.

2. Download gateway.env

   On the peer detail page: click "Download gateway config" — the file will land locally.

3. Compose setup

   mkdir -p /opt/gatecontrol-gateway/config
   cd /opt/gatecontrol-gateway
   cp /path/to/gateway-<id>.env config/gateway.env
   wget https://raw.githubusercontent.com/CallMeTechie/gatecontrol-gateway/main/docker-compose.example.yml -O docker-compose.yml
   

4. Start

   docker compose up -d
   docker compose logs -f
   

   Expected: logs show WireGuard up, config poll successful, HTTP proxy/API server binding on the tunnel IP.

5. Verification

   In the GateControl UI the gateway should appear as "online" (after ~2–5 min hysteresis cooldown).

Troubleshooting

• "Refused to bind on 0.0.0.0" → GC_TUNNEL_IP in gateway.env is missing or wrong
• WoL doesn't work → Gateway is not on the same L2 segment as the target, or host bridge is required instead of NAT
• Gateway shows as offline in the UI → Check docker logs; most common causes are DNS resolution or tunnel problems