DYNR/netbird
2
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-08-05 00:15:26 -04:00
Code Issues 23.5k Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #5359] Proxy Setup with Caddy #11328

New Issue
Open
opened 2026-08-05 01:29:20 -04:00 by saavagebueno · 28 comments
saavagebueno commented 2026-08-05 01:29:20 -04:00
Owner
Copy Link

Originally created by @da-wilky on GitHub (Feb 17, 2026).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/5359

Is your feature request related to a problem? Please describe.
Some time ago I switched from Traefik to Caddy and wont ever go back based on the UX of those two reverse proxies. I had kinda a bad time with Traefik (better than NGINX, but I feel its a pain to add the labels to each container and have this config spread around) and Caddy solved all my problems. So I want to keep Caddy while also being able to use the proxy.

Describe the solution you'd like
A stable production ready Caddy configuration, even tho I think this might not be in your hand. But maybe something can be done by design.

Describe alternatives you've considered
Currently I have a working setup with Caddy for the new Proxy. I will soon create a PR for adding it to the docs as beta, because I dont think this is really production ready, even tho I encountered no issues yet.

Setup

Follow the docs (https://docs.netbird.io/selfhosted/migration/enable-reverse-proxy)

  1. In case you are using the microservice architecture/not netbird-server, use this command instead of the provided command inside the docs to create the management token: docker exec -it netbird-management /go/bin/netbird-mgmt token create --name "my-proxy", thanks to @derlaft

  2. Modify the docker-compose.yml to this:

  # ...

  # Proxy
  proxy:
    image: netbirdio/reverse-proxy:latest
    container_name: netbird-proxy
    extra_hosts:
      - "netbird.domain.com:172.18.0.18" # IP of the Caddy Container
    restart: unless-stopped
    depends_on: # If you use microservice arch use this instead of the docs, if using netbird-server dont change this section
      - management
      - signal
      - relay
    env_file:
      - ./proxy.env
    volumes:
      - netbird_proxy_certs:/certs
    # Remove all the labels
    logging:
      driver: "json-file"
      options:
        max-size: "500m"
        max-file: "2"
    networks:
      default:
      caddy: # Add caddy network to the container

volumes:
  # ...
  netbird_proxy_certs:

networks:
  caddy:              # Add caddy network
    external: true

Also make sure the proxy.env file contains the following line:

...
NB_PROXY_PROXY_PROTOCOL=true
  1. Setup Caddy
  • To be able to pass TLS directly to the netbird-proxy we need the caddy l4 plugin (https://github.com/mholt/caddy-l4). This plugin is still in development, so this setup is not production ready.
  • Create a Dockerfile:
ARG VERSION=2

FROM caddy:${VERSION}-builder AS builder
RUN xcaddy build --with github.com/mholt/caddy-l4

FROM caddy:${VERSION}-alpine
COPY --from=builder /usr/bin/caddy /usr/bin/caddy
  • Use this Dockerfile and build your own caddy image from docker-compose.yml
name: caddy

services:
  caddy:
    image: local-caddy-l4  # Name it how you like
    build:
      context: .
      dockerfile: Dockerfile
      args:
        VERSION: 2
    restart: unless-stopped
    ports:
      - 80:80
      - 443:443
    volumes:
      - ./caddy:/etc/caddy
      - ./data:/data
      - ./config:/config
    networks:
      caddy:
        ipv4_address: 172.18.0.18 # Define your IPv4 here, that you might reference inside the netbird proxy setup, the IP needs to be inside the subnet of the caddy network

networks:
  caddy:
    external: true
  1. Caddy Configuration
    Create the caddy folder and go into it with mkdir caddy && cd caddy (the name should be caddy, or change the name inside the volume section of docker-compose). Inside add the Caddyfile:
# This section needs to be first inside the Caddyfile and cannot be moved!
{
  admin off  # Optional, disables the admin web ui (recommended if not used)
  servers {
    listener_wrappers {
      layer4 {    # This section passes the TLS directly to the container for the specified domain (and wildcard subdomain)
        @proxy-exact tls sni proxy.domain.com
        route @proxy-exact {
          proxy {
            proxy_protocol v2
            upstream netbird-proxy:8443
          }
        } 
        @proxy-wild tls sni_regexp ^[^.]+\.proxy\.domain\.com$
        route @proxy-wild {
          proxy {
            proxy_protocol v2
            upstream netbird-proxy:8443
          }
        }
      }
      tls
    }
  }
}

netbird.domain.com {
    # ws-proxy signal
    handle /ws-proxy/signal* {
        reverse_proxy netbird-signal:80
    }

    # ws-proxy management
    handle /ws-proxy/management* {
        reverse_proxy netbird-management:33073
    }

    # SignalExchange (gRPC)
    handle /signalexchange.SignalExchange/* {
        reverse_proxy h2c://netbird-signal:10000
    }

    # Relay
    handle /relay* {
        reverse_proxy netbird-relay:33080
    }

    # API
    handle /api* {
        reverse_proxy netbird-management:33073 
    }

    # Management gRPC
    handle /management.ManagementService/* {
        reverse_proxy h2c://netbird-management:33073
    }

    # Proxy gRPC -> DONT FORGET TO ADD THIS
    handle /management.ProxyService/* {
        reverse_proxy h2c://netbird-management:33073
    }
    
    # Dashboard
    handle {
        reverse_proxy netbird-dashboard:80
    }
}

# ... additional hosts
  1. Caddy startup
  • Run docker compose build to build the image and docker compose up -d to run caddy.
Originally created by @da-wilky on GitHub (Feb 17, 2026). Original GitHub issue: https://github.com/netbirdio/netbird/issues/5359 **Is your feature request related to a problem? Please describe.** Some time ago I switched from Traefik to Caddy and wont ever go back based on the UX of those two reverse proxies. I had kinda a bad time with Traefik (better than NGINX, but I feel its a pain to add the labels to each container and have this config spread around) and Caddy solved all my problems. So I want to keep Caddy while also being able to use the proxy. **Describe the solution you'd like** A stable production ready Caddy configuration, even tho I think this might not be in your hand. But maybe something can be done by design. **Describe alternatives you've considered** Currently I have a working setup with Caddy for the new Proxy. I will soon create a PR for adding it to the docs as beta, because I dont think this is really production ready, even tho I encountered no issues yet. ### Setup Follow the docs (https://docs.netbird.io/selfhosted/migration/enable-reverse-proxy) 1. In case you are using the microservice architecture/not netbird-server, use this command instead of the provided command inside the docs to create the management token: `docker exec -it netbird-management /go/bin/netbird-mgmt token create --name "my-proxy"`, thanks to @derlaft 2. Modify the `docker-compose.yml` to this: ```yml # ... # Proxy proxy: image: netbirdio/reverse-proxy:latest container_name: netbird-proxy extra_hosts: - "netbird.domain.com:172.18.0.18" # IP of the Caddy Container restart: unless-stopped depends_on: # If you use microservice arch use this instead of the docs, if using netbird-server dont change this section - management - signal - relay env_file: - ./proxy.env volumes: - netbird_proxy_certs:/certs # Remove all the labels logging: driver: "json-file" options: max-size: "500m" max-file: "2" networks: default: caddy: # Add caddy network to the container volumes: # ... netbird_proxy_certs: networks: caddy: # Add caddy network external: true ``` Also make sure the `proxy.env` file contains the following line: ```env ... NB_PROXY_PROXY_PROTOCOL=true ``` 3. Setup Caddy - To be able to pass TLS directly to the netbird-proxy we need the caddy l4 plugin (https://github.com/mholt/caddy-l4). This plugin is still in development, so this setup is not production ready. - Create a `Dockerfile`: ```dockerfile ARG VERSION=2 FROM caddy:${VERSION}-builder AS builder RUN xcaddy build --with github.com/mholt/caddy-l4 FROM caddy:${VERSION}-alpine COPY --from=builder /usr/bin/caddy /usr/bin/caddy ``` - Use this `Dockerfile` and build your own caddy image from `docker-compose.yml` ```yml name: caddy services: caddy: image: local-caddy-l4 # Name it how you like build: context: . dockerfile: Dockerfile args: VERSION: 2 restart: unless-stopped ports: - 80:80 - 443:443 volumes: - ./caddy:/etc/caddy - ./data:/data - ./config:/config networks: caddy: ipv4_address: 172.18.0.18 # Define your IPv4 here, that you might reference inside the netbird proxy setup, the IP needs to be inside the subnet of the caddy network networks: caddy: external: true ``` 4. Caddy Configuration Create the caddy folder and go into it with `mkdir caddy && cd caddy` (the name should be caddy, or change the name inside the volume section of docker-compose). Inside add the `Caddyfile`: ```caddyfile # This section needs to be first inside the Caddyfile and cannot be moved! { admin off # Optional, disables the admin web ui (recommended if not used) servers { listener_wrappers { layer4 { # This section passes the TLS directly to the container for the specified domain (and wildcard subdomain) @proxy-exact tls sni proxy.domain.com route @proxy-exact { proxy { proxy_protocol v2 upstream netbird-proxy:8443 } } @proxy-wild tls sni_regexp ^[^.]+\.proxy\.domain\.com$ route @proxy-wild { proxy { proxy_protocol v2 upstream netbird-proxy:8443 } } } tls } } } netbird.domain.com { # ws-proxy signal handle /ws-proxy/signal* { reverse_proxy netbird-signal:80 } # ws-proxy management handle /ws-proxy/management* { reverse_proxy netbird-management:33073 } # SignalExchange (gRPC) handle /signalexchange.SignalExchange/* { reverse_proxy h2c://netbird-signal:10000 } # Relay handle /relay* { reverse_proxy netbird-relay:33080 } # API handle /api* { reverse_proxy netbird-management:33073 } # Management gRPC handle /management.ManagementService/* { reverse_proxy h2c://netbird-management:33073 } # Proxy gRPC -> DONT FORGET TO ADD THIS handle /management.ProxyService/* { reverse_proxy h2c://netbird-management:33073 } # Dashboard handle { reverse_proxy netbird-dashboard:80 } } # ... additional hosts ``` 5. Caddy startup - Run `docker compose build` to build the image and `docker compose up -d` to run caddy.
saavagebueno added the feature-request label 2026-08-05 01:29:20 -04:00
saavagebueno commented 2026-08-05 01:29:20 -04:00
Author
Owner
Copy Link

@sjansen1 commented on GitHub (Feb 17, 2026):

Good feature request, Caddy with L4 came right into my mind after reading that reverse proxy requires Traffik for TCP proxy. I dont want to hihack this post, but i like to see support for non wildcard stuff to avoid extra hosts like mypp.proxy... Then, Netbird would be an awesome replacement for Azure Application Proxy without the need to have different hostnames for services the run over Netbird Reverse Proxy.

<!-- gh-comment-id:3914494664 --> @sjansen1 commented on GitHub (Feb 17, 2026): Good feature request, Caddy with L4 came right into my mind after reading that reverse proxy requires Traffik for TCP proxy. I dont want to hihack this post, but i like to see support for non wildcard stuff to avoid extra hosts like mypp.proxy... Then, Netbird would be an awesome replacement for Azure Application Proxy without the need to have different hostnames for services the run over Netbird Reverse Proxy.
saavagebueno commented 2026-08-05 01:29:20 -04:00
Author
Owner
Copy Link

@shaban00 commented on GitHub (Feb 17, 2026):

@da-wilky I tried to follow your guide but it's not working for me. I don't see my proxy domain. Am I doing something wrong?

Image

----- Caddyfile -----

{
  admin off
  servers {
    listener_wrappers {
      layer4 {
        @proxy-exact tls sni vpnproxy.example.cc
        route @proxy-exact {
          proxy proxy:8443
        } 
        @proxy-wild tls sni_regexp ^[^.]+\.vpnproxy\.example\.cc$
        route @proxy-wild {
          proxy proxy:8443
        }
      }
      tls
    }
  }
}

(security_headers) {
	header * {
		Strict-Transport-Security "max-age=3600; includeSubDomains; preload"
		X-Content-Type-Options "nosniff"
		X-Frame-Options "SAMEORIGIN"
		X-XSS-Protection "1; mode=block"
		Referrer-Policy "strict-origin-when-cross-origin"
		-Server
		-X-Powered-By
		-Via
	}
}

(compression) {
	encode zstd gzip
}

vpn.example.cc {
        import security_headers
        import compression
        # relay
        reverse_proxy /relay* relay:80
        # Signal
        reverse_proxy /ws-proxy/signal* signal:80
        reverse_proxy /signalexchange.SignalExchange/* h2c://signal:10000
        # Management
        reverse_proxy /api/* management:80
        reverse_proxy /ws-proxy/management* management:80
        reverse_proxy /management.ManagementService/* h2c://management:80
        reverse_proxy /management.ProxyService/* h2c://management:80
        reverse_proxy /oauth2/* management:80
        # Dashboard
        reverse_proxy /* dashboard:80
}

----- Dockerfile.caddy -----

ARG VERSION=2

FROM caddy:${VERSION}-builder AS builder
RUN xcaddy build --with github.com/mholt/caddy-l4

FROM caddy:${VERSION}-alpine
COPY --from=builder /usr/bin/caddy /usr/bin/caddy

----- docker-compose.yml -----

x-default: &default
  restart: unless-stopped
  networks:
    - netbird
  logging:
    driver: "json-file"
    options:
      max-size: "50m"
      max-file: "5"

services:
  postgres:
    image: postgres:18
    container_name: postgres
    <<: *default
    env_file:
      - netbird.env
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U $$POSTGRES_USER -d $$POSTGRES_DB"]
      interval: 5s
      timeout: 5s
      retries: 5
    volumes:
      - postgres:/var/lib/postgresql

  dashboard:
    image: netbirdio/dashboard:latest
    container_name: dashboard
    <<: *default
    env_file:
      - netbird.env

  signal:
    image: netbirdio/signal:latest
    container_name: signal
    <<: *default

  relay:
    image: netbirdio/relay:latest
    container_name: relay
    <<: *default
    env_file:
      - netbird.env
    ports:
      - "3478:3478/udp"

  management:
    image: netbirdio/management:latest
    container_name: management
    <<: *default
    env_file:
      - netbird.env
    command:
      [
        "--disable-anonymous-metrics=true",
        "--disable-geolite-update=false",
        "--disable-single-account-mode=false",
        "--dns-domain=netbird.cloud",
        "--idp-sign-key-refresh-enabled",
        "--port",
        "80",
        "--single-account-mode-domain=netbird.cloud",
        "--log-file",
        "console",
        "--log-level",
        "info",
      ]
    volumes:
      - management:/var/lib/netbird
      - ./management.json:/etc/netbird/management.json
    depends_on:
      postgres:
        condition: service_healthy

  proxy:
    image: netbirdio/reverse-proxy:latest
    container_name: proxy
    extra_hosts:
      - "vpn.example.cc:172.30.0.10"
    restart: unless-stopped
    depends_on:
      - signal
      - relay
      - management
    env_file:
      - netbird.env
    volumes:
      - proxy:/certs

  caddy:
    image: caddy
    container_name: caddy
    build:
      context: .
      dockerfile: Dockerfile.caddy
      args:
        VERSION: 2
    <<: *default
    ports:
      - "443:443"
      - "443:443/udp"
      - "80:80"
    volumes:
      - caddy-data:/data
      - caddy-config:/config
      - ./Caddyfile:/etc/caddy/Caddyfile
    networks:
      netbird:
        ipv4_address: 172.30.0.10

volumes:
  postgres:
    name: postgres
    driver: local
  caddy-data:
    name: caddy-data
    driver: local
  caddy-config:
    name: caddy-config
    driver: local
  management:
    name: management
    driver: local
  proxy:
    name: proxy
    driver: local

networks:
  netbird:
    name: netbird
    driver: bridge
    ipam:
      config:
        - subnet: 172.30.0.0/24
          gateway: 172.30.0.1

----- netbird.env -----

# Database
POSTGRES_HOST=postgres
POSTGRES_PORT=5432
POSTGRES_DB=netbird
POSTGRES_USER=netbird
POSTGRES_PASSWORD=netbird

# Management
NETBIRD_DOMAIN=vpn.example.cc
NETBIRD_MGMT_API_ENDPOINT=https://vpn.example.cc
NETBIRD_MGMT_GRPC_API_ENDPOINT=https://vpn.example.cc
NETBIRD_MGMT_DISABLE_DEFAULT_POLICY=true
AUTH_AUDIENCE=netbird-dashboard
AUTH_CLIENT_ID=netbird-dashboard
AUTH_CLIENT_SECRET=
AUTH_AUTHORITY=https://vpn.example.cc/oauth2
USE_AUTH0=false
AUTH_REDIRECT_URI=/nb-auth
AUTH_SILENT_REDIRECT_URI=/nb-silent-auth
AUTH_SUPPORTED_SCOPES=openid profile email groups
NGINX_SSL_PORT=443
LETSENCRYPT_DOMAIN=none
LETSENCRYPT_EMAIL=example@gmail.com
NETBIRD_STORE_CONFIG_ENGINE=postgres
NETBIRD_STORE_ENGINE_POSTGRES_DSN=host=${POSTGRES_HOST} user=${POSTGRES_USER} password=${POSTGRES_PASSWORD} dbname=${POSTGRES_DB} port=${POSTGRES_PORT}
NB_ACTIVITY_EVENT_STORE_ENGINE=postgres
NB_ACTIVITY_EVENT_POSTGRES_DSN=host=${POSTGRES_HOST} user=${POSTGRES_USER} password=${POSTGRES_PASSWORD} dbname=${POSTGRES_DB} port=${POSTGRES_PORT}

# Relay
NB_LOG_LEVEL=info
NB_LISTEN_ADDRESS=:80
NB_EXPOSED_ADDRESS=rels://vpn.example.cc:443
NB_AUTH_SECRET=BJf3f/GxSU2OKz/WkBNSDpGatNh1m3a007bixHGrOmQ
NB_ENABLE_STUN=true
NB_STUN_LOG_LEVEL=info
NB_STUN_PORTS=3478

# Proxy
NB_PROXY_DEBUG_LOGS=false
NB_PROXY_MANAGEMENT_ADDRESS=http://management:80
NB_PROXY_ALLOW_INSECURE=true
NB_PROXY_DOMAIN=vpnproxy.example.cc
NB_PROXY_ADDRESS=:8443
NB_PROXY_TOKEN=nbx_dgsdfgsd
NB_PROXY_CERTIFICATE_DIRECTORY=/certs
NB_PROXY_ACME_CERTIFICATES=true
NB_PROXY_ACME_CHALLENGE_TYPE=tls-alpn-01
NB_PROXY_OIDC_CLIENT_ID=netbird-proxy
NB_PROXY_OIDC_ENDPOINT=https://vpn.example.cc/oauth2
NB_PROXY_OIDC_SCOPES=openid,profile,email
NB_PROXY_FORWARDED_PROTO=https
NB_PROXY_PROXY_PROTOCOL=true
NB_PROXY_TRUSTED_PROXIES=172.18.0.18
<!-- gh-comment-id:3916475791 --> @shaban00 commented on GitHub (Feb 17, 2026): @da-wilky I tried to follow your guide but it's not working for me. I don't see my proxy domain. Am I doing something wrong? <img width="1212" height="650" alt="Image" src="https://github.com/user-attachments/assets/1d5641eb-f2de-4cb4-a222-3b0636892b67" /> ----- Caddyfile ----- ``` { admin off servers { listener_wrappers { layer4 { @proxy-exact tls sni vpnproxy.example.cc route @proxy-exact { proxy proxy:8443 } @proxy-wild tls sni_regexp ^[^.]+\.vpnproxy\.example\.cc$ route @proxy-wild { proxy proxy:8443 } } tls } } } (security_headers) { header * { Strict-Transport-Security "max-age=3600; includeSubDomains; preload" X-Content-Type-Options "nosniff" X-Frame-Options "SAMEORIGIN" X-XSS-Protection "1; mode=block" Referrer-Policy "strict-origin-when-cross-origin" -Server -X-Powered-By -Via } } (compression) { encode zstd gzip } vpn.example.cc { import security_headers import compression # relay reverse_proxy /relay* relay:80 # Signal reverse_proxy /ws-proxy/signal* signal:80 reverse_proxy /signalexchange.SignalExchange/* h2c://signal:10000 # Management reverse_proxy /api/* management:80 reverse_proxy /ws-proxy/management* management:80 reverse_proxy /management.ManagementService/* h2c://management:80 reverse_proxy /management.ProxyService/* h2c://management:80 reverse_proxy /oauth2/* management:80 # Dashboard reverse_proxy /* dashboard:80 } ``` ----- Dockerfile.caddy ----- ``` ARG VERSION=2 FROM caddy:${VERSION}-builder AS builder RUN xcaddy build --with github.com/mholt/caddy-l4 FROM caddy:${VERSION}-alpine COPY --from=builder /usr/bin/caddy /usr/bin/caddy ``` ----- docker-compose.yml ----- ``` x-default: &default restart: unless-stopped networks: - netbird logging: driver: "json-file" options: max-size: "50m" max-file: "5" services: postgres: image: postgres:18 container_name: postgres <<: *default env_file: - netbird.env healthcheck: test: ["CMD-SHELL", "pg_isready -U $$POSTGRES_USER -d $$POSTGRES_DB"] interval: 5s timeout: 5s retries: 5 volumes: - postgres:/var/lib/postgresql dashboard: image: netbirdio/dashboard:latest container_name: dashboard <<: *default env_file: - netbird.env signal: image: netbirdio/signal:latest container_name: signal <<: *default relay: image: netbirdio/relay:latest container_name: relay <<: *default env_file: - netbird.env ports: - "3478:3478/udp" management: image: netbirdio/management:latest container_name: management <<: *default env_file: - netbird.env command: [ "--disable-anonymous-metrics=true", "--disable-geolite-update=false", "--disable-single-account-mode=false", "--dns-domain=netbird.cloud", "--idp-sign-key-refresh-enabled", "--port", "80", "--single-account-mode-domain=netbird.cloud", "--log-file", "console", "--log-level", "info", ] volumes: - management:/var/lib/netbird - ./management.json:/etc/netbird/management.json depends_on: postgres: condition: service_healthy proxy: image: netbirdio/reverse-proxy:latest container_name: proxy extra_hosts: - "vpn.example.cc:172.30.0.10" restart: unless-stopped depends_on: - signal - relay - management env_file: - netbird.env volumes: - proxy:/certs caddy: image: caddy container_name: caddy build: context: . dockerfile: Dockerfile.caddy args: VERSION: 2 <<: *default ports: - "443:443" - "443:443/udp" - "80:80" volumes: - caddy-data:/data - caddy-config:/config - ./Caddyfile:/etc/caddy/Caddyfile networks: netbird: ipv4_address: 172.30.0.10 volumes: postgres: name: postgres driver: local caddy-data: name: caddy-data driver: local caddy-config: name: caddy-config driver: local management: name: management driver: local proxy: name: proxy driver: local networks: netbird: name: netbird driver: bridge ipam: config: - subnet: 172.30.0.0/24 gateway: 172.30.0.1 ``` ----- netbird.env ----- ``` # Database POSTGRES_HOST=postgres POSTGRES_PORT=5432 POSTGRES_DB=netbird POSTGRES_USER=netbird POSTGRES_PASSWORD=netbird # Management NETBIRD_DOMAIN=vpn.example.cc NETBIRD_MGMT_API_ENDPOINT=https://vpn.example.cc NETBIRD_MGMT_GRPC_API_ENDPOINT=https://vpn.example.cc NETBIRD_MGMT_DISABLE_DEFAULT_POLICY=true AUTH_AUDIENCE=netbird-dashboard AUTH_CLIENT_ID=netbird-dashboard AUTH_CLIENT_SECRET= AUTH_AUTHORITY=https://vpn.example.cc/oauth2 USE_AUTH0=false AUTH_REDIRECT_URI=/nb-auth AUTH_SILENT_REDIRECT_URI=/nb-silent-auth AUTH_SUPPORTED_SCOPES=openid profile email groups NGINX_SSL_PORT=443 LETSENCRYPT_DOMAIN=none LETSENCRYPT_EMAIL=example@gmail.com NETBIRD_STORE_CONFIG_ENGINE=postgres NETBIRD_STORE_ENGINE_POSTGRES_DSN=host=${POSTGRES_HOST} user=${POSTGRES_USER} password=${POSTGRES_PASSWORD} dbname=${POSTGRES_DB} port=${POSTGRES_PORT} NB_ACTIVITY_EVENT_STORE_ENGINE=postgres NB_ACTIVITY_EVENT_POSTGRES_DSN=host=${POSTGRES_HOST} user=${POSTGRES_USER} password=${POSTGRES_PASSWORD} dbname=${POSTGRES_DB} port=${POSTGRES_PORT} # Relay NB_LOG_LEVEL=info NB_LISTEN_ADDRESS=:80 NB_EXPOSED_ADDRESS=rels://vpn.example.cc:443 NB_AUTH_SECRET=BJf3f/GxSU2OKz/WkBNSDpGatNh1m3a007bixHGrOmQ NB_ENABLE_STUN=true NB_STUN_LOG_LEVEL=info NB_STUN_PORTS=3478 # Proxy NB_PROXY_DEBUG_LOGS=false NB_PROXY_MANAGEMENT_ADDRESS=http://management:80 NB_PROXY_ALLOW_INSECURE=true NB_PROXY_DOMAIN=vpnproxy.example.cc NB_PROXY_ADDRESS=:8443 NB_PROXY_TOKEN=nbx_dgsdfgsd NB_PROXY_CERTIFICATE_DIRECTORY=/certs NB_PROXY_ACME_CERTIFICATES=true NB_PROXY_ACME_CHALLENGE_TYPE=tls-alpn-01 NB_PROXY_OIDC_CLIENT_ID=netbird-proxy NB_PROXY_OIDC_ENDPOINT=https://vpn.example.cc/oauth2 NB_PROXY_OIDC_SCOPES=openid,profile,email NB_PROXY_FORWARDED_PROTO=https NB_PROXY_PROXY_PROTOCOL=true NB_PROXY_TRUSTED_PROXIES=172.18.0.18 ```
saavagebueno commented 2026-08-05 01:29:20 -04:00
Author
Owner
Copy Link

@da-wilky commented on GitHub (Feb 17, 2026):

The only deviation from the docs I can tell is the NB_PROXY_MANAGEMENT_ADDRESS=http://management:80 where the public endpoint is referenced inside the docs. Maybe that already helps?

<!-- gh-comment-id:3916561345 --> @da-wilky commented on GitHub (Feb 17, 2026): The only deviation from the docs I can tell is the `NB_PROXY_MANAGEMENT_ADDRESS=http://management:80` where the public endpoint is referenced inside the docs. Maybe that already helps?
saavagebueno commented 2026-08-05 01:29:20 -04:00
Author
Owner
Copy Link

@shaban00 commented on GitHub (Feb 17, 2026):

@da-wilky That's the management URL

Image 
https://github.com/netbirdio/netbird/blob/main/proxy/cmd/proxy/cmd/root.go#L69

In a fresh install it uses NB_PROXY_MANAGEMENT_ADDRESS=http://netbird-server:80

Image
<!-- gh-comment-id:3916809076 --> @shaban00 commented on GitHub (Feb 17, 2026): @da-wilky That's the management URL <img width="1401" height="832" alt="Image" src="https://github.com/user-attachments/assets/47e89e69-2263-40e7-8f44-e16a1c7cbfee" /> ``` https://github.com/netbirdio/netbird/blob/main/proxy/cmd/proxy/cmd/root.go#L69 ``` In a fresh install it uses `NB_PROXY_MANAGEMENT_ADDRESS=http://netbird-server:80` <img width="645" height="280" alt="Image" src="https://github.com/user-attachments/assets/1168f92a-6633-4e86-aa20-80558f41f443" />
saavagebueno commented 2026-08-05 01:29:20 -04:00
Author
Owner
Copy Link

@shaban00 commented on GitHub (Feb 17, 2026):

@braginini @mlsmaycon Is something wrong with the setup?

<!-- gh-comment-id:3916819397 --> @shaban00 commented on GitHub (Feb 17, 2026): @braginini @mlsmaycon Is something wrong with the setup?
saavagebueno commented 2026-08-05 01:29:20 -04:00
Author
Owner
Copy Link

@da-wilky commented on GitHub (Feb 17, 2026):

Yea, I thought it needs to be the public facing address. At least I did it that way and its what the documentation shows on the migration guide (https://docs.netbird.io/selfhosted/migration/enable-reverse-proxy#step-3-add-the-proxy-service-to-docker-compose-yml). Have you tried changing it and if it makes a difference?

<!-- gh-comment-id:3916997056 --> @da-wilky commented on GitHub (Feb 17, 2026): Yea, I thought it needs to be the public facing address. At least I did it that way and its what the documentation shows on the migration guide (https://docs.netbird.io/selfhosted/migration/enable-reverse-proxy#step-3-add-the-proxy-service-to-docker-compose-yml). Have you tried changing it and if it makes a difference?
saavagebueno commented 2026-08-05 01:29:20 -04:00
Author
Owner
Copy Link

@LowFatMom commented on GitHub (Feb 18, 2026):

Wait, so you can use Caddy and then manage the reverse proxies in the netbird's UI ??

<!-- gh-comment-id:3920499250 --> @LowFatMom commented on GitHub (Feb 18, 2026): Wait, so you can use Caddy and then manage the reverse proxies in the netbird's UI ??
saavagebueno commented 2026-08-05 01:29:20 -04:00
Author
Owner
Copy Link

@shaban00 commented on GitHub (Feb 18, 2026):

@da-wilky I tried it but it didn't work. I still don't see my proxy cluster in the Reverse Proxy.

NB_PROXY_MANAGEMENT_ADDRESS=https://vpn.example.com:443

<!-- gh-comment-id:3920857832 --> @shaban00 commented on GitHub (Feb 18, 2026): @da-wilky I tried it but it didn't work. I still don't see my proxy cluster in the `Reverse Proxy`. `NB_PROXY_MANAGEMENT_ADDRESS=https://vpn.example.com:443`
saavagebueno commented 2026-08-05 01:29:20 -04:00
Author
Owner
Copy Link

@da-wilky commented on GitHub (Feb 18, 2026):

@shaban00 I can see inside your docker-compose.yml inside the proxy service you are missing the <<: *default, so it seems the proxy and caddy are not inside the same docker network. Maybe check with docker network inspect netbird if both containers are there and else add the line. Maybe that fixes it.

<!-- gh-comment-id:3920903502 --> @da-wilky commented on GitHub (Feb 18, 2026): @shaban00 I can see inside your `docker-compose.yml` inside the `proxy` service you are missing the `<<: *default`, so it seems the proxy and caddy are not inside the same docker network. Maybe check with `docker network inspect netbird` if both containers are there and else add the line. Maybe that fixes it.
saavagebueno commented 2026-08-05 01:29:20 -04:00
Author
Owner
Copy Link

@da-wilky commented on GitHub (Feb 18, 2026):

Wait, so you can use Caddy and then manage the reverse proxies in the netbird's UI ??

@LowFatMom You can use caddy to pass the defined requests to the netbird proxy and then indeed manage your services that should be exposed via netbird using its UI. This thread is just about using caddy instead of traefik for the setup. (https://docs.netbird.io/selfhosted/migration/enable-reverse-proxy)

<!-- gh-comment-id:3920916892 --> @da-wilky commented on GitHub (Feb 18, 2026): > Wait, so you can use Caddy and then manage the reverse proxies in the netbird's UI ?? @LowFatMom You can use caddy to pass the defined requests to the netbird proxy and then indeed manage your services that should be exposed via netbird using its UI. This thread is just about using caddy instead of traefik for the setup. (https://docs.netbird.io/selfhosted/migration/enable-reverse-proxy)
saavagebueno commented 2026-08-05 01:29:21 -04:00
Author
Owner
Copy Link

@LowFatMom commented on GitHub (Feb 18, 2026):

I tried both using built in traefik (option 0) and caddy (option 4) on an already deployed caddy instance and while this worked, I couldn't manage the proxy from the top ui (no cluster found)

With the built traefik, I'm getting half the speeds on my file transfer that I normally get with caddy.

However your guide include more stuff to do than when using option 4 in the setup, will give it a try !!

<!-- gh-comment-id:3920988594 --> @LowFatMom commented on GitHub (Feb 18, 2026): I tried both using built in traefik (option 0) and caddy (option 4) on an already deployed caddy instance and while this worked, I couldn't manage the proxy from the top ui (no cluster found) With the built traefik, I'm getting half the speeds on my file transfer that I normally get with caddy. However your guide include more stuff to do than when using option 4 in the setup, will give it a try !!
saavagebueno commented 2026-08-05 01:29:21 -04:00
Author
Owner
Copy Link

@shaban00 commented on GitHub (Feb 18, 2026):

@da-wilky You were right, I forgot to add <<: *default to the proxy. I can see the proxy cluster domain now. Thank you very much.

<!-- gh-comment-id:3921053636 --> @shaban00 commented on GitHub (Feb 18, 2026): @da-wilky You were right, I forgot to add `<<: *default` to the proxy. I can see the proxy cluster domain now. Thank you very much.
saavagebueno commented 2026-08-05 01:29:21 -04:00
Author
Owner
Copy Link

@shaban00 commented on GitHub (Feb 18, 2026):

@da-wilky For this it doesn't have to be the public domain, you can use the container name NB_PROXY_MANAGEMENT_ADDRESS=http://management:80

<!-- gh-comment-id:3921095484 --> @shaban00 commented on GitHub (Feb 18, 2026): @da-wilky For this it doesn't have to be the public domain, you can use the container name `NB_PROXY_MANAGEMENT_ADDRESS=http://management:80`
saavagebueno commented 2026-08-05 01:29:21 -04:00
Author
Owner
Copy Link

@shaban00 commented on GitHub (Feb 18, 2026):

@da-wilky Are you able to be issued a certificate?

Image
<!-- gh-comment-id:3921843462 --> @shaban00 commented on GitHub (Feb 18, 2026): @da-wilky Are you able to be issued a certificate? <img width="337" height="135" alt="Image" src="https://github.com/user-attachments/assets/3a7a10fc-9276-41b2-b8ba-3c7ad2cb6fed" />
saavagebueno commented 2026-08-05 01:29:21 -04:00
Author
Owner
Copy Link

@da-wilky commented on GitHub (Feb 18, 2026):

Yes, I have no issues with that. The domains are automatically loading their certs, taking like 15 seconds and then I can connect. Rarely the Issuing certificate is shown longer, even tho I can already access the site with https. In those cases a reload of the website made the button vanish :)

<!-- gh-comment-id:3921953057 --> @da-wilky commented on GitHub (Feb 18, 2026): Yes, I have no issues with that. The domains are automatically loading their certs, taking like 15 seconds and then I can connect. Rarely the Issuing certificate is shown longer, even tho I can already access the site with https. In those cases a reload of the website made the button vanish :)
saavagebueno commented 2026-08-05 01:29:21 -04:00
Author
Owner
Copy Link

@heymoe commented on GitHub (Feb 18, 2026):

@shaban00 Do your netbird clients have a preshared-key or Rosenpass enabled on them? If so, the never ending issuing cert message is likely related to that. I already have an issue open for it here (https://github.com/netbirdio/netbird/issues/5349)

<!-- gh-comment-id:3922175294 --> @heymoe commented on GitHub (Feb 18, 2026): @shaban00 Do your netbird clients have a preshared-key or Rosenpass enabled on them? If so, the never ending issuing cert message is likely related to that. I already have an issue open for it here (https://github.com/netbirdio/netbird/issues/5349)
saavagebueno commented 2026-08-05 01:29:21 -04:00
Author
Owner
Copy Link

@ben-ba commented on GitHub (Feb 18, 2026):

Good feature request, Caddy with L4 came right into my mind after reading that reverse proxy requires Traffik for TCP proxy. I dont want to hihack this post, but i like to see support for non wildcard stuff to avoid extra hosts like mypp.proxy... Then, Netbird would be an awesome replacement for Azure Application Proxy without the need to have different hostnames for services the run over Netbird Reverse Proxy.

Instead of proxy.example.com u can use example.com when ur netbird instance runs as vpn.example.com.
I run this setup since release.

<!-- gh-comment-id:3922846987 --> @ben-ba commented on GitHub (Feb 18, 2026): > Good feature request, Caddy with L4 came right into my mind after reading that reverse proxy requires Traffik for TCP proxy. I dont want to hihack this post, but i like to see support for non wildcard stuff to avoid extra hosts like mypp.proxy... Then, Netbird would be an awesome replacement for Azure Application Proxy without the need to have different hostnames for services the run over Netbird Reverse Proxy. Instead of proxy.example.com u can use example.com when ur netbird instance runs as vpn.example.com. I run this setup since release.
saavagebueno commented 2026-08-05 01:29:21 -04:00
Author
Owner
Copy Link

@shaban00 commented on GitHub (Feb 18, 2026):

@da-wilky I thought it was because I was using NB_PROXY_MANAGEMENT_ADDRESS=http://management:80 so I changed it to NB_PROXY_MANAGEMENT_ADDRESS=https://vpn.shaban.cc:443 just like how you suggested but it's still not working. The certificate issuing is not working. It is still saying Issuing certificate

Is something wrong with my Caddyfile?

{
  admin off
  servers {
    listener_wrappers {
      layer4 {
        @proxy-exact tls sni vpnproxy.example.cc
        route @proxy-exact {
          proxy proxy:8443
        }
        @proxy-wild tls sni_regexp ^[^.]+\.vpnproxy\.example\.cc$
        route @proxy-wild {
          proxy proxy:8443
        }
      }
      tls
    }
    protocols h1 h2
    timeouts {
        read_body   0
        read_header 0
        write       0
        idle        0
    }
  }
}

(security_headers) {
	header * {
		Strict-Transport-Security "max-age=3600; includeSubDomains; preload"
		X-Content-Type-Options "nosniff"
		X-Frame-Options "SAMEORIGIN"
		X-XSS-Protection "1; mode=block"
		Referrer-Policy "strict-origin-when-cross-origin"
		-Server
		-X-Powered-By
		-Via
	}
}

(compression) {
	encode zstd gzip
}

vpn.example.cc {
        import security_headers
        import compression
        # relay
        reverse_proxy /relay* relay:80
        # Signal
        reverse_proxy /ws-proxy/signal* signal:80
        reverse_proxy /signalexchange.SignalExchange/* h2c://signal:10000
        # Management
        reverse_proxy /api/* management:80
        reverse_proxy /ws-proxy/management* management:80
        reverse_proxy /management.ManagementService/* h2c://management:80
        reverse_proxy /management.ProxyService/* h2c://management:80
        reverse_proxy /oauth2/* management:80
        # Dashboard
        reverse_proxy /* dashboard:80
}

Dockerfile.caddy

ARG VERSION=2

FROM caddy:${VERSION}-builder AS builder
RUN xcaddy build --with github.com/mholt/caddy-l4

FROM caddy:${VERSION}-alpine
COPY --from=builder /usr/bin/caddy /usr/bin/caddy
<!-- gh-comment-id:3922944786 --> @shaban00 commented on GitHub (Feb 18, 2026): @da-wilky I thought it was because I was using `NB_PROXY_MANAGEMENT_ADDRESS=http://management:80` so I changed it to `NB_PROXY_MANAGEMENT_ADDRESS=https://vpn.shaban.cc:443` just like how you suggested but it's still not working. The certificate issuing is not working. It is still saying `Issuing certificate` Is something wrong with my Caddyfile? ``` { admin off servers { listener_wrappers { layer4 { @proxy-exact tls sni vpnproxy.example.cc route @proxy-exact { proxy proxy:8443 } @proxy-wild tls sni_regexp ^[^.]+\.vpnproxy\.example\.cc$ route @proxy-wild { proxy proxy:8443 } } tls } protocols h1 h2 timeouts { read_body 0 read_header 0 write 0 idle 0 } } } (security_headers) { header * { Strict-Transport-Security "max-age=3600; includeSubDomains; preload" X-Content-Type-Options "nosniff" X-Frame-Options "SAMEORIGIN" X-XSS-Protection "1; mode=block" Referrer-Policy "strict-origin-when-cross-origin" -Server -X-Powered-By -Via } } (compression) { encode zstd gzip } vpn.example.cc { import security_headers import compression # relay reverse_proxy /relay* relay:80 # Signal reverse_proxy /ws-proxy/signal* signal:80 reverse_proxy /signalexchange.SignalExchange/* h2c://signal:10000 # Management reverse_proxy /api/* management:80 reverse_proxy /ws-proxy/management* management:80 reverse_proxy /management.ManagementService/* h2c://management:80 reverse_proxy /management.ProxyService/* h2c://management:80 reverse_proxy /oauth2/* management:80 # Dashboard reverse_proxy /* dashboard:80 } ``` Dockerfile.caddy ``` ARG VERSION=2 FROM caddy:${VERSION}-builder AS builder RUN xcaddy build --with github.com/mholt/caddy-l4 FROM caddy:${VERSION}-alpine COPY --from=builder /usr/bin/caddy /usr/bin/caddy ```
saavagebueno commented 2026-08-05 01:29:21 -04:00
Author
Owner
Copy Link

@shaban00 commented on GitHub (Feb 18, 2026):

@heymoe If I do a fresh install with the default traefik, the reverse proxy service works and the certificate issuing works. I am only having the certificate issue with Caddy

<!-- gh-comment-id:3922952451 --> @shaban00 commented on GitHub (Feb 18, 2026): @heymoe If I do a fresh install with the default traefik, the reverse proxy service works and the certificate issuing works. I am only having the certificate issue with Caddy
saavagebueno commented 2026-08-05 01:29:21 -04:00
Author
Owner
Copy Link

@shaban00 commented on GitHub (Feb 18, 2026):

@ben-ba You mean you are using regular Caddy and the reverse proxy is working for you? Is it possible to share how you've set it up?

<!-- gh-comment-id:3922956504 --> @shaban00 commented on GitHub (Feb 18, 2026): @ben-ba You mean you are using regular Caddy and the reverse proxy is working for you? Is it possible to share how you've set it up?
saavagebueno commented 2026-08-05 01:29:21 -04:00
Author
Owner
Copy Link

@da-wilky commented on GitHub (Feb 18, 2026):

But can you access the service behind the subdomain where the "Issuing Certificate" is running? Or which error do you have on accessing the domain?

<!-- gh-comment-id:3923124547 --> @da-wilky commented on GitHub (Feb 18, 2026): But can you access the service behind the subdomain where the "Issuing Certificate" is running? Or which error do you have on accessing the domain?
saavagebueno commented 2026-08-05 01:29:21 -04:00
Author
Owner
Copy Link

@ben-ba commented on GitHub (Feb 18, 2026):

@ben-ba You mean you are using regular Caddy and the reverse proxy is working for you? Is it possible to share how you've set it up?

No, sorry for the confusion. For the traefik installation. I read your post partly, caddy part and feature part.

<!-- gh-comment-id:3923152964 --> @ben-ba commented on GitHub (Feb 18, 2026): > @ben-ba You mean you are using regular Caddy and the reverse proxy is working for you? Is it possible to share how you've set it up? No, sorry for the confusion. For the traefik installation. I read your post partly, caddy part and feature part.
saavagebueno commented 2026-08-05 01:29:21 -04:00
Author
Owner
Copy Link

@shaban00 commented on GitHub (Feb 18, 2026):

@da-wilky When I try to access it, I get this error This site can’t be reached. I am just trying to test with grafana

Image Image Image
<!-- gh-comment-id:3923335289 --> @shaban00 commented on GitHub (Feb 18, 2026): @da-wilky When I try to access it, I get this error `This site can’t be reached`. I am just trying to test with grafana <img width="974" height="321" alt="Image" src="https://github.com/user-attachments/assets/117032e5-489b-421e-9fd0-144bcffbad72" /> <img width="1702" height="590" alt="Image" src="https://github.com/user-attachments/assets/6b0ebae1-8351-4cc8-b314-cf2a9a5d952c" /> <img width="1425" height="800" alt="Image" src="https://github.com/user-attachments/assets/2483d827-6b26-4d64-9ea0-dfdfcc0e61b6" />
saavagebueno commented 2026-08-05 01:29:21 -04:00
Author
Owner
Copy Link

@da-wilky commented on GitHub (Feb 18, 2026):

Your error is related to your netbird proxy setup. You pass NB_PROXY_TRUSTED_PROXIES=172.18.0.18, but the request is not really proxied by caddy, its just passed through without being intercepted. Remove this line from the config and it should work fine. Maybe its also an implementation error of netbird, but removing the line should fix your problem :)

<!-- gh-comment-id:3923540886 --> @da-wilky commented on GitHub (Feb 18, 2026): Your error is related to your netbird proxy setup. You pass `NB_PROXY_TRUSTED_PROXIES=172.18.0.18`, but the request is not really proxied by caddy, its just passed through without being intercepted. Remove this line from the config and it should work fine. Maybe its also an implementation error of netbird, but removing the line should fix your problem :)
saavagebueno commented 2026-08-05 01:29:21 -04:00
Author
Owner
Copy Link

@shaban00 commented on GitHub (Feb 18, 2026):

@da-wilky Removing NB_PROXY_TRUSTED_PROXIES solved the problem. Thank you

<!-- gh-comment-id:3923785929 --> @shaban00 commented on GitHub (Feb 18, 2026): @da-wilky Removing `NB_PROXY_TRUSTED_PROXIES` solved the problem. Thank you
saavagebueno commented 2026-08-05 01:29:21 -04:00
Author
Owner
Copy Link

@LowFatMom commented on GitHub (Feb 19, 2026):

So, does it use Caddy as a reverse proxy, or it only use Caddy for the SSL, and still use the Netbird's own go server as reverse proxy (wich is slower than Caddy)

<!-- gh-comment-id:3927629840 --> @LowFatMom commented on GitHub (Feb 19, 2026): So, does it use Caddy as a reverse proxy, or it only use Caddy for the SSL, and still use the Netbird's own go server as reverse proxy (wich is slower than Caddy)
saavagebueno commented 2026-08-05 01:29:21 -04:00
Author
Owner
Copy Link

@da-wilky commented on GitHub (Feb 19, 2026):

Wait, so you can use Caddy and then manage the reverse proxies in the netbird's UI ??

@LowFatMom You can use caddy to pass the defined requests to the netbird proxy and then indeed manage your services that should be exposed via netbird using its UI. This thread is just about using caddy instead of traefik for the setup. (https://docs.netbird.io/selfhosted/migration/enable-reverse-proxy)

No, you cannot replace the netbird proxy with caddy using this guide.

You still have the netbird-proxy in use. Thats the one you can configure using the web UI. This thread is not about replacing netbird proxy with caddy, its about replacing traefik with caddy (which is in front of netbird proxy).

So a request is handled by Caddy first (instead of traefik), from there Caddy can act as reverse proxy for several apps, for netbird dashboard and for netbird proxy. In case of netbird proxy domains caddy passes the tls through to netbird proxy. Then netbird proxy resolves SSL and handles the request.

<!-- gh-comment-id:3927999251 --> @da-wilky commented on GitHub (Feb 19, 2026): > > Wait, so you can use Caddy and then manage the reverse proxies in the netbird's UI ?? > > [@LowFatMom](https://github.com/LowFatMom) You can use caddy to pass the defined requests to the netbird proxy and then indeed manage your services that should be exposed via netbird using its UI. This thread is just about using caddy instead of traefik for the setup. (https://docs.netbird.io/selfhosted/migration/enable-reverse-proxy) No, you cannot replace the netbird proxy with caddy using this guide. You still have the netbird-proxy in use. Thats the one you can configure using the web UI. This thread is not about replacing netbird proxy with caddy, its about replacing traefik with caddy (which is in front of netbird proxy). So a request is handled by Caddy first (instead of traefik), from there Caddy can act as reverse proxy for several apps, for netbird dashboard and for netbird proxy. In case of netbird proxy domains caddy passes the tls through to netbird proxy. Then netbird proxy resolves SSL and handles the request.
saavagebueno commented 2026-08-05 01:29:22 -04:00
Author
Owner
Copy Link

@da-wilky commented on GitHub (Apr 29, 2026):

To fix the error that only the caddy IP is read by the netbird reverse proxy like described here #5324 the following fix should be applied to use the PROXY protocol v2. I also modify the original comment with the changes.
Without this fix the new Access Control for Reverse Proxy Service wont work correctly.

Caddyfile:

{
  admin off  # Optional, disables the admin web ui (recommended if not used)
  servers {
    listener_wrappers {
      layer4 {    # This section passes the TLS directly to the container for the specified domain (and wildcard subdomain)
        @proxy-exact tls sni proxy.domain.com
        route @proxy-exact {
          #   THIS CHANGES
          proxy {
            proxy_protocol v2
            upstream netbird-proxy:8443
          }
          #    ---------------
        } 
        @proxy-wild tls sni_regexp ^[^.]+\.proxy\.domain\.com$
        route @proxy-wild {
          #   THIS CHANGES
          proxy {
            proxy_protocol v2
            upstream netbird-proxy:8443
          }
          #    ---------------
        }
      }
      tls
    }
  }
}

proxy.env:

...
NB_PROXY_PROXY_PROTOCOL=true
<!-- gh-comment-id:4342305867 --> @da-wilky commented on GitHub (Apr 29, 2026): To fix the error that only the caddy IP is read by the netbird reverse proxy like described here #5324 the following fix should be applied to use the PROXY protocol v2. I also modify the original comment with the changes. Without this fix the new Access Control for Reverse Proxy Service wont work correctly. `Caddyfile`: ```caddy { admin off # Optional, disables the admin web ui (recommended if not used) servers { listener_wrappers { layer4 { # This section passes the TLS directly to the container for the specified domain (and wildcard subdomain) @proxy-exact tls sni proxy.domain.com route @proxy-exact { # THIS CHANGES proxy { proxy_protocol v2 upstream netbird-proxy:8443 } # --------------- } @proxy-wild tls sni_regexp ^[^.]+\.proxy\.domain\.com$ route @proxy-wild { # THIS CHANGES proxy { proxy_protocol v2 upstream netbird-proxy:8443 } # --------------- } } tls } } } ``` `proxy.env`: ```env ... NB_PROXY_PROXY_PROTOCOL=true ```
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2021 Q4
2021 Q4
2022 Q1
2022 Q1
2022 Q1
2022 Q1
2022 Q1
2022 Q1
accessibility
accessibility
accessibility
acl
acl
acl
agent
agent
agent
agent
agent
agent
Android
Android
Android
Android
Android
Android
api
api
api
authentik
authentik
authentik
automation
automation
automation
azure
azure
azure
battery-usage
battery-usage
battery-usage
bug
cache
cache
cache
client
client
client
client-ui
client-ui
client-ui
cloud
cloud
cloud
cloud-only
cloud-only
cloud-only
cloudflare
cloudflare
cloudflare
community
community
community
compatibility
compatibility
compatibility
config-idp
config-idp
config-idp
config-issue
config-issue
config-issue
connection
connection
connection
contribution
contribution
contribution
coturn
coturn
coturn
cross-vpn
cross-vpn
cross-vpn
dashboard
dashboard
dashboard
data-usage
data-usage
data-usage
distribution
distribution
distribution
dns
dns
dns
docker
docker
docker
documentation
documentation
documentation
duplicate
duplicate
duplicate
enhancement
enhancement
event-stream
event-stream
event-stream
feature-request
feature-request
feature-request
freebsd
freebsd
freebsd
getting-started
getting-started
getting-started
go
go
go
good first issue
good first issue
good first issue
gui
gui
gui
help wanted
help wanted
help wanted
home-assistant
home-assistant
home-assistant
idp
idp
idp
inconsistency
inconsistency
inconsistency
integration
integration
integration
integrations
integrations
integrations
ios
ios
ios
ipv6
ipv6
ipv6
jwt
jwt
jwt
k8s
k8s
k8s
keycloak
keycloak
keycloak
linux
linux
linux
login
login
login
macos
macos
macos
management-service
management-service
management-service
Medium
Medium
Medium
missing-docs
missing-docs
missing-docs
mobile
mobile
mobile
moved-internal
moved-internal
moved-internal
needs-review
needs-review
needs-review
netbird-ui
netbird-ui
netbird-ui
networking
networking
networking
new-platform
new-platform
new-platform
nginx
nginx
nginx
notification
notification
notification
okta
okta
okta
openwrt
openwrt
openwrt
P2
P2
P2
packaging
packaging
packaging
peer-management
peer-management
peer-management
peer-management
peer-management
peer-management
peer-management
peer-management
peer-management
performance
performance
performance
postgres
postgres
postgres
posture-checks
posture-checks
posture-checks
psk
psk
psk
pull-request
Mirrored from GitHub Pull Request
 question
question
question
refactor
refactor
refactor
relay
relay
relay
release
release
release
rfc
rfc
rfc
routes
routes
routes
security
security
security
security-improvement
security-improvement
security-improvement
security-related
security-related
security-related
self-hosting
self-hosting
self-hosting
server
server
server
signal
signal
signal
sleep-issue
sleep-issue
sleep-issue
ssh
ssh
ssh
ssl
ssl
ssl
status
status
status
store
store
store
synology
synology
synology
system-compatibility-issue
system-compatibility-issue
system-compatibility-issue
test-suite
test-suite
test-suite
third-party-integration
third-party-integration
third-party-integration
triage
triage
triage
triage
triage
triage
triage-needed
triage-needed
triage-needed
troubleshooting
troubleshooting
troubleshooting
UX
UX
UX
waiting-feedback
waiting-feedback
waiting-feedback
windows
windows
windows
wontfix
wontfix
wontfix
zitadel
zitadel
zitadel
No Label feature-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dynr-servers saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#11328
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?