Gitlab accidentally closed the sign-in, unable to log into the Web pit ...

Hand cheap accidentally with root in Gitlab backstage login function to turn off, then I was confused forced.

Here's how to fix it:

#进入数据库修改配置
[Email protected] ~]# gitlab-"/root"psql (9.2.     ' help ' for help.gitlabhq_production

To view a list of repositories:

[Email protected] ~]# Gitlab-psql-L could not change directory to"/root"List of Databases Name| Owner |   Encoding |    Collate | Ctype |Access Privileges---------------------+-------------+----------+-------------+-------------+---------------------------------gitlabhq_production| Gitlab | UTF8 | en_US. utf-8| en_US. utf-8|Postgres| Gitlab-psql | UTF8 | en_US. utf-8| en_US. utf-8|Template0| Gitlab-psql | UTF8 | en_US. utf-8| en_US. utf-8| =c/"Gitlab-psql"+                     |          |             |             | |"Gitlab-psql"=ctc/"Gitlab-psql"template1| Gitlab-psql | UTF8 | en_US. utf-8| en_US. utf-8| =c/"Gitlab-psql"+                     |          |             |             | |"Gitlab-psql"=ctc/"Gitlab-psql"(4Rows

After entering the client:

Commands can be tab-out, very cow B
set signin_enabled=true5

Restart Gitlab:

Here because of the slow start of the GitLab Web error appears: 502, Whoops, GitLab is taking too much time to respond.

After waiting for port 8080 to start, access can be restored:

TCP        0      0127.0.  0.1:8080          0.0.  0.0:*               LISTEN      7275

[Email protected] ~]# gitlab-ctl restartok:run:gitlab72207226   723472417250 72557260) 0s

　　

Gitlab accidentally closed the sign-in, unable to log into the Web pit ...