@cryptotaxi247 / netdata-1 / commits / 48c05cbf3

fix proxy links in netdata security (#14613)

Chris Akritidis committed Feb 26, 2023 at 10:01 UTC 48c05cbf36bceb48ea60130c0110d398edcfbfd7
1 file changed +7 -1
docs/netdata-security.md
+7 -1
@@ -170,7 +170,13 @@ dashboard in transit. The connection to Netdata Cloud is always secured with TLS
170
171 ### Use an authenticating web server in proxy mode
172
173 -Use one web server to provide authentication in front of **all your Netdata servers**. So, you will be accessing all your Netdata with URLs like `http://{HOST}/netdata/{NETDATA_HOSTNAME}/` and authentication will be shared among all of them (you will sign-in once for all your servers). Instructions are provided on how to set the proxy configuration to have Netdata run behind [nginx](Running-behind-nginx.md), [Apache](Running-behind-apache.md), [lighttpd](Running-behind-lighttpd.md) and [Caddy](Running-behind-caddy.md).
173 +Use one web server to provide authentication in front of **all your Netdata servers**. So, you will be accessing all your Netdata with URLs like `http://{HOST}/netdata/{NETDATA_HOSTNAME}/` and authentication will be shared among all of them (you will sign-in once for all your servers). Instructions are provided on how to set the proxy configuration to have Netdata run behind
174 +[nginx](https://github.com/netdata/netdata/blob/master/docs/Running-behind-nginx.md),
175 +[HAproxy](https://github.com/netdata/netdata/blob/master/docs/Running-behind-haproxy.md),
176 +[Apache](https://github.com/netdata/netdata/blob/master/docs/Running-behind-apache.md),
177 +[lighthttpd](https://github.com/netdata/netdata/blob/master/docs/Running-behind-lighttpd.md),
178 +[caddy](https://github.com/netdata/netdata/blob/master/docs/Running-behind-caddy.md), and
179 +[H2O](https://github.com/netdata/netdata/blob/master/docs/Running-behind-h2o.md).
180
181 To use this method, you should firewall protect all your Netdata servers, so that only the web server IP will be allowed to directly access Netdata. To do this, run this on each of your servers (or use your firewall manager):
182