Issues After Migrating Rocket.Chat to Docker on Debian 12 – Workspace Sync & Notifications Not Working

Community Support
1

Description

Hi everyone,

I recently migrated my Rocket.Chat instance from a bare-metal installation on Debian 11 to Debian 12 with Docker. Since the migration, several features, including push notifications and email functionality, are not working correctly.

My instance is registered in the Rocket.Chat Cloud Workspace, yet I keep receiving emails prompting me to update, even though my instance is already running the latest version inside the Docker container. This leads me to believe that the Workspace Cloud Sync is not functioning properly.

What I have tried so far:

:check_mark: Deleted the workspace registration and reset the settings → No success
:check_mark: The Admin Panel still shows the workspace as registered, meaning I cannot enter a new token for re-registration
:check_mark: Checked GitHub issues and previous forum posts → Found similar problems in older versions, but no clear solution

Symptoms:

  • Under Subscription in the Admin Panel, clicking “Sync License Update” results in the error:
    “Error during Workspace Sync”
  • No relevant error messages appear in the container logs

Has anyone encountered this issue before? Is there a way to force a re-registration or manually trigger a successful sync?

Any help would be greatly appreciated! :rocket:

Thanks in advance!

Server Setup Information

  • Version of Rocket.Chat Server: 7.4.1
  • Operating System: Debian
  • Deployment Method: docker
  • Number of Running Instances: 1
  • DB Replicaset Oplog: Enabled
  • NodeJS Version: 22.13.1
  • MongoDB Version: 6.0.13
  • Proxy: dedicated Haproxy
  • Firewalls involved: Yes

Any additional Information

Only Message in Logs for Failed Push:

{“level”:40,“time”:“2025-04-01T15:09:26.915Z”,“pid”:1,“hostname”:“ae21d8b25271”,“name”:“Push”,“msg”:“Error sending push to gateway (not authorized) ‘’”}

2

I found a workaround by manually resetting the workspace registration in the database using:

db.rocketchat_settings.remove({ "_id": /Cloud_/ })

After doing this, the workspace status was correctly set to “not registered”, and I was able to start the registration process again.

However, I am now stuck at Step 1 of the registration process. After entering my email and checking the required boxes, clicking “Next” does nothing. I can click the button repeatedly, but it does not proceed to the next step.
Error in Rocket.Chat Container Logs:

2025-04-01T16:33:31.815767385Z {"level":50,"time":"2025-04-01T16:33:31.815Z","pid":1,"hostname":"ae21d8b25271","name":"System","msg":"Failed to register workspace intent with Rocket.Chat Cloud","url":"/api/v2/register/workspace","err":{"type":"AbortError","message":"The user aborted a request.","stack":"AbortError: The user aborted a request.\n at abort (/app/bundle/programs/server/npm/node_modules/node-fetch/lib/index.js:1458:16)\n at AbortSignal.abortAndFinalize (/app/bundle/programs/server/npm/node_modules/node-fetch/lib/index.js:1473:4)\n at AbortSignal.dispatchEvent (/app/bundle/programs/server/npm/node_modules/event-target-shim/src/event-target.mjs:337:35)\n at abortSignal (/app/bundle/programs/server/npm/node_modules/abort-controller/src/abort-signal.ts:68:12)\n at AbortController.abort (/app/bundle/programs/server/npm/node_modules/abort-controller/src/abort-controller.ts:26:9)\n at Timeout.<anonymous> (/app/bundle/programs/server/npm/node_modules/@rocket.chat/server-fetch/src/index.ts:43:48)\n at listOnTimeout (node:internal/timers:594:17)\n at processTimers (node:internal/timers:529:7)","name":"AbortError"}}

Has anyone encountered this issue before? Could this be related to a timeout, network issue, or something cached from the previous registration?