Your account is pending approval from your GitLab administrator and hence blocked. Please contact your GitLab administrator if you think this is an error
Well as the message states. You have created an account on a self-hosted GitLab instance.
The administrators of that instance have configured it so that they have to manually approve every account that is created. This is usually to prevent spam and exploiting of publicly reachable instance.
When this setting is enabled, any user visiting your GitLab domain and signing up for a new account using the registration form must be explicitly approved by an administrator before they can start using their account. In GitLab 13.6 and later, this setting is enabled by default for new GitLab instances. It is only applicable if sign ups are enabled.
- gitlab docs; link
The first time you access your self-hosted Gitlab it asks you to set up a password. Then you can access using user root and the password you set up. Hope it helps!
I just ran into the same problem (Vbox, VM; self-managed gitlab on my VM's static IP).
I remembered installing with export GITLAB_HOME=/srv/gitlab
sudo more /srv/gitlab/initial_root_password
in that file is a long password which I used along with root as the user.
Related
I run gitlab and activated mattermost. I created a new project and set up a mattermoast team.
Now I want to add all other users. But my user is no admin in mattermost. how can I solve that?
Thanks in advance.
According to this link, the first user in the system has the system_admin role.
Find the first user that is created on your Mattermost server and use it as an admin account.
I'm trying to get to the admin area so I can set the time-to-live for the gitlab container registry token. However, I don't see where that's available to me. I am the sole owner and creator of the project after I signed up for a Gitlab account and clicked to create a new project. My problem is similar to this person:
https://forum.gitlab.com/t/where-is-the-admin-area/5936
except I'm not using Gitlab CE.
So how can I become an admin for my own project so I can change some admin settings?
You can't have access to the admin area of gitlab.com. It is a private instance of Gitlab Enterprise Edition, belonging to Gitlab. They do allow anyone to have unlimited access (any number of public or private repositories as well as groups etc) but you can't be an admin.
Being an admin would mean you could see anyone's projects or delete them etc. That's not reasonable...
I am locking for the right GitLab CE server configuration to block new users, which signed up manually via the sign-up page (username / name / password). This users should be blocked until manually confirmed by an admin.
I found options to block new (auto-created) users for LDAP and OmniAuth in gitlab.yml but not for plain user accounts, who just registered on the sign-up page:
## LDAP settings
ldap:
servers:
main:
block_auto_created_users: true
## OmniAuth settings
omniauth:
block_auto_created_users: true
I want to let the users register themselves, so completely disabling this the admin area is not wanted:
How can I configure GitLab CE to block new users who just signed-up so that I have an admin confirmation for new users (not using LDAP or OmniAuth)?
GitLab version is 8.5.7 CE.
You now (October 2020) have an alternative with GitLab 13.5:
Required approval for new user registration
To reduce the operational burden on GitLab administrators without compromising security, GitLab 13.5 introduces a new instance-level option to require administrator approval for any new user accounts.
This option is disabled by default but when enabled, will require manual approval by instance administrators before users that completed the sign-up process can access the instance.
See Documentation and Epic.
And:
See GitLab 13.6 (November 2020)
Admin approval required by default for new user registrations
In GitLab 13.5, we introduced the option to require administrator approval for new user registrations.
To increase security of our default configuration, GitLab 13.6 makes this option the default experience for new instances.
We have also introduced email notifications to instance administrators when a new signup occurs and to users when their registration is approved.
Email notifications at these critical steps in the process help reduce the turnaround time to onboard users when administrator approval is required.
See Documentation and Epic.
YouTrack supports integration with GitLab, which I would like to use.
When I create a new integration, YouTrack asks for a private token and gives me the option to navigate to my own user profile on our GitLab server to copy my token.
Does that mean that all future actions performed by YouTrack will be performed with my user account? Should I create a separate user for YouTrack?
It does mean that all future actions are performed with this user, but all those actions are read-only. The only modifying action is that if you delete/disable the integration, YouTrack will delete a web hook that it registers in GitLab.
My campus runs a gitlab server. I am a user, not an admin. Campus policy forbids giving LDAP access to off-campus collaborators/co-authors, but has no problem in principle with allowing such folks to have "Developer" level access to non-public repositories on an invitational basis. Is it possible to have my off-campus colleagues send me an SSH key, and have the gitlab admin create a no-login user with that key who I could then add as a "Developer" member to selected projects? If it's do-able, what's the magic process so I can pass it along to the IT support folks?
Ask your IT support team to create Gitlab account with specific permissions for those developers without LDAP account. And then simply add them to the repositories and ask them to upload ssh keys.