Fixie gives you a static IP address for your OpenClaw agent so outbound HTTP and HTTPS requests can reach services that require IP whitelisting.

Use this setup when OpenClaw needs to call a private API, webhook endpoint, SaaS admin API, internal tool, or any third-party service that only accepts traffic from approved IP addresses. OpenClaw runs through Fixie, and the remote service sees your Fixie static IP addresses instead of the changing IP address of your local machine, container, or gateway host.

This page is for HTTP and HTTPS requests from OpenClaw. For databases, SSH, SFTP, FTP, and other raw TCP connections, use Fixie Socks with a SOCKS-aware client or fixie-wrench.

1. Create a Fixie HTTP/S proxy

Create a Fixie HTTP/S proxy in the Fixie Dashboard, then copy its proxy URL. It will look like:

http://fixie:YOUR_TOKEN@YOUR_SUBDOMAIN.usefixie.com:80

Each Fixie proxy group has two static IP addresses. Add both IP addresses from the Fixie dashboard to the allowlist for the service your OpenClaw agent needs to call.

2. Configure OpenClaw to use Fixie

OpenClaw's managed network proxy can route normal runtime HTTP and WebSocket egress through a forward proxy. Set your Fixie proxy URL as the OpenClaw managed proxy:

export FIXIE_URL="http://fixie:YOUR_TOKEN@YOUR_SUBDOMAIN.usefixie.com:80"

openclaw config set proxy.enabled true
openclaw config set proxy.proxyUrl "$FIXIE_URL"
openclaw proxy validate --proxy-url "$FIXIE_URL"
openclaw gateway run

For an installed OpenClaw gateway service, store the URL durably and restart the service:

# ~/.openclaw/.env or $OPENCLAW_STATE_DIR/.env
OPENCLAW_PROXY_URL=http://fixie:YOUR_TOKEN@YOUR_SUBDOMAIN.usefixie.com:80

openclaw config set proxy.enabled true
openclaw gateway install --force
openclaw gateway start

3. Pass proxy variables to child processes

OpenClaw's managed proxy covers supported HTTP and WebSocket clients in the OpenClaw runtime. If your OpenClaw agent launches tools, scripts, or child processes that make their own outbound HTTP requests, also provide standard proxy variables:

export HTTP_PROXY="$FIXIE_URL"
export HTTPS_PROXY="$FIXIE_URL"
export http_proxy="$FIXIE_URL"
export https_proxy="$FIXIE_URL"
export NO_PROXY="localhost,127.0.0.1,::1"
export no_proxy="$NO_PROXY"

If you run OpenClaw in Docker, Kubernetes, or another container runtime, set these variables inside the container as well as on the host.

4. Verify the static IP address

Run a request from the same OpenClaw environment that will call the whitelisted service:

curl --proxy "$FIXIE_URL" http://welcome.usefixie.com
curl https://api.ipify.org

The first command verifies explicit Fixie proxy use. The second command verifies that the current shell environment is honoring the proxy variables.

Troubleshooting OpenClaw static IP requests

If the remote service still sees the wrong IP address:

• Confirm both Fixie static IP addresses are on the remote service's allowlist.
• Confirm the OpenClaw gateway was restarted after the proxy configuration changed.
• Check whether the request comes from OpenClaw itself or from a child process that needs HTTP_PROXY and HTTPS_PROXY.
• Check NO_PROXY and no_proxy; any matching host bypasses Fixie.
• For raw TCP use cases, switch to Fixie Socks or fixie-wrench.