RocketChat 7.3.0 - Forced Readonly Mode

Community Support
1

Description

Our rocket chat instance has been switching to read-only mode once a day due to it thinking it is an air-gapped instance. A quick reboot of the server fixes the issue, however, it continues to occur on the daily. Based on current pattern, this occurs just once a day at about the same time. Does anyone have an idea of best approach to troubleshoot this issue? Are there any specific logs to take a look at which could help understand the root cause?

Quick context: This is not an airgapped instance. We have been running Rocket Chat since version 4.0. Everything has been running fine until latest upgrade to version 7 (this was a direct upgrade from 6.x → 7.3). Interestingly, it wasn’t until around a week after upgrading to 7.3 that we started to get air-gapped/readonly mode condition. There has been no change to any of the underlying networking setup since it has been stood up (proxy, fw, etc.).

Any help would be greatly appreciated!

Server Setup Information

  • Version of Rocket.Chat Server: 7.3.0
  • Operating System: Debian 12
  • Deployment Method: Docker
  • Number of Running Instances: 1
  • DB Replicaset Oplog:
  • NodeJS Version:
  • MongoDB Version: 5.0
  • Proxy: nginx
  • Firewalls involved:

Any additional Information

2

There were bug changes after 6.5, and 7.

How many users?

What licence?

Does your licence sync? What do your logs say?

Did you read tge release notes & changelogs? Generally you must be connected online now with a cloud account.

3

Hi Reetp, thank you for your reply! We have around 100 users and it is a standard community plan (self hosted). Looks like the license is synced on the workspace section. It also looks like the issue is now resolved, whatever it was. It has been several days now that we have not seen this occur, so I’m hoping it was a temporary problem. I will advise again with more input and information if we see this occur more.

Thank you very much, I greatly appreciate ya Reetp!

1 Like