# "Failed to communicate with Rocket.Chat Cloud" "The user aborted a request." **URL:** \ **Category:** Community Support\ **Created:** [December 27, 2025, 4:27pm UTC](https://forums.rocket.chat/t/failed-to-communicate-with-rocket-chat-cloud-the-user-aborted-a-request/22654 "2025-12-27T16:27:20Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![mkm](https://avatars.discourse-cdn.com/v4/letter/m/edb3f5/32.png) [@mkm](https://forums.rocket.chat/u/mkm)\ **Post date:** [December 27, 2025, 4:27pm UTC](https://forums.rocket.chat/t/failed-to-communicate-with-rocket-chat-cloud-the-user-aborted-a-request/22654/1 "2025-12-27T16:27:21Z")
### 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](https://releases.rocket.chat/v2/server/supportedVersions%22,%22err%22:%7B%22type%22:%22AbortError%22,%22message%22:%22The) 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](https://forums.rocket.chat/groups/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: ```bash 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`). ---
**Author:** ![reetp](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/reetp/32/5546_2.png) [@reetp](https://forums.rocket.chat/u/reetp)\ **Post date:** [December 27, 2025, 6:04pm UTC](https://forums.rocket.chat/t/failed-to-communicate-with-rocket-chat-cloud-the-user-aborted-a-request/22654/2 "2025-12-27T18:04:08Z")
Worth doing some proper reading. You’re out of luck and the message is correct. > **[Rocket Chat Version Durability Policy](https://docs.rocket.chat/docs/version-durability)** > > Explore Rocket Chat version durability policies. Ensure secure communications and supported deployments. ---
**Author:** ![mkm](https://avatars.discourse-cdn.com/v4/letter/m/edb3f5/32.png) [@mkm](https://forums.rocket.chat/u/mkm)\ **Post date:** [December 27, 2025, 7:27pm UTC](https://forums.rocket.chat/t/failed-to-communicate-with-rocket-chat-cloud-the-user-aborted-a-request/22654/3 "2025-12-27T19:27:59Z")
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. ---
**Author:** ![reetp](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/reetp/32/5546_2.png) [@reetp](https://forums.rocket.chat/u/reetp)\ **Post date:** [December 27, 2025, 11:07pm UTC](https://forums.rocket.chat/t/failed-to-communicate-with-rocket-chat-cloud-the-user-aborted-a-request/22654/4 "2025-12-27T23:07:30Z")
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) > **[Release 7.13.2 · RocketChat/Rocket.Chat](https://github.com/RocketChat/Rocket.Chat/releases/tag/7.13.2)** > > Engine versions > > Node: 22.16.0 > Deno: 1.43.5 > MongoDB: 5, 6, 7, 8 > Apps-Engine: 1.58.0 > > Patch Changes > > > Bump @rocket.chat/meteor version. > > > Bump @rocket.chat/meteor version. > > > (#37876 by @dionisio-bot...