[v9.4.x] Give more detail and context on http_addr in grafana.ini (#65644)

Give more detail and context on http_addr in grafana.ini (#65187) * Give more detail and context on http_addr in grafana.ini This particular configuration item is misleadingly named (it's about networking addresses rather than HTTP) and there are a bunch of ways users can misread, misconfigure, and create a situation where grafana won't start due to a bind error. I'm trying to outline a couple of extra things about what this covers and provide good default advice, leaving room for specialists who know what they're doing to still use this, with more clarity. * Update _index.md * Apply suggestions from code review Co-authored-by: Christopher Moyer <35463610+chri2547@users.noreply.github.com> * Update _index.md removed recommendation note about http_addr * makes prettier --------- Co-authored-by: Christopher Moyer <35463610+chri2547@users.noreply.github.com> Co-authored-by: Chris Moyer <chris.moyer@grafana.com> (cherry picked from commit 765073a776) Co-authored-by: David Allen <david.allen@grafana.com>
2023-03-30 12:34:10 -05:00
parent 76c3e1863b
commit fc6b8f9c6c
1 changed files with 3 additions and 1 deletions
@@ -191,7 +191,9 @@ Folder that contains [provisioning]({{< relref "../../administration/provisionin

 ### http_addr

-The IP address to bind to. If empty will bind to all interfaces
+The host for the server to listen on. If your machine has more than one network interface, you can use this setting to expose the Grafana service on only one network interface and not have it available on others, such as the loopback interface. An empty value is equivalent to setting the value to `0.0.0.0`, which means the Grafana service binds to all interfaces.
+
+In environments where network address translation (NAT) is used, ensure you use the network interface address and not a final public address; otherwise, you might see errors such as `bind: cannot assign requested address` in the logs.

 ### http_port