No Return from Server while trying to add GPG Keys
Summary
We recently upgrade from 11.9 via 11.11.5 to 12.0.3 Community Edition
After this a user reports that he cannot add GPG Keys in Settings Area.
when Pressing ADD KEY Button after a period of time we get
`Proxy Error
The proxy server received an invalid response from an upstream server. The proxy server could not handle the request POST /profile/gpg_keys.
Reason: Error reading from remote Server `
Steps to reproduce
Install 11.9 with several users Projects, migrate to 11.11 and then to 12.0.3
11.11 still is ok with GPG keys but 12.0.3 isnt anymore
Example Project
What is the current bug behavior?
we get a PROXY Error from nginx, trying without nginx does not help The proxy server could not handle the request POST /profile/gpg_keys.
What is the expected correct behavior?
Adding GPG Succesful or Comeback with error message
Relevant logs and/or screenshots
we find some http 502 Errors in gitlab_access.log but no further help assuming loop in procedure resulting timeout.
Output of checks
this happens on centos 6.6 - so we use community Edition el6
Results of GitLab environment info
Expand for output related to GitLab environment info
System information System: CentOS 6.6 Current User: git Using RVM: no Ruby Version: 2.6.3p62 Gem Version: 2.7.9 Bundler Version:1.17.3 Rake Version: 12.3.2 Redis Version: 3.2.12 Git Version: 2.21.0 Sidekiq Version:5.2.7 Go Version: unknownGitLab information Version: 12.0.3 Revision: 08a51a9db93 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: PostgreSQL DB Version: 10.7 URL: http://git-ext HTTP Clone URL: http://git-ext/some-group/some-project.git SSH Clone URL: git@git-ext:some-group/some-project.git Using LDAP: yes Using Omniauth: yes Omniauth Providers:
GitLab Shell Version: 9.3.0 Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell Git: /opt/gitlab/embedded/bin/git
Results of GitLab application Check
Expand for output related to the GitLab application check
[root@gitlab]# gitlab-rake gitlab:check SANITIZE=true Checking GitLab subtasks ... Checking GitLab Shell ... GitLab Shell: ... GitLab Shell version >= 9.3.0 ? ... OK (9.3.0) 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 Gitaly ... Gitaly: ... default ... OK Checking Gitaly ... Finished Checking Sidekiq ... Sidekiq: ... Running? ... yes Number of Sidekiq processes ... 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: ... Server: ldapmain LDAP authentication... Success LDAP users with access to your GitLab server (only showing the first 100 results) Checking LDAP ... Finished Checking GitLab App ... 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: ... all yes Redis version >= 2.8.0? ... yes Ruby version >= 2.5.3 ? ... yes (2.6.3) Git version >= 2.21.0 ? ... yes (2.21.0) Git user has default SSH configuration? ... yes Active users: ... XXX Checking GitLab App ... Finished Checking GitLab subtasks ... Finished