From 534ee211f34ea13b0951358aece3ee836954982f Mon Sep 17 00:00:00 2001 From: DoTheEvo Date: Tue, 23 May 2023 16:17:14 +0200 Subject: [PATCH] update --- caddy_v2/readme.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/caddy_v2/readme.md b/caddy_v2/readme.md index 105fd2a..805041b 100644 --- a/caddy_v2/readme.md +++ b/caddy_v2/readme.md @@ -390,6 +390,13 @@ network be allowed through?
Well, the [remote_ip](https://caddyserver.com/docs/caddyfile/matchers#remote-ip) matcher comes to play, which enables you to filter requests by their IP.
+* *note* - if your router uses hairpin/NATreflection to get around + [the issue](https://github.com/DoTheEvo/selfhosted-apps-docker/tree/master/caddy_v2#editing-hosts-file) + of accessing locally hosted stuff from LAN side by the hostname, + then this will block LAN side too. As remote_ip will be your public ip. + Local DNS server is needed, with records sending traffic to docker host + instead of hairpin/NATreflection + Named matchers are defined by `@` and can be named whatever you like. ```