Just deleted the user again, re-created it with our usual ansible playbook, issue remains. Log in as admin user and click “Confirm email” manually and all working now. Weird.
A bug I’d say.
Same on 12.9.2. Have to confirm user after creating via the API. Not very automated. Should I report it?
Hi,
sorry for the late response, had been busy with onboarding tasks. It looks like as if this could be a bug, please continue with creating an issue and summarize your findings from here 
Thanks,
Michael
1 Like
Hi @ghenry
I agree with your assessment, this sounds like a bug.
To raise awareness of this and help us find a solution, can you please create new issue.
I suggest using the “Bug” issue template, adding as many relevant details as possible.
When you create an issue, please link it here and I’ll add appropriate labels to help triage and raise attention. Thanks!
2 Likes
Great, thanks!
Just thought of something else that might be coming into play:
Can you check <external_url>/admin/application_settings/general > expand Sign-up Restrictions, and verify if the checkbox for Send confirmation email on sign-up is checked or unchecked?
1 Like
Yep, it is.
Ah-hah! That explains it!
Having that setting enabled will send a confirmation email, and for that user to be “unlocked”, it requires the confirmation link in the confirmation email is clicked. If you’re creating a user with Ansible and the confirmation email isn’t received and the link it contains clicked, it would cause the “user is blocked” error you’re seeing.
If you did not check the box for this requirement, I suspect the default setting might’ve changed in 12.9.x. Do you notice if this checkbox was checked before upgrading?
Unchecking the box, or manually “confirming” the email of your Ansible-created user in the GitLab Admin UI should remove the block on this user.
1 Like
Nope. After your reply, I unchecked it and saved it. Deleted the user, ran the ansible playbook again and same message and going into Users still shows Confirm User.
Confirming the user and git pull etc. works as normal.
i did have the same problem and solved it by change the ssh-pub key on the gitlab platform
Hi, I have started training on Git Essential and struggling to clone the project. Getting below error:
Please advise what is wrong here.
Please do not use pictures for critical portions of your post. Pictures may not be legible, cannot be searched and are not view-able to some, such as those who use screen readers.
The error message says quite clearly what is wrong (in the cloning process): “Your account has been blocked”.
That really only shifts the problem to finding out why your account is blocked, and I can’t help with that, you need to get hold of an admin of the involved instance.
As far as I can see (but I haven’t spend much time on it), gitlabtraining.cloud is a service under gitlab.com, if that’s the case I will suggest opening a support case, but support for non-paying users is not prioritised, so you’ll probably have to wait.