health check via whitelist_ip not working according to docs

Summary

When I whitelist an ip (10.10.0.0/16) in gitlab-ce (omnibus) v11.0.4 Im unable to curl the metrics from https://gitlab.mydomain.net/-/readiness I get a 404 error. However if I use the token which is supposed to be deprecated it does work: curl https://gitlab.mydomain.net/-/readiness?token=MdXoSsGxX6oduEvXsyxz

Steps to reproduce

From another machine that is on the same network in the whitelisted cidr I do: curl https://gitlab.mydomain.net/-/readiness and get a 404 error

From the same machine I add the token and successfully see my metrics: curl https://gitlab.mydomain.net/-/readiness?token=MdXoSsGxX6oduEvXsyxz

The entry in gitlab.rb looks like this: gitlab_rails['monitoring_whitelist'] = ['192.168.0.0/16', '10.10.0.0/16', '100.100.0.0/16', '200.200.0.0/16']

The ip of the test machine is: 10.10.11.167 The ip of the gitlab server is: 10.10.11.42

What is the current bug behavior?

Results are not what is expected based on documentation.

What is the expected correct behavior?

According to the docs here: https://docs.gitlab.com/ce/user/admin_area/monitoring/health_check.html I should see my metrics if the correct ip/cidr is entered in the gitlab.rb file in /etc/gitlab/ as whitelisted and then I do curl https://gitlab.mydomain.net/-/readiness

Results of GitLab environment info

gitlab-rake gitlab:env:info

System information
System:		Ubuntu 16.04
Current User:	git
Using RVM:	no
Ruby Version:	2.4.4p296
Gem Version:	2.7.6
Bundler Version:1.16.2
Rake Version:	12.3.1
Redis Version:	3.2.11
Git Version:	2.17.1
Sidekiq Version:5.1.3
Go Version:	unknown

GitLab information
Version:	11.0.4
Revision:	edb037c
Directory:	/opt/gitlab/embedded/service/gitlab-rails
DB Adapter:	postgresql
URL:		https://gitlab.mydomain.net
HTTP Clone URL:	https://gitlab.mydomain.net/some-group/some-project.git
SSH Clone URL:	git@gitlab.mydomain.net:some-group/some-project.git
Using LDAP:	no
Using Omniauth:	no

GitLab Shell
Version:	7.1.4
Repository storage paths:
- default: 	/var/opt/gitlab/git-data/repositories
Hooks:		/opt/gitlab/embedded/service/gitlab-shell/hooks
Git:		/opt/gitlab/embedded/bin/git

Results of GitLab application Check

gitlab-rake gitlab:check SANITIZE=true
Checking GitLab Shell ...

GitLab Shell version >= 7.1.4 ? ... OK (7.1.4)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:root, or git:git?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ...
3/5 ... ok
2/6 ... ok
3/8 ... ok
3/9 ... repository is empty
3/10 ... ok
3/11 ... ok
2/12 ... ok
3/15 ... ok
3/16 ... ok
3/17 ... ok
3/20 ... ok
14/23 ... ok
14/24 ... ok
14/25 ... ok
3/26 ... ok
14/28 ... repository is empty
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Redis available via internal API: OK

Access to /var/opt/gitlab/.ssh/authorized_keys: OK
gitlab-shell self-check successful

Checking GitLab Shell ... Finished

Checking Sidekiq ...

Running? ... yes
Number of Sidekiq processes ... 1

Checking Sidekiq ... Finished

Reply by email is disabled in config/gitlab.yml
Checking LDAP ...

LDAP is disabled in config/gitlab.yml

Checking LDAP ... Finished

Checking GitLab ...

Git configured correctly? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory exists? ... yes
Uploads directory has correct permissions? ... yes
Uploads directory tmp has correct permissions? ... yes
Init script exists? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
Projects have namespace: ...
3/5 ... yes
2/6 ... yes
3/8 ... yes
3/9 ... yes
3/10 ... yes
3/11 ... yes
2/12 ... yes
3/15 ... yes
3/16 ... yes
3/17 ... yes
3/20 ... yes
14/23 ... yes
14/24 ... yes
14/25 ... yes
3/26 ... yes
14/28 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.5 ? ... yes (2.4.4)
Git version >= 2.9.5 ? ... yes (2.17.1)
Git user has default SSH configuration? ... yes
Active users: ... 9

Checking GitLab ... Finished

Actual question...

Which way should be working for the version that I am on?