"Failed to communicate with Rocket.Chat Cloud" "The user aborted a request."

Community Support
1

Description

I’ve started my first rocket.chat setup, and I’m self-hosting using docker + nginx. I observed when trying to connect the mobile app to my server that the app fails with the message “Rocket.Chat is running an unsupported version of Rocket.Chat.” That seemed unlikely, since I’m on 7.5.0, so I looked at the logs with docker compose logs rocketchat and saw Failed to communicate with Rocket.Chat Cloud with the detail The user aborted a request. (More log given below.) That’s a surprise. I have no awareness of aborting a request as a user. Anyone have insight?

Server Setup Information

  • Version of Rocket.Chat Server: 7.5.0
  • Operating System: Ubuntu 24.04
  • Deployment Method: self-hosted docker
  • Number of Running Instances: 1
  • DB Replicaset Oplog: Enabled
  • NodeJS Version: 22.13.1 - x64
  • MongoDB Version: 6.0.13
  • Proxy: nginx
  • Firewalls involved: n/a

Any additional Information

Here’s what my docker logs show.

rocketchat-1 | {“level”:50,“time”:“2025-12-27T03:45:25.333Z”,“pid”:1,“hostname”:“b5b69cd52327”,“name”:“Rocket.Chat Apps”,“msg”:“Error getting the app requests stats from marketplace ‘’”}
rocketchat-1 | {“level”:50,“time”:“2025-12-27T12:00:20.050Z”,“pid”:1,“hostname”:“b5b69cd52327”,“name”:“System”,“msg”:“Failed to communicate with Rocket.Chat Cloud”,“url”:“https://releases.rocket.chat/v2/server/supportedVersions",“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. (/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”}}

I seem to have no firewall problems. I can curl a successful response from https://releases.rocket.chat/v2/server/supportedVersions from within my docker container:

docker compose exec -u root rocketchat sh
$ apk add curl
$ curl https://releases.rocket.chat/v2/server/supportedVersions

I’m using nginx as the gateway for incoming requests, though I don’t suppose that’s implicated. I started up the containers with docker compose -f compose.database.yml -f compose.monitoring.yml -f compose.yml up -d (omitting compose.traefik.yml).

2

Worth doing some proper reading.

You’re out of luck and the message is correct.

3

Thanks, @reetp. I had a bit of a mental disconnect (based my earlier choice of v7.5 on the example from the installation guide).

I’ve updated to 7.13.0 and no longer see any error in my docker logs.

4

For your own security I’d ALWAYS use the latest point version unless you have a specific reason not too. Eg 7.13.2

Always read the releaese notes (reading is so important)