mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Can I use Uptime Kuma to ping private IPs from multiple locations? #2936
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#2936
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @djxcee on GitHub (Dec 18, 2023).
⚠️ Please verify that this bug has NOT been raised before.
🛡️ 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
@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.
@CommanderStorm commented on GitHub (Dec 18, 2023):
The reverse is possible:
You set up push monitors on your central instance and push heartbeats there after doing arbitrary checks.
@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.
@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.
@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.