pull/35/head
DoTheEvo 1 year ago
parent 3da006624c
commit 2b028aa1b4

@ -390,14 +390,14 @@ network be allowed through?<br>
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.<br>
* *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

Loading…
Cancel
Save