Unable to register a new self-hosted workspace

Description

I have successfully installed Rocket.Chat 6.7.4 on Mongo 4.4 using Docker and Docker Compose under Ubuntu 24.04 LTS OS.

During the setup wizard, it prompts me to verify and register the workspace. I have clicked the confirmation link in the email, and it says:

====
Email Confirmed!

You can return to your Rocket.Chat application – we have launched your workspace already.

However, when we are back to the Rocket.Chat application, it is still at “Awaiting confirmation” page and the pop up message “Workspace is not registered” keeps on popping up.

Server Setup Information

  • Version of Rocket.Chat Server: 6.7.4
  • Operating System: Ubuntu 24.04 LTS
  • Deployment Method: Docker
  • Number of Running Instances: 1
  • DB Replicaset Oplog: not sure
  • NodeJS Version: not sure
  • MongoDB Version: 4.4
  • Proxy: not sure
  • Firewalls involved: no (ufw disabled)

Any additional Information

Any help is appreciated, thanks.

Which document did you follow?

I would think you should have started on 6.9.x and Mongo 5.

But DON’T use the “latest” tag. See this:

How have you setup your reverse proxy andd SSL certificate and server name?

What do your docker logs say?

I have the same exact issue. What’s the fix?

Use a non disposable email address.

gmail/hotmail/other junkmails are not permitted.

are you saying a custom domain email is not permitted?

No I didn’t. You can see exactly what I said. A number of common junk domains are blocked inc gmail hotmail etc.

And note you said “I have the same issue”

If so that’s almost always the answer.

If not then you need to tell us a lot more about your deployment, preferably in its own thread.

Information required

Also note a random comment on a closed bug will likely get zero attention.

Thanks.

Then you didn’t read my comment well. I mentioned that I use a custom domain email address and I mentioned my environment as well

Oh I did. That’s the job I do in my spare time here.

Again, read what I said, not what you think I said.

Junkmail addresses are not permitted eg gmail, hotmail and some others though I do not have a comprehensive list. You haven’t actually mentioned the domain here either so no way I can actually find out if it is permitted or not.

No you said you had the same issue, not the same environment.

That isn’t your environment.

If you actually have the same environment then the first thing to do is read the docs and upgrade as yours is EOL.

https://docs.rocket.chat/docs/version-durability

On the basis that it isn’t identical then you need to describe exactly what you do have as per the link I posted.

That will save us all the XY Problem and wasting our spare time.

Thanks.

I posted on another forum, and there I expanded more, I thought it was this one, I mixed them up, apologies. I host on railway.app and I used a customdomain.com email address

1 Like

I have no knowledge or experience of your platform.

You still haven’t old us anything about your deployment and we have no idea what your domain is.

So we really can’t help you right now.

I can only suggest you check your setup and test with a different email address.

I think you can actually try and create a new cloud account with it and add the Reg key to the .env when you start the server.

There are other posts on this sort of thing.

I have the exact same thing:

I registered with my company domain (nothing disposable or junk domain like) and I get the same response: when I verify my email I get a success message, but after that, it says my workspace is not registered.
And then, we I search for help, someone keeps on telling me that I should not use a junkmail address, which it is not.
Is there a solution already?

I now also tried with 3 different email addresses; all company domains, with different hosting companies. No difference; it just doesn’t work.

Splattering comments everywhee on old posts without providing any basic info on your own setup is a) making a lot more work for me with no results, and I don’t even work here b) not making you many friends and c) not going to get a fix.

One place, one properly documented message.

Thanks.