🇪🇺 Static IP for Coolify

One fixed EU IP pair for every server Coolify manages

Per app: Configuration > Environment Variables

Open the application, add the variable under Configuration > Environment Variables, leave it a runtime variable, and restart the app so the container is recreated with the new environment. Use Developer view to paste several lines at once.

# Coolify app environment (Developer view)
HTTPS_PROXY=https://user:pass@eu-01.outboundgateway.com:8443
NO_PROXY=localhost,127.0.0.1

Whole fleet: define it once as a Shared Variable

Create the proxy URL at team, project, or environment scope, then reference it from any app. One edit updates every application that points at it.

# In each app's Environment Variables
HTTPS_PROXY={{environment.OGW_PROXY_URL}}

Python apps

requests and httpx read HTTPS_PROXY from the container environment automatically. No code changes.

import os
import requests

# picked up from HTTPS_PROXY set in Coolify
r = requests.get(
    "https://api.partner.eu/orders",
    headers={"Authorization":
        f"Bearer {os.environ['PARTNER_TOKEN']}"},
)

Node.js apps

Node's fetch does not follow proxy environment variables on its own. Wire it explicitly with https-proxy-agent.

const { HttpsProxyAgent } = require('https-proxy-agent');
const agent = new HttpsProxyAgent(process.env.HTTPS_PROXY);

const res = await fetch('https://api.partner.eu/orders', {
  headers: { 'Authorization': 'Bearer ..' },
  agent,
});

Docker Compose deployments

Coolify detects ${...} references in your Compose file and surfaces them as application variables, so the URL never sits hardcoded in the repository.

# docker-compose.yml, deployed through Coolify
services:
  api:
    environment:
      - HTTPS_PROXY=${OGW_PROXY_URL}
      - NO_PROXY=localhost,127.0.0.1