mirror of
https://github.com/fleetdm/fleet
synced 2026-05-22 08:28:52 +00:00
637430f442
Fixing typos - replacing capital case with lower case. Removed all the checklist because it doesn't apply to changes in the documentation.... ... ... Co-authored-by: Mike McNeil <mikermcneil@users.noreply.github.com> Co-authored-by: Sampfluger88 <108141731+Sampfluger88@users.noreply.github.com>
19 lines
969 B
Markdown
19 lines
969 B
Markdown
# Using a proxy
|
|
|
|
If you are in an enterprise environment where Fleet is behind a proxy and you would like to be able to retrieve vulnerability data for [vulnerability processing](https://fleetdm.com/docs/using-fleet/vulnerability-processing#vulnerability-processing), it may be necessary to configure the proxy settings. Fleet automatically uses the `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY` environment variables.
|
|
|
|
For example, to configure the proxy in a systemd service file:
|
|
|
|
```systemd
|
|
[Service]
|
|
Environment="HTTP_PROXY=http(s)://PROXY_URL:PORT/"
|
|
Environment="HTTPS_PROXY=http(s)://PROXY_URL:PORT/"
|
|
Environment="NO_PROXY=localhost,127.0.0.1,::1"
|
|
```
|
|
|
|
After modifying the configuration you will need to reload and restart the Fleet service, as explained above.
|
|
|
|
<meta name="title" value="Proxies">
|
|
<meta name="pageOrderInSection" value="800">
|
|
<meta name="description" value="Learn how to configure proxy settings for Fleet.">
|
|
<meta name="navSection" value="TBD">
|