* update FAQ

Squashed commit of the following:

commit c1fac87e93a7cdcc6079d3f608f775132b68c9e0
Author: Simon Zolin <s.zolin@adguard.com>
Date:   Tue Jul 14 16:56:19 2020 +0300

    * update FAQ
Simon Zolin 2020-07-15 12:12:14 +03:00
parent d9cc9c720e
commit cd10068ab5
1 changed files with 25 additions and 0 deletions

25
FAQ.md

@ -6,6 +6,7 @@
* [How to configure AdGuard Home to run together with pixelsrv-tls?](#q2) * [How to configure AdGuard Home to run together with pixelsrv-tls?](#q2)
* [Are there any known limitations?](#q3) * [Are there any known limitations?](#q3)
* [Why am I getting "bind: address already in use" error when trying to install on Ubuntu?](#q4) * [Why am I getting "bind: address already in use" error when trying to install on Ubuntu?](#q4)
* [How to configure a reverse proxy server for AdGuard Home?](#q5)
## Answers: ## Answers:
@ -81,3 +82,27 @@ Activate another resolv.conf file:
Stop DNSStubListener: Stop DNSStubListener:
systemctl reload-or-restart systemd-resolved systemctl reload-or-restart systemd-resolved
<a id="q5"></a>
### How to configure a reverse proxy server for AdGuard Home?
If you're running a web server already and you want to access AdGuard Home dashboard UI from an URL like `http://YOUR_SERVER/aghome/` you can use this configuration for your web server:
#### nginx
location /aghome/ {
proxy_pass http://AGH_IP:AGH_PORT/;
proxy_redirect / /aghome/;
proxy_cookie_path / /aghome/;
}
#### caddy
:80/aghome/* {
route {
uri strip_prefix /aghome
reverse_proxy AGH_IP:AGH_PORT
}
}