[GH-ISSUE #2203] [Feature Request] custom icanhazip server #3310

New issue

Open

opened 2026-03-14 07:06:14 +03:00 by kerem · 1 comment

kerem commented

2026-03-14 07:06:14 +03:00

Owner

Originally created by @P6g9YHK6 on GitHub (Apr 9, 2025).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2203

Is your feature request related to a problem? Please describe.
currently all agents uses icanhazip.tacticalrmm.io for the public ip information and this is not customizable as hardcoded into the agent.

Describe the solution you'd like

and i could push the thing a bit futher: the trmm server should have a icanhazip endpoint in the api/web as some people would not need an external if they never uses it in lan while default could always stay icanhazip.tacticalrmm.io for everyone else.

Describe alternatives you've considered
changing hosts file on all agent to point icanhazip.tacticalrmm.io to another ip of a server with "icanhazip.tacticalrmm.io" as a vhost.

Originally created by @P6g9YHK6 on GitHub (Apr 9, 2025). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2203 **Is your feature request related to a problem? Please describe.** currently all agents uses icanhazip.tacticalrmm.io for the public ip information and this is not customizable as hardcoded into the agent. **Describe the solution you'd like** ![Image](https://github.com/user-attachments/assets/e0858dab-f135-48cc-8644-58b2d88d1217) and i could push the thing a bit futher: the trmm server should have a icanhazip endpoint in the api/web as some people would not need an external if they never uses it in lan while default could always stay icanhazip.tacticalrmm.io for everyone else. **Describe alternatives you've considered** changing hosts file on all agent to point icanhazip.tacticalrmm.io to another ip of a server with "icanhazip.tacticalrmm.io" as a vhost.

kerem commented

2026-03-14 07:06:20 +03:00

Author

Owner

@vladyspavlov commented on GitHub (Apr 16, 2025):

It would be nice to have an option to disable the public IP check and completely hide the field in the dashboard for all agents, either in the global settings or in local_settings.py. This is useful when Tactical is used with agents on a single LAN or VPN.

I’m aware of the CHECK_PUBIP setting in local_settings.py, but it’s not a very clear workaround for this use case.

@vladyspavlov commented on GitHub (Apr 16, 2025): It would be nice to have an option to disable the public IP check and completely hide the field in the dashboard for all agents, either in the global settings or in local_settings.py. This is useful when Tactical is used with agents on a single LAN or VPN. I’m aware of the CHECK_PUBIP setting in local_settings.py, but it’s not a very clear workaround for this use case.