Pull request 164: docker-fix
Merge in GO/adguard-home-wiki from docker-fix to master Squashed commit of the following: commit 86872089f48770c8bfa59f88bbdd123b6c18ba01 Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Tue Apr 4 14:04:39 2023 +0300 Encryption: add info on host commit abeabbdafe07a9d825d2e18939f3b803c0a5e1f2 Merge: 1a10fa6 5de6748 Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Tue Apr 4 14:01:26 2023 +0300 Merge branch 'master' into docker-fix commit 1a10fa63c3a0ea752d6645809e65fb02ba39da65 Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Mon Apr 3 19:35:20 2023 +0300 all: add info on clients in docker; imp nginx
parent
5de6748790
commit
3f7b70e6b3
|
@ -95,6 +95,11 @@ Port mappings you might need:
|
||||||
* `-p 5443:5443/tcp -p 5443:5443/udp`: add if you are going to run AdGuard
|
* `-p 5443:5443/tcp -p 5443:5443/udp`: add if you are going to run AdGuard
|
||||||
Home as a [DNSCrypt] server.
|
Home as a [DNSCrypt] server.
|
||||||
|
|
||||||
|
### Client IPs
|
||||||
|
|
||||||
|
If you want AdGuardHome to see the original client IPs as opposed to something
|
||||||
|
like `172.17.0.1`, you should add `--network host` to the list of options.
|
||||||
|
|
||||||
### Control the container
|
### Control the container
|
||||||
|
|
||||||
* Start: `docker start adguardhome`
|
* Start: `docker start adguardhome`
|
||||||
|
|
|
@ -179,15 +179,20 @@ Home will receive and interpret the value of this header as real client's
|
||||||
address. The address of the reverse proxy server will be received too and also
|
address. The address of the reverse proxy server will be received too and also
|
||||||
checked against the "trusted" proxies list.
|
checked against the "trusted" proxies list.
|
||||||
|
|
||||||
|
Another header you might want to proxy is the `Host` header, which is required
|
||||||
|
to make AdGuard Home recognize requests from clients that have a ClientID in
|
||||||
|
their hostnames.
|
||||||
|
|
||||||
For example, if the configuration of the reverse proxy server contains the
|
For example, if the configuration of the reverse proxy server contains the
|
||||||
following directives:
|
following directives:
|
||||||
|
|
||||||
```none
|
```none
|
||||||
location /dns-query {
|
location /dns-query {
|
||||||
...
|
# …
|
||||||
|
proxy_set_header Host $host;
|
||||||
proxy_set_header X-Real-IP '1.2.3.4';
|
proxy_set_header X-Real-IP '1.2.3.4';
|
||||||
proxy_bind 192.168.1.2;
|
proxy_bind 192.168.1.2;
|
||||||
...
|
# …
|
||||||
}
|
}
|
||||||
```
|
```
|
||||||
|
|
||||||
|
|
3
FAQ.md
3
FAQ.md
|
@ -348,9 +348,10 @@ configuration for your web server:
|
||||||
|
|
||||||
```none
|
```none
|
||||||
location /aghome/ {
|
location /aghome/ {
|
||||||
|
proxy_cookie_path / /aghome/;
|
||||||
proxy_pass http://AGH_IP:AGH_PORT/;
|
proxy_pass http://AGH_IP:AGH_PORT/;
|
||||||
proxy_redirect / /aghome/;
|
proxy_redirect / /aghome/;
|
||||||
proxy_cookie_path / /aghome/;
|
proxy_set_header Host $host;
|
||||||
}
|
}
|
||||||
```
|
```
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue