Internal Server Error on Admin Area -> Settings -> General

I am running GitLab on my little server for my little hobby projects. So this is what happened:

  • Last week I was still able to open Admin Area -> Settings -> General
  • There I enabled some sign-up restrictions (cannot remember which; isn’t important I think)
  • Then due to a stupid mistake I had to restore the postgresDb with a month-old dump
  • Now, whenever I try to open Admin Area -> Settings -> General, I get the ‘500 - Whoops, something went wrong on our end.’ Page
  • I am pretty sure that GitLab and the database are now out of sync .
  • In the production.log I find this:

Started GET “/admin/application_settings/general” for at 2020-12-07 17:40:33 +0000
Processing by Admin::ApplicationSettingsController#general as HTML
Completed 500 Internal Server Error in 134ms (ActiveRecord: 1.8ms | Elasticsearch: 0.0ms | Allocations: 45481)

ActionView::Template::Error (undefined method `domain_allowlist’ for #ApplicationSetting:0x00007f8e9e5797a0
Did you mean? domain_allowlist_raw
32: = _(“See GitLab’s %{password_policy_guidelines}”).html_safe % { password_policy_guidelines: password_policy_guidelines_link }
33: .form-group
34: = f.label :domain_allowlist, _(‘Allowed domains for sign-ups’), class: ‘label-bold’
35: = f.text_area :domain_allowlist_raw, placeholder: ‘’, class: ‘form-control’, rows: 8
36: .form-text.text-muted ONLY users with e-mail addresses that match these domain(s) will be able to sign-up. Wildcards allowed. Use separate lines for multiple entries. Ex:, *
37: .form-group
38: = f.label :domain_denylist_enabled, _(‘Domain denylist’), class: ‘label-bold’

app/models/application_setting_implementation.rb:206:in `domain_allowlist_raw’

Can someone help me?

  • Do I have to add some missing tables to the database?
  • Is there a way to reset those sign-up restrictions?
  • Anything else I can do?

Thanks for reading :slight_smile:

1 Like

UPDATE: after updating to the latest version of GitLab (13.6.3 (857c6c6a6a9)) the problem is gone. I am pretty sure that the update-process itself fixed the inconsistency and the exact number of the version is not important, but of course I cannot be sure.