support window notification

[wanderlage]

Actual behavior:

We received an email informing us that our workspace version is out of compliance. The current version is 6.7.1 which is in active support until October. The email states version 6.5.4. How to proceed?

Server Setup Information:

• Version of Rocket.Chat Server: 6.7.1
• Operating System:
• Deployment Method: Docker
• Number of Running Instances: 1
• DB Replicaset Oplog:
• NodeJS Version: v14.21.3
• MongoDB Version: 6.0.10 / wiredTiger (oplog Enabled)

Additional context

[xbiafra]

We have the same issue, currently we use the newest version 6.9.0

Non-admin user get this notification:

Whats more we were notified by email that we use v6.5.0 which is outside of our support window while it's not true.

[reetp]

I think your system is out of sync with your cloud panel.

See this:

https://forums.rocket.chat/t/received-msg-you-are-running-v6-5-0-which-is-outside-of-our-support-window/20082

Please check, and resync.

[xbiafra]

Hmm but how to do it if rocket is in state: Workspace registered

I can't find option to unregister or provide new token.

[reetp]

Have you checked

a) your workspace status in your cloud panel. Ensure you have the right server.

b) Admin/Subscription/Sync Licence Update

[geekgonecrazy]

Whats more we were notified by email that we use v6.5.0 which is outside of our support window while it's not true.

In your case you've registered the same workspace address with a couple of different accounts. Looks like a test account workspace is back on 6.5.0 and its alerting on that workspace.

For your case since you did include a screenshot containing workspace address i've fixed so you won't get emails about that workspace any more.

[wanderlage]

@geekgonecrazy ,

Where would we get information on what version the workspace (https://cloud.rocket.chat/) is? Why is it that when I synchronize (Sync License Update) an error is not returned.

[reetp]

The management panel at cloud.rocket.chat doesn't show your local registered version.

No idea why not.

If you sync your licence with no error you should be ok.

Check your logs and admin/info.

[github-actions[bot]]

This issue has been marked as stale because there has been no further activity in the last 10 days. If the issue remains stale for the next 4 days (a total of 14 days with no activity), then it will be assumed that the question has been resolved and the issue will be automatically closed.

[github-actions[bot]]

This issue was closed because it has been inactive for 14 days since being marked as stale.