Use own caddy as reverse proxy
Self-Host
Hello, I'm using netbird selfhosted with an already existing caddy on my host. I removed the caddy container from the docker compose and then set my ports for each container (dashboard, signal, relay, management and zitadel). Then simply reversed all the incoming incoming to the docker from host caddy. Its working but its incredibly slow... How can I solve this?
/etc/caddy/Caddyfile
/etc/caddy/Caddyfile
vpn.abc.dev {
tls /etc/ssl/abc.dev/fullchain.pem /etc/ssl/abc.dev/key.pem
import security_headers
reverse_proxy /relay* localhost:9023
reverse_proxy /signalexchange.SignalExchange/* h2c://localhost:9021
reverse_proxy /ws-proxy/signal/* localhost:9021
reverse_proxy /management.ManagementService/* h2c://localhost:9022
reverse_proxy /ws-proxy/management/* localhost:9022
reverse_proxy /api/* localhost:9022
reverse_proxy /zitadel.admin.v1.AdminService/* h2c://localhost:9019
reverse_proxy /admin/v1/* h2c://localhost:9019
reverse_proxy /zitadel.auth.v1.AuthService/* h2c://localhost:9019
reverse_proxy /auth/v1/* h2c://localhost:9019
reverse_proxy /zitadel.management.v1.ManagementService/* h2c://localhost:9019
reverse_proxy /management/v1/* h2c://localhost:9019
reverse_proxy /zitadel.system.v1.SystemService/* h2c://localhost:9019
reverse_proxy /system/v1/* h2c://localhost:9019
reverse_proxy /assets/v1/* h2c://localhost:9019
reverse_proxy /ui/* h2c://localhost:9019
reverse_proxy /oidc/v1/* h2c://localhost:9019
reverse_proxy /saml/v2/* h2c://localhost:9019
reverse_proxy /oauth/v2/* h2c://localhost:9019
reverse_proxy /.well-known/openid-configuration h2c://localhost:9019
reverse_proxy /openapi/* h2c://localhost:9019
reverse_proxy /debug/* h2c://localhost:9019
reverse_proxy /device/* h2c://localhost:9019
reverse_proxy /device h2c://localhost:9019
reverse_proxy /zitadel.user.v2.UserService/* h2c://localhost:9019
reverse_proxy /* localhost:9020
}vpn.abc.dev {
tls /etc/ssl/abc.dev/fullchain.pem /etc/ssl/abc.dev/key.pem
import security_headers
reverse_proxy /relay* localhost:9023
reverse_proxy /signalexchange.SignalExchange/* h2c://localhost:9021
reverse_proxy /ws-proxy/signal/* localhost:9021
reverse_proxy /management.ManagementService/* h2c://localhost:9022
reverse_proxy /ws-proxy/management/* localhost:9022
reverse_proxy /api/* localhost:9022
reverse_proxy /zitadel.admin.v1.AdminService/* h2c://localhost:9019
reverse_proxy /admin/v1/* h2c://localhost:9019
reverse_proxy /zitadel.auth.v1.AuthService/* h2c://localhost:9019
reverse_proxy /auth/v1/* h2c://localhost:9019
reverse_proxy /zitadel.management.v1.ManagementService/* h2c://localhost:9019
reverse_proxy /management/v1/* h2c://localhost:9019
reverse_proxy /zitadel.system.v1.SystemService/* h2c://localhost:9019
reverse_proxy /system/v1/* h2c://localhost:9019
reverse_proxy /assets/v1/* h2c://localhost:9019
reverse_proxy /ui/* h2c://localhost:9019
reverse_proxy /oidc/v1/* h2c://localhost:9019
reverse_proxy /saml/v2/* h2c://localhost:9019
reverse_proxy /oauth/v2/* h2c://localhost:9019
reverse_proxy /.well-known/openid-configuration h2c://localhost:9019
reverse_proxy /openapi/* h2c://localhost:9019
reverse_proxy /debug/* h2c://localhost:9019
reverse_proxy /device/* h2c://localhost:9019
reverse_proxy /device h2c://localhost:9019
reverse_proxy /zitadel.user.v2.UserService/* h2c://localhost:9019
reverse_proxy /* localhost:9020
}Dive into Netbird with the unofficial Netbird community! Homelab and & Enterpise unite to share tips, troubleshoot, and assist withthe usage and/or deployment of Netbird. We're a community with shared intests, and we'd love to welcome you onto the server!
203Members
Resources
Similar Threads
Was this page helpful?
