Kembali ke Blog
SERVER

Build a 24/7 Server Monitoring System on a Budget Using an Old STB and Uptime

22 May 2026 Administrator
Header Hero


Build a 24/7 Server Monitoring System on a Budget Using an Old STB and Uptime Kuma



Turn an Old STB into a 24/7 Uptime Kuma Server Monitor



Have you ever experienced a sudden network or website outage, only to realize it hours after the fact? Delayed awareness of server downtime can be disastrous. However, you don't need to burn a hole in your pocket paying for expensive server hosting just to keep an eye on your systems. The most cost-effective workaround is repurposing a used Set-Top Box (STB) as a dedicated, 24/7 monitoring hub using Uptime Kuma, which can instantly push alerts directly to your smartphone.



By investing in secondhand hardware for roughly Rp100,000, you can establish an efficient, round-the-clock monitoring infrastructure. It's affordable, practical, and highly responsive.




Related Reading: How to Remotely Access an Armbian STB Using Tailscale


(If you are a visual learner, be sure to check out the full video tutorial linked below before reading further.)






Why Use a Used STB and Uptime Kuma?


Pairing budget-friendly hardware with open-source software creates the ultimate monitoring environment. Uptime Kuma is widely celebrated as a top-tier, self-hosted monitoring tool featuring a sleek, user-friendly interface. Running it on a repurposed STB (such as the HG680P or B860H models) offers incredible power efficiency. Your monitoring node can stay online constantly without causing a spike in your electricity bill.



Beyond its low power consumption, this setup unlocks premium, enterprise-level features completely free of charge:



  • Comprehensive Protocol Support: It goes beyond basic HTTP/HTTPS website tracking. You can ping client routers, verify specific application TCP ports, monitor DNS records, and even check database statuses (like MySQL and Redis).

  • Instant Notifications: Forget about constantly refreshing a dashboard. The moment an anomaly occurs or a server drops, the system triggers immediate alerts via Telegram, Discord, Email, and various other channels.

  • Ultimate Flexibility: This setup is perfect for anyone—from system administrators tracking server health and homelab enthusiasts, to local WISP (RT/RW Net) operators needing a centralized, ultra-low-budget monitoring solution.





Hardware and Software Requirements


Before assembling your monitoring station, you must prepare a few essential components. Since this is meant to be a non-stop, self-hosted server, reliable hardware is key.



Hardware Needed:



  • Used STB Unit: This guide references the HG680P model, but similar variants like the B860H work just as well. The only strict requirement is that the STB must be unlocked and capable of running a Linux operating system.

  • Authentic MicroSD Card: This acts as the primary storage for your OS and database. While a 16GB card is sufficient to run Armbian and Docker, a 64GB card is highly recommended to provide ample breathing room. Crucial tip: Always use an original, high-quality MicroSD to ensure the server remains stable 24/7 and to prevent data corruption.



Software Needed:



  • Armbian Linux: Your STB must have the Armbian Linux OS flashed and running.

  • CasaOS: To streamline file and application management, we will utilize CasaOS. While command-line (CLI) installations are possible, CasaOS offers an incredibly intuitive, web-based graphical interface that makes the process effortless.


(Note: If your STB is currently unconfigured, please refer to a basic STB server installation guide to get Armbian and CasaOS running before proceeding to the next steps.)





Installing Uptime Kuma via CasaOS


Once your STB's baseline infrastructure is set, deploying the monitoring software is a breeze. Thanks to CasaOS, there is no need to wrestle with complex Linux terminal commands—it’s essentially a one-click process.




  1. Access your CasaOS dashboard via a web browser on your computer.

  2. Navigate to the App Store from the main dashboard.

  3. Type "Uptime Kuma" into the search bar.

  4. Once the app appears in the results, hit the Install button.

  5. The download and deployment will process automatically. Being a lightweight application, it typically finishes in under two minutes (depending on your network speed).

  6. After installation, return to the CasaOS home screen. You will now see the Uptime Kuma icon, indicating that your monitoring server is live and ready for configuration.





Initial Configuration & Adding Monitors


Click the newly created Uptime Kuma icon in CasaOS to access its web interface. For your very first login, a brief initial setup is required:



  • Database Selection: Choose the Embedded DB (SQLite) option. This is highly recommended for STB environments because it is lightweight and requires zero extra configuration.

  • Admin Account: Set up a secure username and password for future dashboard management, then click Create.



Once logged in, you can start inputting the targets you want to track. Here is an example of how to monitor a standard HTTPS website:



  1. Click the green Add New Monitor button in the top-left corner.

  2. Under the Monitor Type dropdown menu, select HTTPS.

  3. Enter a Friendly Name (e.g., "Client A Website").

  4. Input the website's address into the URL field.

  5. Scroll down to utilize one of Uptime Kuma's best features: check the boxes for Certificate Expiry Notification and Domain Name Expiry Notification. This ensures you are warned well before your SSL or domain expires.

  6. Leave the rest of the settings at their defaults and click Save.


Your website is now actively monitored! The detail page will display real-time ping graphs, response times, and a countdown timer for your domain and SSL certificate renewals.





Configuring Telegram Alerts in Uptime Kuma


A monitoring system is only useful if it proactively warns you of issues. Let's set up automated Telegram alerts so your smartphone notifies you the second a server crashes.



1. Create a Telegram Bot and Get the API Token



  • Open Telegram and search for the official @BotFather (look for the verified blue tick).

  • Send the /newbot command.

  • Give your bot a display name (e.g., "Cloud Monitor") and a unique username ending in "bot" (e.g., "cloudmonitor_bot").

  • Upon success, BotFather will generate a long alphanumeric string—your API Token. Copy and save this securely.



2. Retrieve Your Chat ID


Next, you need your personal ID so the bot knows where to send the alerts:



  • Search for @userinfobot or @MyIDBot in Telegram.

  • Click Start or type /id.

  • The bot will reply with a string of numbers. This is your Chat ID. Copy it.


(Crucial Step: Before heading back to Uptime Kuma, search for your newly created bot in Telegram and click Start to initiate a chat. If you skip this, the bot won't have permission to message you and will throw an error.)



3. Link Telegram to Uptime Kuma



  • Go back to your Uptime Kuma dashboard.

  • Click your profile icon (top right), go to Settings, and select the Notifications tab.

  • Click Setup Notification and choose Telegram as the type.

  • Paste your API Token (from BotFather) into the Bot Token field.

  • Paste your Chat ID into the designated field.

  • Click Test. If you receive a test message on Telegram, hit Save.


Now, whenever a service goes down, your Telegram bot will instantly shoot you a red-flagged alert. Once the service is restored, you will receive a follow-up message confirming it is back online.





Conclusion


Repurposing an old STB (like the HG680P or B860H) to run Uptime Kuma is arguably one of the smartest, most budget-friendly homelab investments you can make. With minimal power draw, you gain an enterprise-grade utility that vigilantly guards your network's uptime, tracks SSL lifespans, and delivers instant Telegram alerts the moment things go awry.

DAFTAR ARTIKEL LAINNYA