How to Set Up Health Checks on SonicBit: Keep Your Seedbox Running 24/7
How to Set Up Health Checks on SonicBit: Keep Your Seedbox Running 24/7
Picture this: you kick off a 40GB Linux ISO transfer before bed, wake up excited to grab it, and discover qBittorrent crashed three hours in. Your download never finished, and you had no idea anything went wrong until you checked manually. That's the exact problem health checks solve — they watch your apps so you don't have to.
In this tutorial, you'll learn how to set up automated monitoring for your SonicBit seedbox using Uptime Kuma, SonicBit's built-in monitoring app. By the end, you'll have uptime tracking, instant alerts, and the know-how to diagnose common failures before they ruin your downloads.
Prerequisites:
- A SonicBit account with at least 1 basic app slot available (the Nano plan at $1.99/month works fine)
- At least one app already running (Plex, qBittorrent, Sonarr, etc.) that you want to monitor
- A few minutes to configure your alert channels (email, Discord, or Telegram)
Why Health Checks Matter for a Seedbox
A seedbox runs multiple moving parts at once — your torrent client, maybe a media server, an automation app like Sonarr, and your network connection to trackers. Any one of these can quietly fail:
- Your download client crashes mid-transfer and stops responding
- A container loses network connectivity and can't reach trackers
- Your media server freezes, so Plex shows "server unavailable" to your family
- Disk space fills up and new downloads silently fail
Without monitoring, you usually find out about these problems the hard way — when you go looking for a file that was never actually downloaded. Health checks flip that script: instead of you checking on your apps, your apps get checked automatically, and you only hear about it when something's actually wrong.
Step 1: Deploy Uptime Kuma
Uptime Kuma is a lightweight, self-hosted monitoring tool, and it's available as a one-click app on SonicBit.
- Log in to your SonicBit dashboard
- Go to the Apps section
- Search for "Uptime Kuma" in the app catalog
- Click Deploy — no Docker commands or config files needed, SonicBit handles the container, networking, and SSL automatically
!Deploying Uptime Kuma from the app catalog
- Once deployed, open the app from your dashboard — it'll be live at a subdomain like
uptimekuma-yourusername.sonicbit.net - Create your admin username and password on first launch
Uptime Kuma is a light app, so it runs comfortably on a basic app slot without eating into the performance slots you'll want reserved for things like Plex.
Step 2: Add Monitors for Your Apps
Now tell Uptime Kuma what to watch. You'll create one "monitor" per service.
- Inside Uptime Kuma, click Add New Monitor
- Choose a monitor type:
| Monitor Type | Best For |
|---|---|
| HTTP(s) | Web-based apps like Plex, Sonarr, Radarr, Jellyfin |
| TCP Port | qBittorrent's web UI port, Nzbget, raw service ports |
| Ping | Checking basic network reachability |
- Fill in the details:
- Friendly Name: something recognizable, like "qBittorrent" or "Plex Media Server"
- URL/Port: the app's subdomain URL from your SonicBit dashboard (for HTTP monitors) or its port (for TCP monitors)
- Heartbeat Interval: how often to check — 60 seconds is a good default for most apps
- Retries: set this to 2-3 so a single blip doesn't trigger a false alarm
- Click Save
Repeat this for every app you want watched — your torrent client, your media server, and any automation apps like Sonarr or Radarr that need to stay running for your downloads to actually get organized.
!Adding a new monitor in Uptime Kuma
Step 3: Set Up Automated Alerts
A monitor that fails silently doesn't help you — you need it to actually notify you.
- In Uptime Kuma, go to Settings > Notifications
- Click Setup Notification and pick a channel:
- Email — simplest option, works everywhere
- Telegram — fast push notifications to your phone
- Discord — good if you already run a server for your media setup
- Webhook — for more advanced custom integrations
- Enter the required credentials (bot token, webhook URL, or SMTP details depending on the channel)
- Click Test to confirm it fires correctly
- Go back to each monitor you created and attach this notification under Notifications on the monitor's edit screen
Now, if qBittorrent stops responding at 3am, you'll get a message instead of finding out when you check your transfers the next day.
Step 4: Interpreting Common Status Failures
Once your monitors are live, you'll start seeing different failure types. Here's how to read them:
"Down" with a connection timeout Usually means the app's container has crashed or stopped. Head to your SonicBit dashboard's Apps page and check the app's status — a quick restart from there usually resolves it.
"Down" with a 502/503 error The container is running, but it isn't responding properly yet (common right after a restart while the app initializes). Give it a minute and re-check before assuming it's a real failure.
Intermittent flapping (up/down/up/down) Often points to the app running low on resources. If you're running something heavy like Plex transcoding or JDownloader2 on a basic slot, consider upgrading to a plan with more performance app slots — see the SonicBit pricing page for options.
TCP monitor down, but HTTP monitor up This can indicate a specific service inside the app (like qBittorrent's torrent engine) has hung even though the web UI is still technically reachable. Worth a manual check if you see this pattern repeatedly.
Step 5: Catch Connectivity Issues Before They Disrupt Transfers
Beyond individual app crashes, you can monitor connectivity itself:
## Example: what a TCP monitor checks under the hood
## It's effectively verifying the port accepts connections
nc -zv your-app-subdomain.sonicbit.net 443
Add a monitor pointed at your tracker-facing apps (like Jackett or Prowlarr) so you know immediately if connectivity to your indexers drops — this is often the real cause behind "my downloads just stopped" moments, rather than the download client itself being broken.
What's Next?
Now that your monitoring is in place, a few logical next steps:
- Set up a full automation stack (Sonarr + Radarr + Prowlarr + Plex) so Uptime Kuma has more to watch — and your downloads organize themselves
- Pair health checks with Remote Upload to confirm your cloud transfers to Google Drive or Dropbox are completing successfully
- If you're monitoring several heavy apps, check whether your current plan has enough performance app slots on the pricing page
Health checks turn your seedbox from something you babysit into something that just works in the background — exactly how self-hosting should feel.
Sign up free at SonicBit.net and get 4GB storage. Download our app on Android and iOS to access your seedbox on the go.
Put it into practice — cloud storage with one-click apps and a built-in seedbox.
START FREE — 4 GB
