2022-07-23 23:45:48 +05:30
---
stage: Data Stores
2022-08-27 11:52:29 +05:30
group: Application Performance
2022-11-25 23:54:43 +05:30
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
2022-07-23 23:45:48 +05:30
---
# IP whitelist **(FREE SELF)**
GitLab provides some [monitoring endpoints ](../../user/admin_area/monitoring/health_check.md )
that provide health check information when probed.
To control access to those endpoints via IP whitelisting, you can add single
hosts or use IP ranges:
2022-11-25 23:54:43 +05:30
**Omnibus**
2022-07-23 23:45:48 +05:30
1. Open `/etc/gitlab/gitlab.rb` and add or uncomment the following:
```ruby
gitlab_rails['monitoring_whitelist'] = ['127.0.0.0/8', '192.168.0.1']
```
1. Save the file and [reconfigure ](../restart_gitlab.md#omnibus-gitlab-reconfigure ) GitLab for the changes to take effect.
---
2022-11-25 23:54:43 +05:30
**Helm chart**
2022-07-23 23:45:48 +05:30
You can set the required IPs under the `gitlab.webservice.monitoring.ipWhitelist` key. For example:
```yaml
gitlab:
webservice:
monitoring:
# Monitoring IP whitelist
ipWhitelist:
- 0.0.0.0/0 # Default
```
---
2022-11-25 23:54:43 +05:30
**Source**
2022-07-23 23:45:48 +05:30
1. Edit `config/gitlab.yml` :
```yaml
monitoring:
# by default only local IPs are allowed to access monitoring resources
ip_whitelist:
- 127.0.0.0/8
- 192.168.0.1
```
1. Save the file and [restart ](../restart_gitlab.md#installations-from-source ) GitLab for the changes to take effect.
