GET "/profile/gpg_keys" times out, returns 502 badgateway

I’m using Chrome on Windows to access GitLab CE 10.4.0 (128ef10). I have a GPG key associated with my profile. When I go to look at my GPG keys page, it times out with a 502 HTTP code. Looking at the log files gets me this:

[root@GITLAB gitlab]# pwd
/var/log/gitlab

[root@GITLAB gitlab]# grep -R 'gpg_key' *
gitlab-rails/production.log:Started GET "/profile/gpg_keys" for [IPADDR] at 2018-05-02 08:19:24 -0700
gitlab-rails/production.log:Started GET "/profile/gpg_keys" for [IPADDR] at 2018-05-02 08:25:20 -0700

gitlab-workhorse/current:2018-05-02_15:20:24.35614 2018/05/02 08:20:24 error: GET "/profile/gpg_keys": badgateway: failed after 60s: EOF
gitlab-workhorse/current:2018-05-02_15:20:24.38748 gitlab.REDACTED.COM @ - - [2018-05-02 08:19:24.100243221 -0700 PDT m=+3032.427806050] "GET /profile/gpg_keys HTTP/1.1" 502 2916 "https://gitlab.REDACTED.COM/profile" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.119 Safari/537.36" 60.287078
gitlab-workhorse/current:2018-05-02_15:26:21.13885 2018/05/02 08:26:21 error: GET "/profile/gpg_keys": badgateway: failed after 60s: EOF
gitlab-workhorse/current:2018-05-02_15:26:21.13889 gitlab.REDACTED.COM @ - - [2018-05-02 08:25:20.758804085 -0700 PDT m=+3389.086366677] "GET /profile/gpg_keys HTTP/1.1" 502 2916 "https://gitlab.REDACTED.COM/profile" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.119 Safari/537.36" 60.379910

nginx/gitlab_access.log:10.12.7.78 - - [02/May/2018:08:20:24 -0700] "GET /profile/gpg_keys HTTP/2.0" 502 2916 "https://gitlab.REDACTED.COM/profile" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.119 Safari/537.36"
nginx/gitlab_access.log:10.12.7.78 - - [02/May/2018:08:26:21 -0700] "GET /profile/gpg_keys HTTP/2.0" 502 2916 "https://gitlab.REDACTED.COM/profile" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.119 Safari/537.36"
  • I’ve rebooted the GitLab server.
  • I’ve cleared cookies and cache from the browser.

What else?