Selfhosted
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: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
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!
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 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.
Same here. Run it on my VPS to test my outside reachability and inside to check against my VPS.
This is what I use, though I run it on a local server that checks services that it runs (update breaks something, etc) and then also reaches out to the vps (and more) for status checks. Have it check services that are accessible by an access control rule, so the server is protected but you have updates on exactly what is having issues.
I use uptime Kuma with signal-cli for notifications - it's been rock solid. I also have another uptime kuma instance 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.