After install

A fresh install of Proxima Gateway boots in idle mode — the binary is running, the heartbeat loop is reporting in, but no ports are listening because the config has an empty ports: [] array. Your job from here: add at least one port.

The dashboard layout

After install, /app shows your server card with the version badge, host, and three buttons:

• Manage → server config (general, ports, replacements, etc.)
• Firewall → rate limits, whitelist, banned IPs, auto-ban settings
• Logs → live tail of /var/log/proxima-gateway/gateway.log

The sidebar exposes the same sections plus an IP Test tool for checking how the proxy will see a given IP (country, ASN, whitelist status).

Adding your first port

Sidebar → Configuration → Ports → Add Port. You'll need:

• Port — the TCP port the proxy will listen on (e.g. 443)
• Backend URL — where to forward to (e.g. http://127.0.0.1:8080)
• Optional per-port overrides for URL replacements, blocked countries, and allowed domains

Save and the dashboard pushes the new config to your server. The proxy picks it up on the next config reload — no restart required.

→ See Port configuration for the full schema.

Quick checklist

After adding ports you might want:

• Geo URL replacements — route traffic by country
• Country blocking — refuse traffic from a deny-list of countries
• Rate limiting — cap requests per IP
• Auto-ban — automatically ban IPs that hammer login pages

Verifying everything works

From your dev machine:

curl -i http://<your-server-ip>:<port>/

You should see your backend's response, with proxy headers added.

If you see "Connection refused", the port isn't listening — check that you saved the port config and that your VPS firewall allows inbound on that port.

If you see a Cloudflare-style "country blocked" page, you've turned on country blocking for a region you're testing from.