Tactical RMM Troubleshooting

Common Issues

Date and Time Synchronization

Ensure that your date/time is properly configured. Replace Asia/Manila with your own time zone. You can set the time zone using the commands below.

To set the time zone:

sudo timedatectl set-timezone Asia/Manila

To set the time:

timedatectl set-time 21:45:53

To set the date:

timedatectl set-time 2025-03-31

Server Troubleshooting Script

While this script can help you to check what goes wrong, Tactical RMM has a discord server where you can also ask for help.

First, ensure that dig is installed via the dnsutils package:

sudo apt update && sudo apt install -y dnsutils

Next, download and run the troubleshooting script:

wget -N https://raw.githubusercontent.com/amidaware/tacticalrmm/develop/troubleshoot_server.sh
chmod +x troubleshoot_server.sh
./troubleshoot_server.sh

Updating the server through their update script can also help fix most of the post-install issues:

Download the update script and run it:

wget -N https://raw.githubusercontent.com/amidaware/tacticalrmm/master/update.sh
chmod +x update.sh
./update.sh

If you are already on the latest version, the update script will notify you of this and return immediately.

You can pass the optional --force flag to the update script to forcefully run through an update, which will bypass the check for latest version.

wget -N https://raw.githubusercontent.com/amidaware/tacticalrmm/master/update.sh
chmod +x update.sh
./update.sh --force

This is useful for a botched update that might have not completed fully.

The update script will also fix any permissions that might have gotten messed up during a botched update, or if you accidentally ran the update script as the root user.

Make sure DNS (name resolution) was setup properly

If you're having trouble installing agent or connecting to the client device, make sure you can ping the 3 subdomains you set in the installation. You can test it by pinging the subdomains from the agent/client device.

ping rmm.example.com

ping mesh.example.com

ping api.example.com 

Check RMM Services

Check all the systemd services that the rmm uses to function and check to make sure they're all active / running and enabled:

sudo systemctl status rmm.service
sudo systemctl status daphne.service
sudo systemctl status celery.service
sudo systemctl status celerybeat.service
sudo systemctl status nginx.service
sudo systemctl status nats.service
sudo systemctl status nats-api.service
sudo systemctl status meshcentral.service
sudo systemctl status mongod.service
sudo systemctl status postgresql.service
sudo systemctl status redis-server.service

Or you can use systemctl --failed to see any failed services on your machine.

Read through the log files in the following folders and check for errors:

/rmm/api/tacticalrmm/tacticalrmm/private/log
/var/log/celery

Need to recover your Mesh token?

Login to server with SSH and run:

node /meshcentral/node_modules/meshcentral --logintokenkey