Discharge7443/fleet
1
0
Fork 0
Code Issues Pull Requests Actions 5 Packages Projects Releases Wiki Activity

Update fleet-server-configuration.md adding allow_private_network (#50422)

Browse Source 
Adds the `server_allow_private_network_integrations` flag information

For #49727

---------

Co-authored-by: Rachael Shaw <r@rachael.wtf>
This commit is contained in:
Gray Williams
2026-08-04 11:54:18 -05:00
committed by GitHub
co-authored by Rachael Shaw
parent e35e30751c
commit be48a82d16
1 changed files with 14 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/Configuration/fleet-server-configuration.md
+14
View File
@@ -801,6 +801,20 @@ Setting to true will disable the origin check.
websockets_allow_unsafe_origin: true
```
### server_allow_private_network_integrations
Allows Fleet's HTTP client to make outbound requests to RFC 1918 and other private network addresses. Enable this if Fleet needs to reach an integration over HTTP. (Examples include SSO/IdP, EJBCA, Jira, or SCEP server, or an `HTTP_PROXY`/`HTTPS_PROXY` hosted on a private network.)
This does not affect the always-blocked loopback (`127.0.0.0/8`) and cloud metadata (`169.254.0.0/16`) ranges.
- Default value: `false`
- Environment variable: `FLEET_SERVER_ALLOW_PRIVATE_NETWORK_INTEGRATIONS`
- Config file format:
```yaml
server:
allow_private_network_integrations: true
```
### server_force_h2c
Setting this will force the Go webserver to attempt HTTP2. By default, HTTP2 support is only negotiated if the Go webserver