Hi, is there any new information regarding my problem? GitHub issue #41714 is marked as resolved, but I’m not getting a reply to my question.
My Licence is not valid for 8.7.0
Logon mongo:
use rocketchat
db.rocketchat_settings.findOne(
{_id:“Enterprise_License”},
{value:1}
).value
Result is RCV3_WERT token
Execute python3 with RCV3_WERT
python3 - <<‘PY’
import base64, json
token = “”“HIER_DEN_VOLLSTÄNDIGEN_RCV3_WERT_EINFÜGEN”“”
jwt = token.removeprefix(“RCV3_”)
parts = jwt.split(“.”)
payload = parts[1]
payload += “=” * (-len(payload) % 4)
data = json.loads(base64.urlsafe_b64decode(payload))
print(“offline =”, data.get(“information”, {}).get(“offline”))
PY
Result:
offline = True
I need an License with offline = False.
Where can correct my licence *?
This is the answer.
You need to create a new licence and use it.
You probably have to delete the old one first. If you did what I just did and read the docs you would find this:
And why? At a guess you did something odd to start with. No idea what but I’d guess you tried an offline setup somehow.
Starting from Rocket.Chat 8.7
I’d also imagine from reading the docs that they changed something in 8.7.x - possibly a license bug fix and caught you out.
Hi, thanks for your answer.
Thanks for your reply. I have been running this Rocket.Chat workspace for about two years and have only performed normal Docker image upgrades. I have never intentionally configured the workspace as offline or air-gapped.
The workspace is registered online and Cloud Push worked correctly with 8.6.1. After upgrading to 8.7.0, the existing license is now interpreted as offline=true, which disables the Push Gateway.
Would it be possible for Rocket.Chat to correct or re-issue the license for the existing workspace in the Cloud portal, so that I can then use Sync license update in the admin interface to retrieve the corrected license?
I would prefer not to delete and re-register the workspace unless this is officially required, because the registration itself has been working correctly for years.
You have already been told this:
Fix is: re-register online
That’s it. The cloud workspace will issue a new new license - read the manual.
I have no idea what you did to get to this place and I haven’t seen any other issues. Something you did when you set it up, or when you changed something.
But there is only one fix, and that is creating a new license which you can do in the cloud panel.
I think when you “Register self-managed” you will get a trial Pro license which will automatically downgrade to Starter after 30 days.
Hi, thanks for the quick response.
I’m just a bit hesitant because I want to avoid a situation where, if something goes wrong during the re-registration, I end up having to rebuild the entire installation from scratch.
I’ve been running and maintaining this Rocket.Chat workspace for about two years, so losing the existing setup over a licensing issue would be very frustrating.
I’m absolutely a fan of Rocket.Chat, but I’d really like to preserve the current installation and only change what is strictly necessary to get the license back into a correct state.
That’s the only way.
Nothing else I can do - I got you the official response from Casals who works at Rocket.
Without paid support, that’s it.
It’s just a new license. That’s all.
AFAIAA delete the old, create and add new. It is free… 
I’ve started the re-registration process. As I predicted, it isn’t working. I’m now getting the following windows alternately, and I can no longer access the application. Instead, I’m constantly receiving welcome emails for the “Starter Edition.”
You can give Rocket.Chat my regards—they managed to break a working installation with their fix.
Loop
You do remember that RocketChat is open source?
It costs you absolutely nothing, but you are profiting from the use of it?
No, they didn’t. As above yours was already broken. It’s just that the update (which you didn’t appear to to test) enforced a setting that had been there a long time.
Your install/license was already broken if you read the whole thread. That’s why you opened it and created a github issue.
I have already said that this is likely self inflicted - possibly when you first set up the server - probably messing about with airgapped at a guess (which first appeared around 6.5)
You have had other issues with this install IIRC so I’m pretty sure this goes back a long way.
I have also seen no other queries relating to this.
The only solution is to generate a new key and add it to Rocket because the original license you created was wrong.
Someone may or may not get back to you. I can’t guarantee anything. But being rude to Rocket won’t help you.
Hello, “Black Monday” is over. Rocket.Chat is now running with a new license—configured with offline = False—on version 8.7.0, and with a functioning push gateway. Thanks, Rocket.Chat, for the gray hairs that PR #41148 caused me during my installation process.
A huge thank you to you, too, reetp; you really had to go through a lot, but your words gave me the motivation to fix everything today. It was also great that you were able to ask a Rocket.Chat employee for support.
Since the error lay with the “old issued license,” I assume others will run into this same problem with “old” licenses. Deleting everything in the cloud space and re-registering from scratch is indeed a viable solution, though the manuals don’t offer much guidance on this. Thanks to Claude and ChatGPT, the crisis has been averted.
Regarding the loop error I described: once I verified that all licenses had been transmitted correctly, I was able to disable it by running the following command in MongoDB:
db.rocketchat_settings.updateOne(
{_id:“Show_Setup_Wizard”},
{$set:{value:“completed”}}
)
That’s all from me—until next time.
Here are the important checks.
First Read Licence from Mongo (Output: TOKEN)
/*
db.rocketchat_settings.findOne(
{ _id: “Enterprise_License” },
{ value: 1 }
).value
*/
Second Check Offline value in licence
/*
python3 - <<‘PY’
import base64, json
token = “”“TOKEN”“”
jwt = token.removeprefix(“RCV3_”)
parts = jwt.split(“.”)
payload = parts[1]
payload += “=” * (-len(payload) % 4)
data = json.loads(base64.urlsafe_b64decode(payload))
print(“offline =”, data.get(“information”, {}).get(“offline”))
PY
*/
offline = False (works)
offline = True (not working)
Thanks, Thanks, Thanks
Cool.
I have said more than once I suspect that you did something unusual when you first started - possibly trying airgapped mode. You have never mentioned this but it is the only way I can think of it occurring. All good, until they enforce it.
Yup - as suggested.
Regarding the docs you should fill out the bit at the bottom of the license page where it says ‘Was this article helpful’ and say ‘no’ and write your comment out - it will get looked at. Your bit of ‘giving back’ to open source.