Default username/password not working.
Can't sign in on new install
Cannot log into new GitLab installation
Store username and password
Videos
I had a similar problem. Even if I set the environment variable, it seems that my gitlab ce still can't login. So I reset the password with the "root" user.
# dir: /etc/gitlab
gitlab-rake "gitlab:password:reset[root]"
Wait 10 minutes. And result
Enter password:
Confirm password:
Password successfully updated for user with username root.
Then all works as usual.
If you are using Docker, you can get this bash:
docker exec -it gitlab_continer bash
and open Rails console.
gitlab-rails console -e production
and Enter the code below
user = User.where(id: 1).first
user.password = 'your secret'
user.password_confirmation = 'your secret'
user.save
exit
You can get more information from the link below https://docs.gitlab.com/ee/security/reset_user_password.html
Greetings,
I recently set up a docker stack on my synology NAS to host gitlab. It spins up and I can get to the login screen, but I cannot login. I tried the default credentials of admin@local.host and 5iveL!fe , to no avail. Any ideas? Is there some other password now? Or some way I can set an initial default with an environment variable or something?
Not strictly related to the current scenario. Sometimes when you are prompted for password, it is because you added the wrong* origin format (HTTPS instead of SSH)
HTTP(S) protocol is commonly used for public repos with strong username+pass
SSH authentication is more common for internal projects where you can authenticate with a ssh-key-file and simple pass-phrase
GitLab users are more likely to use the SSH protocol
View your remote info with
git remote -v
If you see HTTP(S) address, this is the command to change it to SSH:
git remote set-url origin [email protected]_domain.com/example-project.git
It prompted me for password.
It shouldn't.
If you have the right public/private key representing a user authorized to access project-x, then gitlab won't ask you for anything.
But that supposes that ssh -vT [email protected] is working first.