From 2e316c7821fa031ea36f54355ed8e55e4df285be Mon Sep 17 00:00:00 2001 From: DoTheEvo Date: Sat, 1 Apr 2023 01:36:59 +0200 Subject: [PATCH] update --- caddy_v2/readme.md | 44 ++++++++++++++++++++++---------------------- 1 file changed, 22 insertions(+), 22 deletions(-) diff --git a/caddy_v2/readme.md b/caddy_v2/readme.md index 41633cb..105fd2a 100644 --- a/caddy_v2/readme.md +++ b/caddy_v2/readme.md @@ -351,6 +351,28 @@ nextcloud.{$MY_DOMAIN} { } ``` +### Backend communication + +Some containers might be set to communicate only through https 443 port. +But since they are behind proxy, their certificates wont be singed, wont be trusted. + +Caddies sub-directive `transport` sets how to communicate with the backend.
+Setting the upstream's scheme to `https://` +or declaring the `tls` transport subdirective makes it use https. +Setting `tls_insecure_skip_verify` makes Caddy ignore errors due to +untrusted certificates coming from the backend. + +``` +whatever.{$MY_DOMAIN} { + reverse_proxy https://server-blue:443 { + transport http { + tls + tls_insecure_skip_verify + } + } +} +``` + ### Named matchers and IP filtering Caddy has [matchers](https://caddyserver.com/docs/caddyfile/matchers)
@@ -428,28 +450,6 @@ b.{$MY_DOMAIN} { } ``` -### Backend communication - -Some containers might be set to communicate only through https 443 port. -But since they are behind proxy, their certificates wont be singed, wont be trusted. - -Caddies sub-directive `transport` sets how to communicate with the backend.
-Setting the upstream's scheme to `https://` -or declaring the `tls` transport subdirective makes it use https. -Setting `tls_insecure_skip_verify` makes Caddy ignore errors due to -untrusted certificates coming from the backend. - -``` -whatever.{$MY_DOMAIN} { - reverse_proxy https://server-blue:443 { - transport http { - tls - tls_insecure_skip_verify - } - } -} -``` - ### Headers and gzip This example is with vaultwarden password manager, which comes with its reverse proxy