Gitlab Admin Area Refuses to Connect

Problem to solve

Cannot access admin area in self-hosted 16.10. I renewed the GPG key, reconfigured and restarted gitlab and downloaded new version, nothing helped. The “/admin/” is the site that refuses to connect.

Steps to reproduce

Click on “Admin Area” and 127.0.0.1 refused to connect comes up.

Versions

Please select whether options apply, and add the version information.

  • [* ] Self-managed
    16.10.0

Output:

sudo gitlab-rake gitlab:env:info && sudo gitlab-rake gitlab:check SANITIZE=true

System information
System: Ubuntu 20.04
Current User: git
Using RVM: no
Ruby Version: 3.1.4p223
Gem Version: 3.5.6
Bundler Version:2.5.6
Rake Version: 13.0.6
Redis Version: 7.0.15
Sidekiq Version:7.1.6
Go Version: go1.13.8 linux/amd64

GitLab information
Version: 16.10.0
Revision: ee32b9a6f7f
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: PostgreSQL
DB Version: 13.13
Using LDAP: no
Using Omniauth: yes
Omniauth Providers:

GitLab Shell
Version: 14.34.0
Repository storages:

  • default: unix:/var/opt/gitlab/gitaly/gitaly.socket
    GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell

Gitaly

  • default Address: unix:/var/opt/gitlab/gitaly/gitaly.socket
  • default Version: 16.10.0
  • default Git Version: 2.43.0
    Checking GitLab subtasks …

Checking GitLab Shell …

GitLab Shell: … GitLab Shell version >= 14.34.0 ? … OK (14.34.0)
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Internal API available: OK
Redis available via internal API: OK
gitlab-shell self-check successful

Checking GitLab Shell … Finished

Checking Gitaly …

Gitaly: … default … OK

Checking Gitaly … Finished

Checking Sidekiq …

Sidekiq: … Running? … yes
Number of Sidekiq processes (cluster/worker) … 1/1

Checking Sidekiq … Finished

Checking Incoming Email …

Incoming Email: … Reply by email is disabled in config/gitlab.yml

Checking Incoming Email … Finished

Checking LDAP …

LDAP: … LDAP is disabled in config/gitlab.yml

Checking LDAP … Finished

Checking GitLab App …

Database config exists? … yes
Tables are truncated? … skipped
All migrations up? … yes
Database contains orphaned GroupMembers? … no
GitLab config exists? … yes
GitLab config up to date? … yes
Cable config exists? … yes
Resque config exists? … 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
Systemd unit files or init script exist? … skipped (omnibus-gitlab has neither init script nor systemd units)
Systemd unit files or init script up-to-date? … skipped (omnibus-gitlab has neither init script nor systemd units)
Projects have namespace: …
6/1 … yes
6/3 … yes
6/4 … yes
6/5 … yes
9/6 … yes
2/8 … yes
6/10 … yes
6/11 … yes
9/12 … yes
6/13 … yes
6/14 … yes
20/15 … yes
6/16 … yes
9/17 … yes
3/18 … yes
6/19 … yes
6/20 … yes
6/21 … yes
6/22 … yes
3/23 … yes
33/24 … yes
3/26 … yes
23/27 … yes
9/28 … yes
9/30 … yes
34/31 … yes
6/32 … yes
34/33 … yes
9/34 … yes
6/36 … yes
6/37 … yes
6/38 … yes
6/39 … yes
9/40 … yes
9/41 … yes
6/42 … yes
9/43 … yes
5/44 … yes
34/45 … yes
6/46 … yes
36/47 … yes
6/48 … yes
6/49 … yes
34/51 … yes
47/52 … yes
6/53 … yes
36/54 … yes
6/55 … yes
49/56 … yes
9/57 … yes
6/58 … yes
6/59 … yes
6/60 … yes
6/61 … yes
6/62 … yes
6/63 … yes
48/65 … yes
48/67 … yes
48/69 … yes
48/71 … yes
48/72 … yes
48/73 … yes
Redis version >= 6.2.14? … yes
Ruby version >= 3.0.6 ? … yes (3.1.4)
Git user has default SSH configuration? … yes
Active users: … 47
Is authorized keys file accessible? … yes
GitLab configured to store new projects in hashed storage? … yes
All projects are in hashed storage? … yes

Checking GitLab App … Finished

Checking GitLab subtasks … Finished