Hello,

Recently, I upgraded GitLab from version 14.0.0 to 17.4.2 and migrated it to a supported OS (AlmaLinux), while keeping the same IP address and hostname.

I can create projects and add users to groups, but I’m unable to make any changes in the admin area.

500: We’re sorry, something went wrong on our end

Request ID: 01JA7TKC53N0ZFS90D48XTET1E
Try refreshing the page, or going back and attempting the action again.
Please contact your GitLab administrator if this problem persists.

Here is the info:

System:
Current User:   git
Using RVM:      no
Ruby Version:   3.1.5p253
Gem Version:    3.5.17
Bundler Version:2.5.11
Rake Version:   13.0.6
Redis Version:  7.0.15
Sidekiq Version:7.2.4
Go Version:     unknown

GitLab information
Version:        17.4.2
Revision:       2c7e66ebdb6
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     PostgreSQL
DB Version:     14.11
URL:            http://gitlab.ssctest.gov.hr
HTTP Clone URL:
SSH Clone URL:  
Using LDAP:     yes
Using Omniauth: yes
Omniauth Providers:

GitLab Shell
Version:        14.39.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:      17.4.2
- default Git Version:  2.46.0

error:
==> /var/log/gitlab/gitlab-rails/production.log <==
OpenSSL::Cipher::CipherError ():

I followed the migration steps from the official site, and based on the error, it seems to be an issue with the gitlab-secrets.json file.

I’ve copied the file from the old server and restored the backup.

Any ideas how to fix this?

Thank you

I’m able to access the admin area, even change the setting but when I click save changed it shows error 500, but the change is visible in GUI.

And how did you upgrade from Gitlab 14.0.0 to 17.4.2? Direct? Or did you follow the upgrade path?

If you did it direct and didn’t follow the upgrade path, then you will need to restore your server to version 14.0.0 and follow the upgrade process correctly ensuring that the upgrade path is followed, and between each upgrade you ensure that background migrations have finished before starting the next upgrade. This is all explained in the Gitlab documentation, and a lot of links for that can be found here: GitLab Upgrade Path Resources

Hello,

I’ve followed the path. I think I had almost 12 upgrades in between.
I took hours

First thing to try would be:

gitlab-ctl reconfigure
gitlab-ctl restart
systemctl restart gitlab-runsvdir

if problems still persist after that, check all the log files under /var/log/gitlab to see what errors there might be that may hint at why this isn’t working.

Sometimes when Gitlab has issues after upgrades, the reconfigure and restart would normally sort it out, but other things can happen that these steps may not resolve.

Hey,

thank you for the info.

It was an issue with the gitlab-secrets.json file. I’ve restored the file and setup gitlab again and now it works

Thank you once again!