Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to communicate with Rocket.Chat Cloud because the domain is blocked in mainland China #34863

Closed
HanadaLee opened this issue Jan 2, 2025 · 4 comments

Comments

@HanadaLee
Copy link

HanadaLee commented Jan 2, 2025

{"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 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?

image
image
image

@HanadaLee
Copy link
Author

Due to the above problems, I have rolled back to version 6.13.1 and look forward to a suitable solution.

@reetp
Copy link

reetp commented Jan 2, 2025

@reetp reetp closed this as not planned Won't fix, can't repro, duplicate, stale Jan 2, 2025
@HanadaLee
Copy link
Author

Does this mean that the community version of Rocket.Chat will no longer be available to users in mainland China?

@reetp
Copy link

reetp commented Jan 2, 2025

No.

It means if you want to operate offline/air gapped you either need

  • An offline licence - contact sales

  • You will have to build your own version from the open source code and remove any registration code etc.

(Don't shoot the messenger - I don't work for Rocket.Chat !)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants