Description
{"level":50,"time":"2025-01-02T02:24:04.005Z","pid":1,"hostname":"a91c12bcf8dd","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/server-fetch/src/index.ts:43:48)\n at listOnTimeout (node:internal/timers:581:17)\n at processTimers (node:internal/timers:519:7)","name":"AbortError"}}
I noticed that in the latest version, rocketchat requires a connection to releases.rocket.chat. However, this domain is completely banned in mainland China (DNS resolution is polluted, HTTPS requests are reset), so it is impossible to connect to releases.rocket.chat in mainland China.
However, due to the mandatory requirements of the latest version of the instance, all rocketchat instances running in mainland China are forced to enter a read-only state.
Is there any way to solve this problem, or will no longer be able to run any community version rocketchat instances in mainland China in the future?
Server Setup Information
- Version of Rocket.Chat Server: 7.0.0
- Operating System: Centos 7
- Deployment Method: docker
- Number of Running Instances: 1
- DB Replicaset Oplog: Enabled
- NodeJS Version: unknown
- MongoDB Version: 5.0
- Proxy: nginx
- Firewalls involved: none
Any additional Information
None
