Gitlab EE doesnt work after 10.2 update

Summary

Just updated my Omnibus Gitlab EE installation to 10.2.0 from 10.1.3 and Gitlab doesnt respond anymore. gitlab-ctl statussays everything is ok but API access checks fail in gitlab-rake gitlab:check SANITIZE=true

Results of GitLab environment info

Expand for output related to GitLab environment info

System information
System:		Debian 8.9
Proxy:		no
Current User:	git
Using RVM:	no
Ruby Version:	2.3.5p376
Gem Version:	2.6.13
Bundler Version:1.13.7
Rake Version:	12.1.0
Redis Version:	3.2.5
Git Version:	2.13.6
Sidekiq Version:5.0.4
Go Version:	unknown
GitLab information
Version:	10.2.0-ee
Revision:	cb1866d
Directory:	/opt/gitlab/embedded/service/gitlab-rails
DB Adapter:	postgresql
DB Version:	9.6.5
URL:		https://git.worldia.com
HTTP Clone URL:	https://git.worldia.com/some-group/some-project.git
SSH Clone URL:	git@git.worldia.com:some-group/some-project.git
Elasticsearch:	no
Geo:		no
Using LDAP:	yes
Using Omniauth:	yes
Omniauth Providers: google_oauth2, saml
GitLab Shell
Version:	5.9.4
Repository storage paths:

• default: /mnt/disks/storage/git-data/repositories Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks Git: /opt/gitlab/embedded/bin/git

Results of GitLab application Check

Expand for output related to the GitLab application check

Checking GitLab Shell ...
GitLab Shell version >= 5.9.4 ? ... OK (5.9.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: ...
59/2 ... ok
7/3 ... ok
7/4 ... ok
7/5 ... ok
5/8 ... ok
5/9 ... ok
5/10 ... ok
5/11 ... ok
7/12 ... ok
5/15 ... ok
5/16 ... ok
5/17 ... ok
5/18 ... ok
60/19 ... ok
10/20 ... ok
5/21 ... ok
5/22 ... ok
48/23 ... ok
5/24 ... ok
5/26 ... ok
5/28 ... ok
5/29 ... ok
5/30 ... ok
5/31 ... ok
5/32 ... ok
5/33 ... ok
5/34 ... ok
60/35 ... ok
60/36 ... ok
59/38 ... ok
59/39 ... ok
59/40 ... ok
5/41 ... ok
5/42 ... ok
59/43 ... ok
2/45 ... ok
5/46 ... ok
5/49 ... ok
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: FAILED: Failed to connect to internal API
gitlab-shell self-check failed
Try fixing it:
Make sure GitLab is running;
Check the gitlab-shell configuration file:
sudo -u git -H editor /opt/gitlab/embedded/service/gitlab-shell/config.yml
Please fix the error above and rerun the checks.
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes
Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Checking Reply by email ...
IMAP server credentials are correct? ... yes
Init.d configured correctly? ... skipped
MailRoom running? ... skipped
Checking Reply by email ... Finished
Checking LDAP ...
Server: ldapmain
LDAP authentication... Success
LDAP users with access to your GitLab server (only showing the first 100 results)
[EDITED: Bunch of LDAP users list]
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: ...
59/2 ... yes
7/3 ... yes
7/4 ... yes
7/5 ... yes
5/8 ... yes
5/9 ... yes
5/10 ... yes
5/11 ... yes
7/12 ... yes
5/15 ... yes
5/16 ... yes
5/17 ... yes
5/18 ... yes
60/19 ... yes
10/20 ... yes
5/21 ... yes
5/22 ... yes
48/23 ... yes
5/24 ... yes
5/26 ... yes
5/28 ... yes
5/29 ... yes
5/30 ... yes
5/31 ... yes
5/32 ... yes
5/33 ... yes
5/34 ... yes
60/35 ... yes
60/36 ... yes
59/38 ... yes
59/39 ... yes
59/40 ... yes
5/41 ... yes
5/42 ... yes
59/43 ... yes
2/45 ... yes
5/46 ... yes
5/49 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.5 ? ... yes (2.3.5)
Git version >= 2.7.3 ? ... yes (2.13.6)
Git user has default SSH configuration? ... yes
Active users: ... 41
Elasticsearch version 5.1 - 5.5? ... skipped (elasticsearch is disabled)
Checking GitLab ... Finished

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)