After upgrading to v18.3 Puma is returning 502

Summary

I'm using the gitlab/gitlab-ce image. After the update to v18.3 I was no longer able to access my instance, as it was returning a 502 error. Looking at the logs I see the following messages when accessing my gitlab instance:

    web_1  | ==> /var/log/gitlab/puma/puma_stderr.log <==
    web_1  | 2025-08-25 14:37:26 +0000 Rack app (“GET /” - (xxx,  xxx)): #<NoMethodError: undefined method `include?’ for nil:NilClass>
    web_1  | Error reached top of thread-pool: stack level too deep (SystemStackError)
    web_1  |
    web_1  | ==> /var/log/gitlab/gitlab-workhorse/current <==
    web_1  | {“correlation_id”:“01K3GTK7G03Q4VK7QT67EX7EAE”,“duration_ms”:44,“error”:“badgateway: failed to receive response: EOF”,“level”:“error”,“method”:“GET”,“msg”:“”,“time”:“2025-08-25T14:37:26Z”,“uri”:“/”}
    web_1  | {“backend_id”:“rails”,“body_limit”:104857600,“content_type”:“text/html; charset=utf-8”,“correlation_id”:“01K3GTK7G03Q4VK7QT67EX7EAE”,“duration_ms”:44,“host”:“xxx”,“level”:“info”,“method”:“GET”,“msg”:“access”,“proto”:“HTTP/1.1”,“read_bytes”:983,“referrer”:“”,“remote_addr”:“[xxx]:48670”,“remote_ip”:“xxx”,“route”:“”,“route_id”:“default”,“status”:502,“system”:“http”,“time”:“2025-08-25T14:37:26Z”,“ttfb_ms”:44,“uri”:“/”,“user_agent”:“Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:141.0) Gecko/20100101 Firefox/141.0”,“written_bytes”:2026}

Not entirely sure how to debug this. For now downgrading to gitlab-ce:18.2.4-ce.0 image seems to work.

Steps to reproduce

Here's my docker-compose with all of the identifying information stripped out (no additional gitlab.rb file is used):

version: '2.3'
services:
  web:
    mem_limit: 8g
    cpus: 8.00
    image: 'gitlab/gitlab-ce:latest'
    restart: always
    environment:
      GITLAB_OMNIBUS_CONFIG: |
        external_url 'https://xxx'
        gitlab_rails['time_zone'] = 'EET'
        gitlab_rails['gitlab_email_enabled'] = true
        gitlab_rails['gitlab_email_from'] = 'xxx@xxx'
        gitlab_rails['gitlab_email_display_name'] = 'xxx'
        gitlab_rails['gitlab_email_reply_to'] = 'xxx'
        gitlab_rails['gitlab_username_changing_enabled'] = false
        gitlab_rails['gitlab_default_projects_features_merge_requests'] = true
        gitlab_rails['gitlab_default_projects_features_wiki'] = true
        gitlab_rails['gitlab_default_projects_features_snippets'] = false
        gitlab_rails['gitlab_default_projects_features_builds'] = true
        gitlab_rails['lfs_enabled'] = true
        gitlab_rails['lfs_storage_path'] = "/var/opt/gitlab/lfs-objects"
        gitlab_rails['manage_backup_path'] = true
        gitlab_rails['backup_path'] = "/var/opt/gitlab/backups"
        gitlab_rails['backup_archive_permissions'] = 0600
        gitlab_rails['smtp_enable'] = true
        gitlab_rails['smtp_address'] = "xxx"
        gitlab_rails['smtp_port'] = 000
        gitlab_rails['smtp_user_name'] = "xxx"
        gitlab_rails['smtp_domain'] = "xxx"
        gitlab_rails['smtp_authentication'] = "login"
        gitlab_rails['smtp_enable_starttls_auto'] = true
        gitlab_rails['smtp_tls'] = false
        gitlab_rails['gitlab_ssh_host'] = "xxx"
        gitlab_workhorse['enable'] = true
        gitlab_workhorse['listen_network'] = "tcp"
        gitlab_workhorse['listen_addr'] = "0.0.0.0:8181"
        nginx['enable'] = false
        mattermost['enable'] = false
        mattermost_nginx['enable'] = false
        gitlab_rails['trusted_proxies'] = ['xxx']
        postgresql['shared_buffers'] = "1GB"
      ports:
        - 'xxx:8001:8181'
        - 'xxx:22:22'
      volumes:
        - '/var/www/gitlab/config:/etc/gitlab'
        - '/var/log/gitlab/:/var/log/gitlab'
        - '/var/www/gitlab/data:/var/opt/gitlab'

I was previously running gitlab v18.2.4. I updated using the following commands:

  • docker-compose pull
  • docker-compose stop
  • docker-compose up -d

What is the current bug behavior?

Gitlab is no longer accessible (502)

What is the expected correct behavior?

I should be able to access Gitlab

Relevant logs and/or screenshots

See summary.

Output of checks

?

Results of GitLab environment info

Docker version 24.0.2, build cb74dfc. The following is from the container.

Expand for output related to GitLab environment info 
System information
System:                                                                                                                                                                                                                                             
Current User:   git
Using RVM:      no
Ruby Version:   3.2.8
Gem Version:    3.6.9
Bundler Version:2.7.1
Rake Version:   13.0.6
Redis Version:  7.2.10
Sidekiq Version:7.3.9
Go Version:     unknown

GitLab information
Version:        18.3.0
Revision:       f54d72cc517
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     PostgreSQL
DB Version:     16.8
URL:            https://xxx
HTTP Clone URL: https://xxx/some-group/some-project.git
SSH Clone URL:  git@xxx:some-group/some-project.git
Using LDAP:     no
Using Omniauth: yes
Omniauth Providers:


GitLab Shell
Version:        14.44.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:      18.3.0
default Git Version:  2.50.1.gl1

Results of GitLab application Check

Expand for output related to the GitLab application check 
Checking GitLab subtasks ...


Checking GitLab Shell ...


GitLab Shell: ... GitLab Shell version >= 14.44.0 ? ... OK (14.44.0)
Running /opt/gitlab/embedded/service/gitlab-shell/bin/gitlab-shell-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: ...
3/1 ... yes
3/2 ... yes
3/3 ... yes
3/4 ... yes
2/5 ... yes
2/6 ... yes
7/7 ... yes
8/9 ... yes
8/10 ... yes
8/11 ... yes
8/12 ... yes
8/13 ... yes
8/14 ... yes
8/15 ... yes
8/16 ... yes
8/17 ... yes
8/18 ... yes
8/19 ... yes
8/20 ... yes
8/21 ... yes
7/22 ... yes
8/23 ... yes
1/24 ... yes
8/25 ... yes
1/26 ... yes
1/27 ... yes
8/28 ... yes
7/29 ... yes
7/30 ... yes
8/31 ... yes
1/32 ... yes
7/35 ... yes
7/36 ... yes
7/37 ... yes
1/39 ... yes
1/40 ... yes
3/41 ... yes
8/43 ... yes
3/44 ... yes
3/45 ... yes
3/46 ... yes
3/47 ... yes
3/48 ... yes
3/49 ... yes
17/50 ... yes
8/51 ... yes
8/52 ... yes
3/53 ... yes
1/54 ... yes
1/55 ... yes
8/56 ... yes
3/57 ... yes
3/58 ... yes
3/59 ... yes
3/60 ... yes
3/64 ... yes
3/65 ... yes
3/66 ... yes
3/67 ... yes
7/68 ... yes
7/69 ... yes
7/70 ... yes
17/71 ... yes
17/72 ... yes
17/73 ... yes
3/74 ... yes
3/76 ... yes
3/77 ... yes
3/78 ... yes
18/79 ... yes
18/80 ... yes
18/81 ... yes
8/82 ... yes
1/83 ... yes
1/84 ... yes
7/85 ... yes
3/86 ... yes
8/87 ... yes
1/88 ... yes
18/89 ... yes
18/90 ... yes
7/91 ... yes
7/92 ... yes
7/93 ... yes
1/94 ... yes
1/95 ... yes
21/96 ... yes
21/97 ... yes
18/98 ... yes
21/99 ... yes
191/100 ... yes
7/101 ... yes
21/103 ... yes
7/104 ... yes
7/105 ... yes
21/106 ... yes
8/107 ... yes
22/108 ... yes
22/109 ... yes
22/110 ... yes
21/111 ... yes
22/112 ... yes
7/113 ... yes
18/114 ... yes
21/115 ... yes
21/116 ... yes
18/117 ... yes
8/118 ... yes
18/119 ... yes
8/120 ... yes
1/121 ... yes
1/122 ... yes
1/123 ... yes
8/124 ... yes
8/125 ... yes
8/126 ... yes
21/127 ... yes
21/128 ... yes
7/129 ... yes
7/130 ... yes
8/131 ... yes
7/132 ... yes
7/133 ... yes
8/134 ... yes
1/135 ... yes
21/136 ... yes
1/137 ... yes
21/138 ... yes
21/139 ... yes
21/140 ... yes
21/141 ... yes
21/142 ... yes
21/143 ... yes
21/144 ... yes
21/145 ... yes
21/146 ... yes
21/147 ... yes
21/148 ... yes
21/149 ... yes
21/150 ... yes
21/151 ... yes
21/152 ... yes
21/153 ... yes
1/154 ... yes
21/155 ... yes
21/156 ... yes
7/157 ... yes
21/158 ... yes
21/159 ... yes
191/160 ... yes
21/161 ... yes
21/162 ... yes
21/163 ... yes
21/164 ... yes
21/165 ... yes
1/166 ... yes
21/167 ... yes
21/168 ... yes
21/169 ... yes
8/170 ... yes
1/171 ... yes
21/172 ... yes
191/173 ... yes
191/174 ... yes
191/175 ... yes
21/176 ... yes
191/177 ... yes
191/178 ... yes
21/179 ... yes
21/180 ... yes
Redis version >= 6.2.14? ... yes
Ruby version >= 3.0.6 ? ... yes (3.2.8)
Git user has default SSH configuration? ... yes
Active users: ... 1
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
Edited by 🤖 GitLab Bot 🤖