I've done some security hardening of the nodes (the actual physical servers hosting your VMs). This included, among some other things, blocking access to the Proxmox web UI and SSH server from the Internet.
Our current uptime monitor (Upptime) checked if a server is up by pinging the port on which the Proxmox web UI was on. Of course, as Upptime is hosted on GitHub, now this ping is blocked, and the nodes will always show up as being down.
Technically, it would be possible to work around this issue by having it ping a VM on that node or whitelisting the GitHub Actions IP ranges (this would be a nightmare as they apparently change on a regular basis).
But this is not the only issue with Upptime. For one, it can only be hosted on GitHub. To display the uptime on the website, your browser used to make a request to GitHub's servers, even on Tor (even though your real IP is not exposed, technically you have less privacy when accessing a clearweb domain as opposed to a hidden service). I don't think I need to explain why this is not exactly the best idea for a privacy-first service, considering that GitHub is owned by Microsoft and hosted on Microsoft's servers.
Another issue is that Upptime depends on GitHub Actions for the actual monitoring. This means that GitHub decides when to run the update task based on the current load of their runners. Instead of running every minute, or at least every couple minutes, it could take hours for the status to update.
Looking at other options for an uptime monitor, including paid ones, none of them are up to my standards, so I've decided to build a new one just for Kyun. I'm planning to also add a resource monitor showing the overall CPU & RAM usage of the node. A lot more things are coming, so if you're looking for updates, join our Matrix, where, besides spamming random shit, we'll also be posting status updates and previews of upcoming features & projects.