Page 500 when opening projects imported from github

I had gitlab 8.8.2 installed using omnibus in a CentOS machine. I changed to gitlab-omnibus using docker on Ubuntu 16. Now I have updated to 8.9.2 and whenever I access projects that were imported from github I get the following error:

==> /var/log/gitlab/gitlab-rails/production.log <==
Started GET "/lucasperin/desafio" for (my ip) at 2016-06-29 12:35:37 -0300
Processing by ProjectsController#show as HTML
  Parameters: {"namespace_id"=>"lucasperin", "id"=>"desafio"}
Completed 500 Internal Server Error in 60ms (ActiveRecord: 3.8ms)

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

I have imported new projects after this error and verified that it only happens to projects that were imported in my previous installation.

I should also mention that to upgrade, I restored my backup in gitlab-docker using an 8.8.2 image and latter updated the server pulling lattest image.

I also changed the subdomain of my gitlab, but I don't think this is relevant (from codes.my.domain to gitlab.my.domain).

Added ~12980 import labels

I have this issue as well on any of the repos that existed in a previous install where the secrets.json was fubar. is there a way to fix this without recreating the entire repo?

I upgraded to 8.9.4 and still have same issue. The repos that I really need I fixed by re-importing. Not aware of any other fix.

ugh, ok

I have a similar situation and the exact same error.

Any progress or solution on this?

For those that stumble upon this and need a work around, I did the following:

1. Clone the repository locally
2. Create a new project with ha name like project_1
3. Migrate issues from old to new repository
4. Push local repo to server

That worked for my purposes. Quick and dirty.

Mentioned in issue #24458 (closed)

moved to gitlab#5315

Hey! 👋

GitLab is moving all development for both GitLab Community Edition and Enterprise Edition into a single codebase. The current gitlab-ce repository will become a read-only mirror, without any proprietary code. All development is moved to the current gitlab-ee repository, which we will rename to just gitlab in the coming weeks. As part of this migration, issues will be moved to the current gitlab-ee project.

If you have any questions about all of this, please ask them in our dedicated FAQ issue.

https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

You can also find more information here:

• https://gitlab.com/gitlab-org/gitlab-ee/issues/13304
• https://about.gitlab.com/2019/08/23/a-single-codebase-for-gitlab-community-and-enterprise-edition/

Frequently Asked Questions

For an up to date list of questions and answers, please take a look at https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

What will we do with the repository names?

https://gitlab.com/gitlab-org/gitlab-ee/ will become https://gitlab.com/gitlab-org/gitlab, and https://gitlab.com/gitlab-org/gitlab-ce will become https://gitlab.com/gitlab-org/gitlab-foss.

Why rename gitlab-ce to gitlab-foss?

Using "gitlab" and "gitlab-ce" would be confusing, so we decided to rename gitlab-ce to gitlab-foss to make the purpose of this FOSS repository more clear

I created a merge requests for CE, and this got closed. What do I need to do?

You will need to create a merge request at https://gitlab.com/gitlab-org/gitlab-ee/. This link will eventually redirect to https://gitlab.com/gitlab-org/gitlab.

How does the licensing work in this new setup?

Everything in the ee/ directory is proprietary. Everything else is free and open source software. If your merge request does not change anything in the ee/ directory, the process of contributing changes is the same as when using the gitlab-ce repository.

Will you accept merge requests on the gitlab-ce/gitlab-foss project after it has been renamed?

No. Merge requests submitted to this project will be closed automatically.

Will I still be able to view old issues and merge requests in gitlab-ce/gitlab-foss?

Yes.

How will this affect users of GitLab CE using Omnibus?

No changes will be necessary, as the packages built remain the same.

How will this affect users of GitLab CE that build from source?

Once the project has been renamed, you will need to change your Git remotes to use this new URL. GitLab will take care of redirecting Git operations so there is no hard deadline, but we recommend doing this as soon as the projects have been renamed.

Where can I see a timeline of the remaining steps?

https://gitlab.com/gitlab-org/gitlab-ee/issues/13304

Will community contributions submitted to the new "gitlab" repository be available in the new gitlab-foss repository?

Yes, these changes will be synced to gitlab-foss automatically, several times per day.

locked this issue