agent count always shows zero

[daorlov]

Good day everyone, in the upper right corner it always shows zero, although agents are active, and the icons opposite them are green

[dinger1986]

how did you install?

[Avessalom608]

@dinger1986
The installation was traditional, without any changes. Option 1: Easy installation on VPS. In protected mode

[dinger1986]

what does protected mode mean?

[Avessalom608]

@dinger1986

what does protected mode mean?

Run install.sh without the key --insecure

[silversword411]

Here's what I'd recommend.
Reboot
From the correct user, run your ./update.sh --force
To fix what I'd guess is probably broken permissions on the server at a minimum.

If it's still broken, open a ticket with support
https://docs.tacticalrmm.com/support/#commercial-support

and setup ssh access (lower in the page) and we'll login and have a look.

Include the sequence of events from when it was working, to when it broke.

[Avessalom608]

Unfortunately, running the script did not produce results, but thanks for the answer

[lqdmist]

Any solution? I just updated to 0.19.1 in the hope this would be fixed but no.

[dinger1986]

did you use --insecure when you installed?

[lqdmist]

No but the issue was already present before updating, I thought maybe the update would fix this.

[wh1te909]

this is not a bug with the software, there's no issues with agent counts showing 0. something specific to your install or system.

[silversword411]

Do you have another proxy/load balancer in front of the server processing traffic on 443?

You haven't given any technical details on your install other than didn't use --insecure
https://docs.tacticalrmm.com/faq/#if-you-received-this-link

[lqdmist]

The agent count was showing the correct value before. The (Debian 12) VM experienced a sudden crash resulting in a read-only file system (the cause of this is still unknown). Rebooting this VM brought the application back up and running except for the agent count.
The application is installed natively (no docker), so only the default Nginx is listening on 443.
We ran the troubleshooting script which didn't notice any issues