I have hit resend confirmation email numerous times over the last 24 hours and no email is received, and no its not in the spam filder, trying to create a gitlab.com account. I have seen this in the forums as a constant problem, its often closed, and then re-opened. Is there a solution to reset/clear the username/email address and try again? Or if you try to create an account, and the confirmation email fails to show up, do you just write off gitlab.com and move on? Are you locked out forever, since now the username/email address are “taken” but there is no way to start process over, and it will just fail repeatedly, telling you you cannot login because the username/email is “taken” ut has not been confirmed, yet there is no way to confirm the email address? … trying to migrate from github, but so far I am less than impressed. This is first time ever that I have seen the signup process for a website fail.
I transferred this to our support, hang on!
As stated in Support | GitLab
If you have an issue accessing your account, please use the support web form so an admin can help you.
@axil I have the same problems, I never get a confirmation email so I can’t login, also checked spam folder. I can change my pw however. How to proceed?
same problem here.
I never receieved any email so I can’t validate my account!
Any help?
me too, I never received any email
Have the same problem. Is there some solution?
Same problem on April 2nd, 2019.
I have found /users/password/new works only if I logoff gitlab from the other tabs.
/users/confirmation/new doesn’t send the email, even if I logoff.
Same problem confirmation email never received. finally used github account to login
I’m getting the same issue. Any solutions?
Have same issue, how it can be solve?
Same here.
Same problem, my new email is work but the confirmation never send
@RootKitDev This likely due to a recent email issue - Let’s move to a support ticket and get your account sorted, as some email addresses seem to be getting blocked on our end. Can you open a ticket and choose "Email reconfirmation issue” as the subject: https://support.gitlab.com/hc/en-us/requests/new?ticket_form_id=360000803379
I am not getting a confirmation email for
Like above I have tried re-sending many times
This is still happening. I create a ticket (I get the support emails fine) then they close my ticket because there is no account. I can’t make an account which is why I’m making the ticket. Nice little catch 22 they have going on and they seem to refuse to acknowledge it.
I had to make some throw away email address with a 3rd party to sign up. Clearly whomever does the confirmation emails has some malformed or ill conceived security rules killing emails to various domains / services.
Given I run my own email services this growing discrimination is really infuriating. The web has devolved into “If you aren’t using MSFT/Google services you’re clearly an evil bot…BLOCKED!” Security enabled in browser? BLOCKED!
Well I spoke with support but they dance and contradict things. It’s not them, it’s me, my email is broken. Funny it’s worked for years with other services, government contacts, friends, family…how strange. Comically my email is broken but the gitlab zendesk support emails arrived just fine…such mystery! Then they say I’m not entitled to support for registration because I’m registered.
Basically they use mailgun which does a port scan (with the domain) before sending (rather than just send the fricking mail). Probably then hits my cloudflare geofence or human challenge, fails to see the port it wants, doesn’t send mail…even though if they JUST SENT the mail it would work because cloudflare doesn’t proxy the mail service. So for anyone in the future mailgun port scans your email (incorrectly), fails, doesn’t send, it’s not gitlab, it’s you.
If the proxy option (cloud) is disabled for the MX entries and A record for delivering email, then this cannot be true. The connection is then direct to the server, totally bypassing Cloudflare. If it’s hititng Cloudflare as you mention above, then you have the cloud (proxy) enabled for MX and A records related to your mail server. That means it’s a configuration error on your part because Cloudflare doesn’t work to proxy emails as you also mentioned.
As far as cloudflare says you can’t enable proxy for MX and it’s not enabled either way (again my mail works fine and has for years), but the point is mailgun is doing a web scan in a way that resolves the domain through cloudflare. Again, get all mail fine, including gitlab zendesk…the issue is mailgun and as this thread says lots of reports, once a report is opened gitlab closes it…never acknowledge the catch 22, never fix the problem.
Seems strange that mailgun would fail in that instance. Doing a scan of the mail server would show that port 25 is accessible because the DNS entry isn’t proxied via Cloudflare in that instance (or at least shouldn’t be). I don’t have experience of mailgun so cannot comment, and I’ve never had email problems with Gitlab either. But I agree there are plenty of other people on this forum that have had the same problem when trying to register accounts. It could also be RBL filtering from mailgun side not sending emails if the receiving server is on a blacklist for some reason. But again, without seeing logs, difficult to see if that was the case or not.
I understand your frustration, since Gitlab should at least help users that are attempting to register on their SaaS service - especially since they could become potentially paying customers in the future. The other alternative in such a situation would be to run your own Gitlab server on a VPS like quite a few of us do here. That way you are in control of your own server, and also unlikely to have issues sending/receiving emails from your Gitlab instance, as it will connect to your mail server with the appropriate authentication methods. But I also understand that not everyone wants to run their own server. So catch 22 