Description
Hello. I’m having a little trouble, so please help me.
(Translated from Japanese using DeepL.)
After testing the setup and operation of Rocket.Chat, I installed the server in the production environment, but the message “Workspace in read-only mode. Admins can restore full functionality by connecting it to the internet or upgrading to a premium plan.” appeared and I was unable to chat.
This is because, for security reasons, a proxy server must be set up with a whitelist to access external sites from within the organization’s local network. It is likely that the whitelist has not yet been registered, preventing access to Rocket.Chat’s authentication server and causing it to appear as an air-gapped environment.
Currently, connections to the “rocket.chat” domain are rejected as they are classified as belonging to the “chat app” category.
I searched the community for previously asked questions and found Community License server thinks it is air-gapped (but it's not) · Issue #33989 · RocketChat/Rocket.Chat · GitHub .
I believe that by adding collector.rocket.chat to the proxy server’s whitelist, Rocket.Chat will be able to access https://collector.rocket.chat/ for license authentication, thereby exiting read-only mode.
Is this correct? I would like to seek your expertise before submitting an incorrect whitelist addition request.
Additionally, could you please let me know which server I need to access in order to update Rocket.Chat in the future?
For now, I am considering adding *.snapcraft.io to the whitelist.
If anyone has experience setting up Rocket.Chat in a similar environment, could you please share how you are managing it?
Server Setup Information
- Version of Rocket.Chat Server: 7.5.0
- Operating System: Ubuntu Server 24.04 LTS
- Deployment Method: snap
- Number of Running Instances: 1
- DB Replicaset Oplog: -
- NodeJS Version: -
- MongoDB Version: -
- Proxy: i-Filter
- Firewalls involved: -