How do I change from community to starter?

Description

I upgraded from 6.4.7 to 6.5.0.

I read that it should change to “starter” automatically, but it didn’t. It still says “Community” in the Subscription tab. Push notifications are no longer working either.

I decided to try to make a new workspace/token on cloud.rocket.chat.

It gives me a token and says:

Paste this token into your workspace:
Admin > Connectivity Services > Token

I cannot find where this token is supposed to go in the UI. There is no “Connectivity Services” menu and nothing comes up with you search for it or the word “token” in the settings.

I also tried starting the docker service with “REG_TOKEN” set to my token and that appears to not do anything either.

I also tried to turn the Setup Wizard back on, restarted the server, and when I am greeted with the setup wizard, it says it’s on step “3 of 2” and when you type anything into the “admin email” input, the “register workspace” button becomes disabled.

It seems like everything is completely messed up now.

Server Setup Information

  • Version of Rocket.Chat Server: 6.5.0
  • Operating System: Ubuntu
  • Deployment Method: Docker
  • Number of Running Instances: 1
  • DB Replicaset Oplog:
  • NodeJS Version: v14.21.3
  • MongoDB Version: 5.0.23 / wiredTiger (oplog Enabled)
  • Proxy: traefik
  • Firewalls involved:

Hey, @iankaufmann

I may be able to help you understand what happened so far. Can you send me an e-mail (vinicius.marino@rocket.chat), please? I must ask for more specific workspace details to support you here.

Hello @vinicius.marino, may I aslo ask for assistance or advice here?
Yesterday, my client informed me their RocketChat edition switched from Starter to Community.
Last update we did was 5 weeks ago and just yesterday they reported it switched to Community edition and they lost some features. The issue was resolved after they re-synced the license, but we are curious why or how did that happen.

  • Version of Rocket.Chat Server: 6.9.3
  • Operating System: CentOS Stream
  • Deployment Method: Docker
  • Number of Running Instances: 1
  • DB Replicaset Oplog:
  • NodeJS Version: v14.21.3
  • MongoDB Version: 5.0
  • Proxy: traefik
  • Firewalls involved:

Kind regards,
Leon

You don’t need to @ people thanks.

You would be better off with your own thread rather than jumping on an 8 month old one.

Then you don’t annoy the original posters how may not want to get lots of irrelevant notifications.

Please open a new thread and please provide some logs of the incident and I will try and get someone to have a look.

Thanks.