Can I use Uptime Kuma to ping private IPs from multiple locations? #2936

Closed
opened 2026-02-28 03:12:11 -05:00 by deekerman · 5 comments
Owner

Originally created by @djxcee on GitHub (Dec 18, 2023).

⚠️ Please verify that this bug has NOT been raised before.

  • I checked and didn't find similar issue

🛡️ Security Policy

📝 Describe your problem

I am trying to see if I can use Uptime Kuma to do a basic ping on devices to private IPs from multiple locations. I can setup containers at each location but not sure how I would accomplish this, without a VPN setup.

Any suggestions would be appreciated!

📝 Error Message(s) or Log

No response

🐻 Uptime-Kuma Version

1..23.10

💻 Operating System and Arch

Ubuntu 22.04.3

🌐 Browser

Google Chrome 120.

🐋 Docker Version

No response

🟩 NodeJS Version

No response

Originally created by @djxcee on GitHub (Dec 18, 2023). ### ⚠️ Please verify that this bug has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### 📝 Describe your problem I am trying to see if I can use Uptime Kuma to do a basic ping on devices to private IPs from multiple locations. I can setup containers at each location but not sure how I would accomplish this, without a VPN setup. Any suggestions would be appreciated! ### 📝 Error Message(s) or Log _No response_ ### 🐻 Uptime-Kuma Version 1..23.10 ### 💻 Operating System and Arch Ubuntu 22.04.3 ### 🌐 Browser Google Chrome 120. ### 🐋 Docker Version _No response_ ### 🟩 NodeJS Version _No response_
deekerman 2026-02-28 03:12:11 -05:00
Author
Owner

@chakflying commented on GitHub (Dec 18, 2023):

If you have devices in a private network, but you expect to be able to access them outside, there must be some mechanism for you to bridge the networks together. It would only make sense to run monitoring over the same method you access them. So I don't see why you would want to do this without a VPN.

You can use something like tailscale to avoid the complications of setting up a VPN yourself.

@chakflying commented on GitHub (Dec 18, 2023): If you have devices in a private network, but you expect to be able to access them outside, there must be some mechanism for you to bridge the networks together. It would only make sense to run monitoring over the same method you access them. So I don't see why you would want to do this without a VPN. You can use something like tailscale to avoid the complications of setting up a VPN yourself.
Author
Owner

@CommanderStorm commented on GitHub (Dec 18, 2023):

do a basic ping on devices to private IPs from multiple locations

The reverse is possible:
You set up push monitors on your central instance and push heartbeats there after doing arbitrary checks.

@CommanderStorm commented on GitHub (Dec 18, 2023): > do a basic ping on devices to private IPs from multiple locations The reverse is possible: You set up push monitors on your central instance and push heartbeats there after doing arbitrary checks.
Author
Owner

@djxcee commented on GitHub (Dec 19, 2023):

Hi @CommanderStorm, I was thinking the same without the need to setup a VPN/Bridge.

However, I look at Monitor Types and I only see ping without additional Types to perform per device. Trying to see how I would do a Ping then notifify a Push to our primary Uptime Kuma instance.

@djxcee commented on GitHub (Dec 19, 2023): Hi @CommanderStorm, I was thinking the same without the need to setup a VPN/Bridge. However, I look at Monitor Types and I only see ping without additional Types to perform per device. Trying to see how I would do a Ping then notifify a Push to our primary Uptime Kuma instance.
Author
Owner

@CommanderStorm commented on GitHub (Dec 20, 2023):

Push monitors require you to do arbitrary checks. The other monitoring types are not avaliable for remote execution. See #84 for further discussion.
=> you write a small shell/python/... script that defines what is up and pushes a heartbeat to the url defined by the push monitor in Uptime Kuma if it is.

@CommanderStorm commented on GitHub (Dec 20, 2023): Push monitors require you to do arbitrary checks. The other monitoring types are not avaliable for remote execution. See #84 for further discussion. => you write a small shell/python/... script that defines what is up and pushes a heartbeat to the url defined by the push monitor in Uptime Kuma if it is.
Author
Owner

@github-actions[bot] commented on GitHub (Feb 19, 2024):

We are clearing up our old help-issues and your issue has been open for 60 days with no activity.
If no comment is made and the stale label is not removed, this issue will be closed in 7 days.

@github-actions[bot] commented on GitHub (Feb 19, 2024): We are clearing up our old `help`-issues and your issue has been open for 60 days with no activity. If no comment is made and the stale label is not removed, this issue will be closed in 7 days.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#2936
No description provided.