How to disable clients periodic public ip check ICANHAZIP.COM plus other

[rabsym]

Hello all,

Sorry if already answered or available in docs but unable to find it.

Is there any way to disable clients periodic public ip check to the hosts?

ICANHAZIP.COM
IFCONFIG.CO
ICANHAZIP.TACTICALRMM.IO

Thanks in advance.
Rai

[P6g9YHK6]

https://docs.tacticalrmm.com/howitallworks/#outbound-firewall-rules_1

nope

if you really want to disable it add them to the hosts files via a script

or do a feature request to be able to customise it from global settings ;)

[silversword411]

Those are used to get the agents public IP for your admin panel.

[rabsym]

Nevermind, found the way, the trick is using CHECKIN_PUBIP variable in local_settings.py

Here is the full info from docs if anyone in the future is in the need...

Adjusting Agent Check-In Intervals

The agent periodically communicates with the RMM server, sending various data about its status and environment at random intervals. These randomized intervals are designed to prevent the "thundering herd" problem, where too many agents would check in simultaneously, potentially overloading the server.

You can modify these intervals by adding one or more of the following variables to /rmm/api/tacticalrmm/tacticalrmm/local_settings.py. Each variable is a Python tuple containing two values: the minimum and maximum interval times, specified in seconds. The agent will select a random interval within this range for each check-in.

The default check-in intervals are as follows:

CHECKIN_HELLO=(30,60) # Agent heartbeat ("I'm alive")
CHECKIN_AGENTINFO=(200,400) # System info (logged-in user, boot time, RAM, etc.)
CHECKIN_WINSVC=(2400,3000) # Windows services and their status
CHECKIN_PUBIP=(300,500) # Agent's public IP address
CHECKIN_DISKS=(1000,2000) # Disk information and usage
CHECKIN_SW=(2800,3500) # Installed Windows software list
CHECKIN_WMI=(3000,4000) # Asset details (as seen in the "Assets" tab)
CHECKIN_SYNCMESH=(800,1200) # Agent's Mesh node ID

By adjusting these intervals, you can control how frequently the agent checks in with the RMM server for different types of data. This flexibility allows for balancing between server load and the frequency of updates.

After adding any of these settings, you must restart both the RMM service (sudo systemctl restart rmm) and the agent service. An easy way to restart the agent service is by using the "Tools > Recover All Agents" function in the TRMM web UI.