this post was submitted on 24 Mar 2026
33 points (94.6% liked)
Selfhosted
60409 readers
772 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Uptime Kuma has a number of notification options.
I just had to set one up because the Oracle free tier is hot garbage and needs resetting every day or two.
I use uptime Kuma with signal-cli for notifications - it's been rock solid. I also have anotger uptime kuma that uses email as notification option to monitor my primary uptime kuma and the signal-cli.
+1 for Uptime Kuma, I use it with ntfy. If OP doesn't want a self hosted solution, there's UptimeRobot - essentially SAAS Uptime Kuma, but with a free tier.
I haven't touched my Oracle in months. What exactly is happening?
No idea. The dashboard says it's running and fine, sometimes the shell console is ok, sometimes it's also bogged down, but the instance is completely non-responsive from outside. The other instance I have in the same tenancy but a different fault domain is perfectly fine, so I don't know if that's related somehow. I'm running Pangolin on it to forward a couple things, one of them is higher throughput than I had expected, but rebooting makes it come back, so I don't think they're throttling me.
I'm kind of at a loss, but I threw together a webhook to use their API to reboot it when it stops responding and that seems to be working while not actually addressing whatever the root cause is.