I was looking at an #uptimekuma replacement, since mine often hangs.
Decided to actually go look at the settings - 1.6gb of sqlite and 180 days of retention probably doesn't help... Let's bring that down a bit.
Recent searches
Search options
Administered by:
#uptimekuma
1 post1 participant0 posts today
UptimeKuma 2.0.0-beta.2 has been published!
Release notes are available here: https://github.com/louislam/uptime-kuma/releases/tag/2.0.0-beta.2
UptimeKuma 2.0.0-beta.2-temp has been published!
Release notes are available here: https://github.com/louislam/uptime-kuma/releases/tag/2.0.0-beta.2-temp
Today I hate #SQLite deeply. The idea of having a single point of failure for your entire data is absurd. This marks the third time I have to configure from scratch my endpoints in #UptimeKuma
New addition to my self hosting list: #healthchecks to monitor #backups and Uptime Kuma to monitor endpoints
I'm curious to hear what others are #SelfHosting! Here's my current setup:
Hardware & OS
- Hardware: #RaspberryPi500 (8 GB RAM, 512 GB SD card) #RPi #RPi500 #SingleBoardComputers #HomeLab
- OS: #Stormux, an accessible #Linux distro based on #ArchLinuxARM #LinuxAccessibility #AccessibleTech
Infrastructure & Networking
- Dashboard: #Glance (#Docker) #DockerApps
- Reverse Proxy: #Caddy
- DNS: #Cloudflare
- Domain Registrar: #Porkbun
- Networking & Remote Access: #Tailscale (non-Docker), love its SSH agent and magic DNS features. #NetworkSecurity
Security & Monitoring
- Ad Blocking: #AdGuardHome (non-Docker). Previously used PiHole but find AdGuardHome slightly faster. #PrivacyTools
- Server Monitoring: #Beszel (non-Docker). Tried Grafana/Prometheus/Alertmanager (accessible but overkill) and Netdata (poor screen reader accessibility). Beszel isn't perfect but best compromise so far. #ServerMonitoring
- Server Overview: #Cockpit (non-Docker)
- Security Tools: #Fail2ban, #FirewallD, #ClamAV, and #Rkhunter (non-Docker). Tried CrowdSec but couldn't get it working on Stormux. #CyberSecurity
- Service Uptime Monitoring: #UptimeKuma (Docker), accessible and easy to use. #MonitoringTools
Authentication & Identity Management
- Authelia (Docker): Just set this up for two-factor authentication and single sign-on. Seems to be working well so far!
- LLDAP (Docker): Lightweight LDAP server for managing authentication. Also seems to be working pretty well!
#AuthenticationTools #IdentityManagement
Productivity & Personal Tools
- Docker Management: #Dockge (Docker). More accessible than Portainer; main issue is built-in terminal isn't readable with screen readers. #DockerCompose
- Docker Logs Viewer: #Dozzle (Docker), great web interface and easy searching.
- Git Hosting: #Forgejo (non-Docker), my personal Git server. #GitServer
- Backups: #IDrive (non-Docker), backs up all my devices easily. #BackupSolutions
- Notes: #Joplin server (Docker). Accessibility improving; love the VSCode extension. #NoteTakingApps
- Bookmarks: #Linkding (Docker). Accessible bookmark manager with good browser extension support. #BookmarkManager
- Recipes: #Mealie (Docker), starting to learn cooking!
#CookingApps - RSS Feeds: #Miniflux (non-Docker), excellent accessibility. Originally wanted better podcast support but other options had major accessibility issues. #RSSReader
- Automation & Workflows: #N8N (Docker). Haven't explored deeply yet—open to ideas! #AutomationTools #WorkflowAutomation
- Pastebin Service: #PrivateBin (non-Docker). Considering alternatives or CLI tool for easier console access. #PastebinAlternative
- File Sharing & Editing: #Samba (non-Docker), easy file management from my Windows 11 mini PC. #FileSharing #Windows11
- Search Engine: #SearXNG (non-Docker), accessible and searches multiple engines at once. #PrivacySearchEngine
- IRC Client: #TheLounge (non-Docker). Some accessibility issues but best I've found so far for always-connected IRC. #IRCClient
- Read Later Service: #Wallabag (Docker). Biggest issue is Wallabagger Chrome extension doesn't work for me yet. #ReadItLater
Notifications & Development Workflow
- Notifications via: #Ntfy (Docker) and Zoho's ZeptoMail (#Zoho)
- Development Environment: Mostly using VSCode connected to my server via Remote-SSH extension. #VSCodeRemote
Accessibility Focus 
️
Accessibility heavily influences my choices—I use a screen reader full-time (#ScreenReader), so I prioritize services usable without sight (#InclusiveDesign, #DigitalAccessibility). Always open to discussing accessibility experiences or recommendations!
I've also experimented with:
- Ollama (#Ollama): Not enough RAM on my Pi.
- Habit trackers like Beaver Habit Tracker (#HabitTracking): Accessibility issues made it unusable for me.
I don't really have a media collection, so no Plex or Jellyfin here (#MediaServer)—but I'm always open to suggestions! I've gotten a bit addicted to exploring new self-hosted services! 
What's your setup like? Any cool services you'd recommend I try?
#SelfHosted #LinuxSelfHost #OpenSource #TechCommunity #FOSS #TechDIY
@rigrig Yea, I was wondering the same thing... Seems like a thinly veiled reason to get some information on their users! I'm using #UptimeKuma my self - although had an Uptime Robot going that I had forgotten about!. We don't need Uptime Robot 
#selfhosted #FTW
Yaaay, today I set up #UptimeKuma as status page for #tutter, #Blintflix and for all my other services! 
Check the status page: https://status.tutter.org/
This tool is awesome!
Continued thread
Ermahgerd! Now I'm putting #UptimeKuma and #ActivePieces together. Or really all of my #selfhosting services. So many of them can send webhooks. And I'm processing them in ActivePieces to do things.
Like I can queue up all of the payloads over the day, spit them to an AI API, and get back an HTML formatted daily summary that gets emailed to me.
I'm staying up late working on #ActivePieces and re-deploying #UptimeKuma (better this time around).
Here are my notes on deploying Uptime Kuma. #selfhosting #homelab #docker
Notes from the Rabbit Hole · Deploying Uptime Kuma with DockerA guide for self-hosters to deploy Uptime Kuma using Docker and Docker Compose.
Well, ok, so I have not "sorted" my #smartd notification issue, BUT #UptimeKuma is running like a charm, and I'm monitoring a bunch of other stuff now, with a telegram alerter setup.
Still think I'm gonna try an "inverted push" monitor for the smartd stuff, see how that goes.
If that fails... #mastodon or #nextcloud with RSS feeds
Continued thread
And I kinda solved my issue.
Bye bye #alpinelinux as an host, hello #fedora server.
Now the #UptimeKuma container, still running in a rootless #podman does have the ping monitor working, as does the other monitors.
EDIT: Problem solved, by changing the VM OS from alpinelinux to fedora-server
---
So far I spent almost my whole afternoon trying to get #UptimeKuma running as a #rootless #podman #container on a #alpinelinux #VM to successfully ping some machines to be monitored.
And so far I’m loosing the battle. If anyone has an idea or a pointer to a possible solution, I would be very happy.
Es ist vollbracht!
Die letzte Windows VM ist jetzt aus!
Das war ein hartes Stück Arbeit.
Auf der VM lief jetzt ca. 15 Jhare lang ein #PRTG Server.
Ersetzt wurde der jetzt letztlich durch 4 #OpenSource Tools:
#Beszel - klassisches System Monitoring
#UptimeKuma - Monitoring von HTTP/S Auftritten
#Prometheus (bzw. #VictoriaMetrics) und #Grafana für Metriken, Spezialfälle und Daten, die ich Jahre oder Jahrzehnte sammeln will.
Und alle drei Systeme nutzen #ntfy für Notifications - keine E-Mails.
Best to run not only a different device than your services but on a completely separate network as well. 
#UptimeKuma #monitoring
https://social.intothecloud.net/@greg/113846505336779256
intothecloud.netGreg (@greg@intothecloud.net)If you are self hosting and running any service, particularly ones that are used by family or friends, set up some basic monitoring.
I recommend Uptime Kuma (https://github.com/louislam/uptime-kuma) for monitoring the basic "Is this service alive?". You don't need to go crazy checking cpu, disk (well maybe see below), memory.
Best run on something that is separate from the rest of your services. I run my kuma on a Pi 3b.
Reason for this post? A service filled up its disk and I got a alert and was able to fix it in minutes.
#selfhosting #selfhost #uptimekuma #monitoring #homelab
If you are self hosting and running any service, particularly ones that are used by family or friends, set up some basic monitoring.
I recommend Uptime Kuma (https://github.com/louislam/uptime-kuma) for monitoring the basic "Is this service alive?". You don't need to go crazy checking cpu, disk (well maybe see below), memory.
Best run on something that is separate from the rest of your services. I run my kuma on a Pi 3b.
Reason for this post? A service filled up its disk and I got a alert and was able to fix it in minutes.
GitHubGitHub - louislam/uptime-kuma: A fancy self-hosted monitoring toolA fancy self-hosted monitoring tool. Contribute to louislam/uptime-kuma development by creating an account on GitHub.
@ironicbadger - I just listened to the most recent #SelfHosted #podcast and heard you & @ChrisLAS talking about #monitoring your self hosted bits. I’m currently deploying some system level monitoring to complement my #uptimekuma monitoring of services & came across this gem of #NixOS configuration: https://blog.korfuri.fr/posts/2022/11/autogenerated-prometheus-configs-for-multiple-nixos-hosts/
What are your thoughts? Personally, I’m leaning towards this stack:
- Grafana + Prometheus server + Telegraf agent
- Grafana + Loki + Promtail
korfuri's website · Autogenerated Prometheus configs for multiple NixOS hostsI run NixOS on my machines whenever possible. I also monitor them with Prometheus. Currently, I have 2 machines running Prometheus: sambirano, a Raspberry Pi 4 in my apartment, and boraha, a free Oracle Cloud VM (see here for details on how I installed NixOS there). They also run Grafana and Alertmanager, which forwards alerts to Zenduty.
Each machine runs at least the node-exporter and the smartctl-exporter (although this last one doesn’t report on all my disks, something I’ll have to fix in the future). Some also run other exporters, e.g. sambirano monitors my Asus RT-AC88U router using the SNMP exporter). Prometheus needs to know about all of these exporters on all of these machines somehow, and I don’t want to keep configs in sync manually, so I decided to autogenerate the Prometheus targets with Nix.
Hi #SelfHosted community. I've figured out a lot of my setup. I now have a new domain, laniesplace.us, just for #HomeServer stuff. It's set up through Porkbun with Dynu for #DDNS. I've now got #Traefik, #TailscaleVPN, #Linkding, #Forgejo, #Dokuwiki, Code-Server, #Portainer, #Netdata, #Watchtower, #Cockpit, #Pihole, #MiniFlux, #TheLounge, #Filebrowser, #UptimeKuma, and the #Homer dashboard service installed. I'm now trying to set up #Authelia so I can have single sign-on to my services. For some, it's working now, but I can't seem to get Linkding to work no matter what I do. This is on a #RaspberryPi 500 with 8 GB RAM and a 512 GB SD card, running #Stormux, which is based on #ArchlinuxARM. Can anyone help? I'll reply to this post with all my relevant config files in separate posts. What's happening is this: Linkding is supposed to be available at bookmarks.laniesplace.us. When I go there, I see a 401 unauthorized error and a link to sign into Authelia. Once I sign in, though, it redirects back to the page with the 401 error. I've been trying to figure this out for hours with no luck. Files will be in replies to this post.
#SelfHosting #Linux #HomeLab #RPi #RaspberryPi500 #RPi500
@selfhost @selfhosting @selfhosted @linux