# Server thinks it's air gapped, but it's not!

**URL:** <https://forums.rocket.chat/t/server-thinks-its-air-gapped-but-its-not/22438>\
**Category:** Community Support\
**Created:** [August 12, 2025, 8:23pm UTC](https://forums.rocket.chat/t/server-thinks-its-air-gapped-but-its-not/22438 "2025-08-12T20:23:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sobeguy](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/sobeguy/32/5860_2.png) [@sobeguy](https://forums.rocket.chat/u/sobeguy)\
**Post date:** [August 12, 2025, 8:23pm UTC](https://forums.rocket.chat/t/server-thinks-its-air-gapped-but-its-not/22438/1 "2025-08-12T20:23:15Z")

</div>

I’ve been running a Rocket.Chat server for about the past six months. It’s always worked fine, but several days ago, I started getting notices that the server is air gapped and would soon enter readonly mode.

- This is a snap install running on an AWS virtual server.
- The server has connectivity to the Internet. It has a public IP address and there is no firewall or anything preventing it from making outgoing connections.
- I can connect to collector.rocket.chat via CURL from the server’s command line.
- When I view the rocketchat\_statistics collection in Mongo, I can see that it has failed to obtain a token for the past several days, but it was collecting the token up until then.
- Nothing changed on the server that would affect connectivity to collector.rocket.chat and as I explained, I can connect to it from the command line.
- I see the following log entry each time it attempts to post stats:

```json
{
    "level": 50,
    "time": "2025-08-10T15:07:20.652Z",
    "pid": 20560,
    "hostname": "ip-172-26-2-85",
    "name": "SyncedCron",
    "msg": "Failed to send usage report",
    "err": {
        "type": "FetchError",
        "message": "invalid json response body at https://collector.rocket.chat/ reason: Unexpected end of JSON input",
        "stack": "FetchError: invalid json response body at https://collector.rocket.chat/ reason: Unexpected end of JSON input\n at /snap/rocketchat-server/1677/programs/server/npm/node_modules/node-fetch/lib/index.js:273:32\n at processTicksAndRejections (node:internal/process/task_queues:105:5)\n at sendStats (app/statistics/server/functions/sendUsageReport.ts:25:26)\n at usageReportCron (server/cron/usageReport.ts:19:21)\n at async Promise.all (index 2)\n at startCronJobs (server/startup/cron.ts:15:2)",
        "name": "FetchError"
    }
}

```

### Server Setup Information

- Version of Rocket.Chat Server: 7.9.0
- Operating System: Ubuntu 24
- Deployment Method: Snap
- Number of Running Instances:1
- DB Replicaset Oplog: ???
- NodeJS Version: Not sure
- MongoDB Version: 6.0.19
- Proxy: No
- Firewalls involved: No

---

<div class="post-metadata">

**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:** [August 12, 2025, 9:10pm UTC](https://forums.rocket.chat/t/server-thinks-its-air-gapped-but-its-not/22438/2 "2025-08-12T21:10:40Z")

</div>

Posting in multiple places with no linked references in the hope of eliciting a response just wastes time.

This is you down here.

> <https://github.com/RocketChat/Rocket.Chat/issues/36249#issuecomment-3179854493>
>
> \### Description:
> 
> My workspace is on the community version and keeps getting ide…ntified as airgapped when its not, we all access it via the internet.
> From within the server we can curl to the metrics curl -v https://collector.rocket.chat - this works!
> 
> !\[Image\](https://github.com/user-attachments/assets/594a99fb-80bb-4f6a-ab4b-af3d33c12d51)
> 
> \### Steps to reproduce:
> 
> 1. create a new instance on the 7.7.1 on the community version
> 2. wait 7 days (maybe just 24 hrs)
> 3. problem will show in the logs, after 7 days in screen
> 
> \### Expected behavior:
> 
> Workspace is not identified as airgapped!
> 
> \### Actual behavior:
> 
> !\[Image\](https://github.com/user-attachments/assets/2274a079-267e-477a-9c42-06e5c33b6d2b)
> 
> 
> \### Server Setup Information:
> 
> \- Version of Rocket.Chat Server: 7.7.1
> \- License Type: community
> \- Number of Users: 300+
> \- Operating System: linux
> \- Deployment Method: k8s
> \- Number of Running Instances: 1
> \- DB Replicaset Oplog: 1
> \- NodeJS Version: 20
> \- MongoDB Version: 8
> 
> \### Client Setup Information
> 
> \- Desktop App or Browser Version:
> \- Operating System:
> 
> \### Additional context
> 
> This already happened before and we moved to a new mongo colletion, but now is happening again.
> 
> \### Relevant logs:
> 
> From the Server:
> 
> {"level":50,"time":"2025-06-19T16:12:04.285Z","pid":1,"hostname":"rocketchat-86bc6b554f-bp562","name":"SyncedCron","msg":"Failed to send usage report","err":{"type":"FetchError","message":"invalid json response body at https://collector.rocket.chat/ reason: Unexpected end of JSON input","stack":"FetchError: invalid json response body at https://collector.rocket.chat/ reason: Unexpected end of JSON input\\n at /app/bundle/programs/server/npm/node\_modules/node-fetch/lib/index.js:273:32\\n at processTicksAndRejections (node:internal/process/task\_queues:105:5)\\n at sendStats (app/statistics/server/functions/sendUsageReport.ts:25:26)\\n at server/cron/usageReport.ts:25:22\\n at runCronJobFunctionAndPersistResult (/app/bundle/programs/server/npm/node\_modules/@rocket.chat/cron/src/index.ts:14:18)\\n at Object.fn (/app/bundle/programs/server/npm/node\_modules/@rocket.chat/cron/src/index.ts:130:4)\\n at /app/bundle/programs/server/npm/node\_modules/@rocket.chat/agenda/src/Job.ts:252:6","name":"FetchError"}}

If you have a paid version then open a support ticket. If not you’ll have to hope someone takes a look when they have a free minute.

Note downgrades are not supported and may wreck your install. The only safe way is via backup/restore with the correct vesrsions.

In the meantime to save confusion please stick to the bug. Thanks.