OpenSSL bad decrypt

Is this happening because somehow /etc/gitlab/gitlab-secrets.json is not available/loaded properly the first time?

@stanhu The gitlab-secrets.json is readed and transformed into config/secrets.yml, it may be a problem that Unicorn/Sidekiq is not being restarted after this file gets changed?

@marin What do you think?

As far as omnibus-gitlab is considered, services are getting restarted.

Easy to check though, if a gitlab-ctl restart helps then there is an issue with the type of restart, currently USR2.

Thanks all, I'll report back to get some more insight.

@marin Any ideas on how to check if another process is trapping the USR2 signal.

@balameb I don't follow. Did gitlab-ctl restart help or it didn't?

@marin I'm still waiting for a reply but from the original ticket it says that rebooting works but can't say about restarting yet. I'll ask again.

I have same Issue gitlab version is 8.8.3, gitlab-secrets.json file is present in /etc/gitlab/ application restart doesn't help nor gitlab-ctl reconfigure.
any fix or workaround ?


Completed 302 Found in 336ms (ActiveRecord: 133.9ms)
Started GET "/docker/aqua-player-lib-docker" for 127.0.0.1 at 2016-06-08 16:28:39 +0400
Processing by ProjectsController#show as HTML
  Parameters: {"namespace_id"=>"docker", "id"=>"aqua-player-lib-docker"}
Completed 500 Internal Server Error in 79ms (ActiveRecord: 5.6ms)

OpenSSL::Cipher::CipherError (bad decrypt):
  app/models/project.rb:383:in `import_url'
  app/models/project.rb:413:in `external_import?'
  app/models/project.rb:405:in `import?'
  app/models/project.rb:421:in `import_in_progress?'
  app/controllers/projects_controller.rb:93:in `show'
  lib/gitlab/middleware/go.rb:16:in `call'```

Same issue, gitlab-ctl restart did not help.

GitLab Enterprise Edition 8.8.3-ee 9a7da9c

See https://gitlab.com/gitlab-org/gitlab-ce/issues/17873#note_12117671 and #17975 (moved). Did you do a backup/restore? The issue is that database/secrets.yml is needed.

@stanhu Thanks for mentioning that.
What I did was I had two Gitlab machines I backed up original one (Production server) and than restored it to another machine, (Test server) I didn't checked every project by hand so didn't notice this issue. after that I deleted prod server update everything installed gitlab omnibus and restored backup from test server.

So as I guess I have deleted db_key_base file or does backup includes it somewhere ?

The backup does not include database/secrets.yml for a number of reasons. #17975 (moved) seeks to address a better solution.

Status changed to closed

I got the same problem with Gitlab CE version 8.11 now... :( . I removed the gitlab ci section from gitlab-secrets.json. Otherwise Gitlab didn't load anymore.

So now I get:

Completed 500 Internal Server Error in 55ms (ActiveRecord: 10.3ms)                                                                                                                                         
                                                                                                                                                                                                           
OpenSSL::Cipher::CipherError (bad decrypt):                                                                                                                                                                
  app/models/project.rb:489:in `import_url'                                                                                                                                                                
  app/models/project.rb:525:in `external_import?'                                                                                                                                                          
  app/models/project.rb:517:in `import?'                                                                                                                                                                   
  app/models/project.rb:533:in `import_in_progress?'                                                                                                                                                       
  app/controllers/projects_controller.rb:94:in `show'                                                                                                                                                      
  lib/gitlab/request_profiler/middleware.rb:15:in `call'                                                                                                                                                   
  lib/gitlab/middleware/go.rb:16:in `call'

OK, I solved it. You should ONLY remove the 'gitlab_ci['gitlab_server']' part in gitlab-secrets.json...! Do not remove too much :).

@webmaster1989 I am having this issue just this moment. Can you provide anymore information on how you solved it? I find that some projects work and others do not, can't seem to see a correlation between what will work and what won't. I have checked my gitlab-secrets.json and I don't have a gitlab_ci['gitlab_server'] section. This is that is in mine:

{
  "gitlab_shell": {
    "secret_token": ""
  },
  "gitlab_rails": {
    "secret_key_base": ""
    "db_key_base": ""
    "otp_key_base": ""
  },
  "registry": {
    "http_secret": ""
    "internal_certificate": ""
    "internal_key": ""
  },
  "mattermost": {
    "email_invite_salt": "",
    "file_public_link_salt": "",
    "email_password_reset_salt": "",
    "sql_at_rest_encrypt_key": ""
  }
}

EDIT: Just to add to this, it seems to just be the "Project" page, I can still access things like Settings, Repository Files, Issues, etc, it is just the main project page that I get this error on EDIT 2: Can still push and pull from the repo as normal

@jonnybooker You have similar issues like me (some projects do work & others do not).

In my case it was really the gitlab_ci section within the gitlab-secrets.json file. The db_key_base I have in this file for gitlab_ci is used for encrypting (decrypting I guess as well?) sensitive data into the database. Do you have any back-ups of the gitlab-secrets.json file? I'm not an expert, so I don't know if you loss this information how to regenerate the json file or retrieve the encrypted data from the database...

In the future you really should make back-ups of these files,the back-up feature will not back-up the files in /etc/gitlab for you (sudo gitlab-rake gitlab:backup:create), too bad.. So you need to manually back-up the gitlab.rb & gitlab-secrets.json files.

Mentioned in issue #23126 (closed)

Mentioned in issue #24458 (closed)

How I combine two gitlab-secrets.json file? Because some accounts worked in one gitlab-secrets.json file and other accounts worked in the another gitlab-secrets.json file . So bad. How to solve that? I moved my gitlab server to new machine, and this issue happened.

I my case the same exception was rised when i create repository by importing from another. After shutting down the donor project server I catch 500 error. The exception must be import_url unavailable , not ssl error. My resolution was to clear broken link from database:

update projects set import_url=NULL where id = MY-PROJECT_ID;

@ju.shcherbak I got same problem and fixed by your way. Thanks! Maybe it need a friendly face instead of 500.

OpenSSL bad decrypt

Summary

Steps to reproduce

Expected behavior

Relevant logs and/or screenshots

Output of checks

Results of GitLab Application Check

Results of GitLab Environment Info

Possible fixes

Designs

Child items 0

Activity

Admin message

Admin message

OpenSSL bad decrypt

Summary

Steps to reproduce

Expected behavior

Relevant logs and/or screenshots

Output of checks

Results of GitLab Application Check

Results of GitLab Environment Info

Possible fixes

Activity