From 2b028aa1b4f326d1d06509bae614422cc4e52901 Mon Sep 17 00:00:00 2001 From: DoTheEvo Date: Tue, 23 May 2023 20:23:57 +0200 Subject: [PATCH] update --- caddy_v2/readme.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/caddy_v2/readme.md b/caddy_v2/readme.md index 57f3438..c350ed4 100644 --- a/caddy_v2/readme.md +++ b/caddy_v2/readme.md @@ -390,14 +390,14 @@ 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 +* *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 + instead of hairpin/NATreflection. -* *note:* a shortuc `private_ranges` can be used, instead of specific range +* *Note:* A shortcut `private_ranges` can be used, instead of specific range. Named matchers are defined by `@` and can be named whatever you like. @@ -556,7 +556,7 @@ The drawback is a potential security issue, since you are creating a token that allows full control over your domain's DNS. You store this token somewhere, you are giving it to some application from dockerhub... -*note:* caddy uses a new [libdns](https://github.com/libdns/libdns/) +*Note:* caddy uses a new [libdns](https://github.com/libdns/libdns/) golang library with [cloudflare package](https://github.com/libdns/cloudflare) ### - Create API token on Cloudflare