Error yang muncul di log /var/log/gitlab/gitlab-rails/production.log
Processing by Projects::Settings::CiCdController#show as HTML Parameters: {"namespace_id"=>"lp", "project_id"=>"api-notification"} Completed 500 Internal Server Error in 262ms (ActiveRecord: 25.8ms | Elasticsearch: 0.0ms | Allocations: 162227) ActionView::Template::Error (): 6: locals: { type: 'specific', 7: clusters_path: project_clusters_path(@project) } 8: %hr 9: = render partial: 'ci/runner/how_to_setup_runner', 10: locals: { registration_token: @project.runners_token, 11: type: 'specific', 12: reset_token_url: reset_registration_token_namespace_project_settings_ci_cd_path } lib/gitlab/crypto_helper.rb:27:in `aes256_gcm_decrypt' app/models/concerns/token_authenticatable_strategies/encrypted.rb:45:in `get_token' app/models/concerns/token_authenticatable_strategies/base.rb:33:in `ensure_token!' app/models/concerns/token_authenticatable.rb:43:in `block in add_authentication_token_field'
Beberapa solusi :
1. Hapus gitlab runner dari admin URL-GITLAB/admin/runners, lalu klik Reset runners registration token
2. Reset Token dari database
UPDATE projects SET runners_token = null, runners_token_encrypted = null; UPDATE namespaces SET runners_token = null, runners_token_encrypted = null; UPDATE application_settings SET runners_registration_token_encrypted = null; UPDATE ci_runners SET token = null, token_encrypted = null;
3. Non-aktifkan Gitlab CI
edit file /etc/gitlab/gitlab.rb, tambahkan
gitlab_rails['gitlab_default_projects_features_builds'] = false
4. Restart gitlab gitlab-ctl reconfigure && gitlab-ctl restart
Cek url runner di admin ataupun link CI/CD (-/settings/ci_cd) dari user, bila sudah bisa di akses tidak lagi menampilkan 500 error.
1. Aktifkan Gitlab CI
edit file /etc/gitlab/gitlab.rb, ubah
gitlab_rails['gitlab_default_projects_features_builds'] = false
menjadi true
gitlab_rails['gitlab_default_projects_features_builds'] = true
2. Register ulang runner