Running Docker containers that call external APIs? Containers are ephemeral — their outbound IPs change on every restart and rebuild. Route outbound traffic through a dedicated static EU IP instead.
services:
app:
image: my-app:latest
environment:
- HTTPS_PROXY=https://user:pass@eu-01.outboundgateway.com:8443
- HTTP_PROXY=https://user:pass@eu-01.outboundgateway.com:8443
# All containers now share one
# static EU outbound IP address
Docker containers are designed to be ephemeral — but that means their outbound IPs are unpredictable
Docker containers get new outbound IPs on every restart, rebuild, or scale event. The container that was whitelisted yesterday has a different IP today.
Payment providers, CRMs, and B2B partner APIs require IP whitelisting. Your Docker containers can't reach them without a stable, predictable outbound IP.
When a container restarts and gets a new IP, whitelisted integrations fail silently. API calls return 403 errors. Debugging is painful and intermittent.
Your app has API services, background workers, and sidecars. Each container has its own IP. You'd need to whitelist every single one — and update after every deploy.
"Whitelist this IP or your requests will be blocked."
But your Docker containers get new IPs on every docker-compose up. You need one stable IP to give them.
Docker Container
HTTPS Proxy
(Static EU IP)
External API
The external API sees one fixed EU IP address — no matter which container or how many times it restarts.
HTTPS_PROXY in Docker Compose or docker run --env at runtime
Running Docker containers that call external APIs requiring IP whitelisting
Managing Docker Compose stacks that need a consistent outbound IP for partner integrations
Running containerized microservices that connect to partner APIs and payment providers
Running regulated container workloads that need clear outbound IP audit trails and EU data residency
Set the proxy URL as an environment variable in your Docker configuration. All outbound requests from every container route through your static IP.
Add the proxy URL to your docker-compose.yml environment section. All services in the stack share the same static IP.
# docker-compose.yml
services:
app:
build: .
environment:
- HTTPS_PROXY=https://user:pass@eu-01.outboundgateway.com:8443
- HTTP_PROXY=https://user:pass@eu-01.outboundgateway.com:8443
worker:
build: .
environment:
- HTTPS_PROXY=https://user:pass@eu-01.outboundgateway.com:8443
- HTTP_PROXY=https://user:pass@eu-01.outboundgateway.com:8443
Store the proxy URL in a .env file and reference it at runtime. Secrets never get baked into the image.
# .env (add to .dockerignore, never commit to git)
HTTPS_PROXY=https://user:pass@eu-01.outboundgateway.com:8443
HTTP_PROXY=https://user:pass@eu-01.outboundgateway.com:8443
# Use with docker run
docker run --env-file .env my-app:latest
# Or in docker-compose.yml
services:
app:
env_file: .env
Pass the proxy URL at runtime with the --env flag. No image rebuild needed.
# Pass proxy at runtime
docker run --env HTTPS_PROXY=https://user:pass@eu-01.outboundgateway.com:8443 \
--env HTTP_PROXY=https://user:pass@eu-01.outboundgateway.com:8443 \
my-app:latest
# Or use an env file
docker run --env-file .env my-app:latest📖 Complete Documentation: For detailed examples, error handling, and advanced configurations, see our Python SSL Proxy Guide, Node.js Guide, and all other language guides.
EU-hosted infrastructure with GDPR-conscious data handling for your containerized workloads.
Your proxy infrastructure runs entirely within the European Union. Container traffic stays in EU data centers.
Designed for GDPR-conscious environments. TLS passthrough means your container payloads are never visible to the proxy.
Container traffic routes entirely within EU infrastructure. No detours through US-based servers that could complicate compliance.
One static IP provides a clear, auditable outbound identity for compliance audits and partner security reviews.
One fixed IP for all containers. Only your containers use it. Whitelist once, deploy forever.
Set an environment variable in your Docker Compose file. Your application code stays exactly the same.
European data centers. GDPR-conscious setup. Perfect for businesses with EU compliance requirements.
Docker Compose, Dockerfile, Docker Swarm, standalone containers — one static IP covers every setup.
TLS passthrough means we can't see your traffic. Your API keys and payloads stay secure.
€29/month flat. No usage tiers, no per-request billing, no surprises. Cancel anytime.
Stop worrying about dynamic container IPs breaking your integrations. Start using a dedicated, EU-based static IP today.
€29/month starter plan • 7-day refund policy • Direct founder support
We're happy to help you determine if OutboundGateway is the right fit for your Docker containers.
Contact Our Founders →