Gitlab::Auth::TooManyIps

We have a user when running a pipeline there account seems to get blocked/locked.
In the logs we see:

Gitlab::Auth::TooManyIps (User 16 from IP:XXXXXXXX tried logging from too many ips: 4):
      lib/gitlab/auth/unique_ips_limiter.rb:12:in `limit_user_id!'
      lib/gitlab/auth/unique_ips_limiter.rb:18:in `limit_user!'
      config/initializers/warden.rb:3:in `block (2 levels) in <top (required)>'
      lib/gitlab/auth/user_auth_finders.rb:25:in `find_user_from_warden'
      lib/gitlab/auth/request_authenticator.rb:15:in `user'
      config/initializers/rack_attack_global.rb:51:in `authenticated_user_id'
      config/initializers/rack_attack_global.rb:47:in `unauthenticated?'
      config/initializers/rack_attack_global.rb:28:in `block in <class:Attack>'
      lib/gitlab/middleware/read_only/controller.rb:38:in `call'
      lib/gitlab/middleware/read_only.rb:16:in `call'
      lib/gitlab/middleware/basic_health_check.rb:25:in `call'
      lib/gitlab/request_context.rb:18:in `call'
      lib/gitlab/metrics/requests_rack_middleware.rb:27:in `call'
      lib/gitlab/middleware/release_env.rb:10:in `call'

In /etc/gitlab/gitlab.rb I have set the following value in the hopes of solving the issue:
gitlab_rails[‘rack_attack_git_basic_auth’] = {
‘enabled’ => false,
}

This had no effect. Any other thoughts as to how we can prevent this from happening? The system is internal so access attacks from outside the network are not a concern.