My workspace is identified as Airgapped when its not

Description:

My workspace is on the community version and keeps getting identified 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!

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:

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"}}