🇪🇺 Static IP for Black Forest Labs — FLUX Image Proxy

🇪🇺 Static IP for Black Forest Labs

Generating images with Black Forest Labs FLUX models from containers, serverless, or cloud platforms? Your dynamic outbound IP changes on every deploy. Route FLUX image generation requests and async polling through a dedicated static EU IP for stable, whitelisted access.

generate.py

import requests

# Route through static EU IP

# HTTPS_PROXY=https://user:pass@eu-01.outboundgateway.com:8443

resp = requests.post(

  "https://api.bfl.ai/v1/flux-pro-1.1",

  headers={"Authorization": "Bearer KEY"},

  json={"prompt": "A serene forest"}

)

The Problem

FLUX image generation pipelines need stable, auditable outbound IPs — but your infrastructure IPs keep changing

API Key IP Restrictions

Enterprise teams restrict FLUX API keys to approved IP addresses. Your containers, serverless, and cloud services rotate IPs constantly — breaking image generation access on every deploy.

Dynamic IPs Break Polling

The FLUX API uses async polling — you submit a request, then poll for the result. Kubernetes pods and Lambda functions get new IPs on every scale event, breaking both the submission and the polling steps.

Prompt Data & GDPR

Prompts may contain user-generated or sensitive content. Compliance audits require stable, documented outbound IPs for data flow traceability.

Multi-Environment Complexity

Dev, staging, and production environments each need separate IP management. Different microservices call FLUX from different IPs — unmanageable and unauditable at scale.

When Your Security Team Asks

"All FLUX API access must be restricted to approved IP addresses for compliance."

You need one stable IP to give them — not an IP that changes with every deployment.

The Solution

Route Black Forest Labs API Calls Through a Dedicated HTTPS Proxy with Static IP

Your AI Application

HTTPS Proxy

(Static EU IP)

FLUX API

Black Forest Labs sees your fixed EU IP addresses — every API call from generation requests to result polling. Two IPs for high availability.

Works with the full FLUX lineup — FLUX.2, FLUX 1.1 Pro, Dev, Schnell, Kontext, and the BFL async polling flow
Set HTTPS_PROXY as an environment variable — zero code changes required
TLS passthrough — prompts, API keys, and generated images stay encrypted end-to-end

Why Teams Choose This for Black Forest Labs

Two static IPs for HA — whitelist both for IP-restricted FLUX keys with automatic failover, no single point of failure
Survives the async polling flow — your submit request and poll-for-result calls both come from the same stable IP
EU-hosted infrastructure — Black Forest Labs is German (founded in Freiburg), and so is our proxy. End-to-end EU-only routing.
GDPR compliance — stable outbound IP with documented data flow for processing prompts and generated content
Works with requests, the Vercel AI SDK, LangChain, and any HTTP library — standard HTTPS_PROXY support
Consolidates API calls from all services — Lambda, Docker, Kubernetes, on-premise — into two auditable IPs

Designed For

Creative AI Developers

Building image generation features with FLUX that need a stable outbound IP for enterprise security and IP-restricted API keys

Design & Marketing Platforms

Running FLUX-powered creative tools for EU clients that require IP-whitelisted access and GDPR-conscious image generation

AI Product Teams

Scaling batch image generation workloads with FLUX across multi-region deployments that need consistent, auditable outbound IPs

Compliance Officers

Ensuring GDPR compliance for AI image generation, with auditable outbound IP trails and EU-only data routing

Implementation

Set HTTPS_PROXY as an environment variable. All Black Forest Labs API calls route through your static EU IP. No code changes needed.

Python (requests + polling)

Set HTTPS_PROXY in your environment. The requests library picks it up automatically — both the generation request and the polling call route through your static EU IP.

# .env or shell
HTTPS_PROXY=https://user:pass@eu-01.outboundgateway.com:8443
BFL_API_KEY=your_api_key

import os, time
import requests

headers = {"Authorization": f"Bearer {os.environ['BFL_API_KEY']}"}

# 1) Submit the generation request (routes through HTTPS_PROXY)
resp = requests.post(
    "https://api.bfl.ai/v1/flux-pro-1.1",
    headers=headers,
    json={"prompt": "A serene black forest at dawn"},
)
request_id = resp.json()["id"]

# 2) Poll for the result (also routes through HTTPS_PROXY)
while True:
    status = requests.get(f"https://api.bfl.ai/v1/get_result?id={request_id}", headers=headers).json()
    if status["status"] == "Ready":
        print(status["result"]["sample"])
        break
    time.sleep(2)

Node.js (fetch)

Same pattern — set HTTPS_PROXY in your environment. Use https-proxy-agent for explicit control.

// .env or shell
HTTPS_PROXY=https://user:pass@eu-01.outboundgateway.com:8443
BFL_API_KEY=your_api_key

const { HttpsProxyAgent } = require('https-proxy-agent');

const agent = new HttpsProxyAgent(process.env.HTTPS_PROXY);
const headers = { 'Authorization': `Bearer ${process.env.BFL_API_KEY}` };

// Submit the generation request (routes through your static EU IP)
const res = await fetch('https://api.bfl.ai/v1/flux-pro-1.1', {
  method: 'POST',
  headers,
  body: JSON.stringify({ prompt: 'A serene black forest at dawn' }),
  agent,
});

const { id } = await res.json();
console.log(`Tracking request ${id}`);

Docker / Kubernetes / Lambda

Set the env var in your platform config. Every environment works the same way.

# Docker Compose: reference a .env file (never hardcode secrets)
services:
  app:
    env_file:
      - .env

# Kubernetes: use a Secret object
env:
  - name: HTTPS_PROXY
    valueFrom:
      secretKeyRef:
        name: outboundgateway-proxy
        key: proxy-url

# AWS Lambda: set in function environment variables
HTTPS_PROXY=${OUTBOUNDGATEWAY_PROXY_URL}

Two Static IPs for High Availability

You get two static IP addresses (e.g. 51.xx.xx.10 and 51.xx.xx.11). Whitelist both for your IP-restricted FLUX keys — if one proxy node goes down, traffic automatically fails over. No single point of failure for your image generation workloads.

📖 Complete Documentation: For detailed examples, error handling, and advanced configurations, see our Python SSL Proxy Guide, Node.js Guide, and all other language guides.

Built for European AI

EU-hosted infrastructure designed for GDPR compliance for your FLUX image generation workflows.

EU-to-EU Infrastructure

Black Forest Labs is a German company — and so is our proxy infrastructure. Your FLUX API traffic stays entirely within the EU. Zero cross-border hops.

GDPR-Conscious

TLS passthrough means we never see your prompts or generated images. API keys and content stay encrypted end-to-end through the proxy.

No US-Based Routing

API traffic routes entirely within EU infrastructure. No detours through US servers that could complicate GDPR compliance for prompts and generated content.

Clear Audit Trail

Two static IPs provide a clear, auditable outbound identity for GDPR reviews. Automatic failover keeps your image generation running during maintenance.

Why Developers Choose OutboundGateway for Black Forest Labs

Two Static IPs for HA

Two fixed IPs for all FLUX API calls. Whitelist both for IP-restricted keys — automatic failover if one node goes down.

Zero Code Changes

Set the HTTPS_PROXY env var. requests, fetch, axios, and the Vercel AI SDK detect it automatically. Your FLUX code works as-is.

EU-Hosted Infrastructure

European data centers. GDPR-conscious setup. Black Forest Labs is German — your traffic stays in the EU, end to end.

All FLUX Models

FLUX.2, FLUX 1.1 Pro, Dev, Schnell, Kontext — and the full async polling flow. One static IP covers every endpoint your app uses.

End-to-End Encryption

TLS passthrough means we can't see your traffic. Prompts, generated images, and API keys stay completely private.

Simple Transparent Pricing

€29/month flat. No usage tiers, no per-request billing, no surprises. Cancel anytime.

Get Your Static EU IP for Black Forest Labs

Stop worrying about dynamic IPs breaking your FLUX API access. Start using a dedicated, EU-based static IP for GDPR-compliant image generation.

€29/month starter plan • 7-day refund policy • Direct founder support

Still Deciding?

We're happy to help you determine if OutboundGateway is the right fit for your FLUX image generation integrations.

Contact Our Founders →