Update README.md
Costa Tsaousis committed
Feb 28, 2025 at 13:51 UTC
6fd6603e9d27931b2fee672295dff341de74f114
1 file changed
+2
-2
src/claim/README.md
+2
-2
@@ -60,11 +60,11 @@ The `proxy` option at the `[global]` section in `claim.conf` can be set to:
60
- `none` to disable proxy configuration.
61
- `env` to use the environment variable `http_proxy` (this is the default).
62
- `http://[user:pass@]host:port`, to connect via a web proxy.
63
-- `socks5[h]://[user:pass@]host:port`, to connect via a SOCKS5 or SOCKS5h proxy.
63
+- `socks5[h]://[user:pass@]host:port`, to connect via a SOCKS5 proxy.
64
65
The `http_proxy` environment variable is used only when the `proxy` option is set to `env` (which is the default). The `http_proxy` environment can be:
66
67
-- `http://[user:pass@]host:port`, to connect via an HTTP or HTTPS proxy.
67
+- `http://[user:pass@]host:port`, to connect via an HTTP proxy.
68
- `socks5[h]://[user:pass@]host:port`, to connect via a SOCKS5 or SOCKS5h proxy.
69
70
**NOTE**: Netdata does not currently support secure connections to proxies. So, while the connection from the proxy to Netdata Cloud is always encrypted and secure, the connection from the Netdata Agent to the proxy is always unencrypted. Keep in mind that there are 2 distinct connection libraries involved. Claiming uses libcurl which may be more flexible, but later at the establishment of the actual Netdata Cloud connection a different library implements MQTT over WebSockets over HTTPS (MQTToWSoHTTPS) and unfortunately this library does not currently support secure connections to proxies. So, while claiming may work via a secure connection to a proxy (libcurl), the actual Netdata Cloud connection will later fail if the proxy connection is secure (MQTToWSoHTTPS). The proxy configuration patterns described above, work for both libraries.