Skip to content

Getting Started

Jump to bottom
AstorisTheBrave edited this page Jul 5, 2026 · 2 revisions

Getting Started

A short checklist to go from a fresh install to watching your monitors.

Quick checklist

  • Uptime Kuma is running and reachable from your phone's network
  • You know your Kuma URL, username, and password
  • URSA is installed (Installation)
  • Add your server and log in (below)
  • Optional: enable push (Push Notifications)

1. Connect to your server

On the login screen, enter your Uptime Kuma address, for example:

  • https://kuma.example.com
  • http://192.168.1.10:3001 (a plain-HTTP instance on your LAN)

If you leave off http:// or https://, URSA assumes https://.

Self-signed certificate? If your instance uses HTTPS with a self-signed certificate, tick "Trust self-signed certificate" for that connection. Only do this for servers you control. See Security for what this means.

2. Log in

Enter your username and password. If your account has two-factor authentication (2FA) enabled, URSA asks for your current 6-digit code. URSA stores only the resulting session, never your password, and it is encrypted on the device.

3. Find your way around

URSA has three tabs along the bottom:

  • Monitors - the live list. Each card shows a status circle (or the service's favicon), name and URL, a status pill, a response-time sparkline, and 24-hour uptime. Use the search and status filter in the top bar when the list gets long.
  • Notifications - set up push alerts (see Push Notifications).
  • Settings - app lock, slow-response alerts, Material You, and sign out.

4. Watch a monitor in detail

Tap any monitor to open it:

  • A status pill, current ping, and uptime.
  • A heartbeat strip you can view over 6h, 24h, 7d, or 30d using the chips.
  • TLS certificate info for HTTPS monitors.
  • Pause / Resume to stop or start its checks.
  • If slow-response alerts are on, a per-monitor response-time limit field.

5. Slow-response alerts

In Settings, turn on Slow-response alerts and set a response-time limit (in milliseconds). URSA then notifies you when a monitor is up but responding slower than that limit - something Uptime Kuma itself cannot alert on. You can override the limit per monitor from its detail screen.

6. Multiple servers

Add more than one Uptime Kuma server and switch between them. URSA keeps you signed in and reconnects automatically if the connection drops.

7. Public status pages

You can also view a public Uptime Kuma status page by its URL, without logging in.

Signing out

Open the Settings tab and tap Sign out to end the session and remove the stored credentials for the active server.

Next: Push Notifications, Wear OS, or Troubleshooting.

URSA Wiki

For users

For developers

Clone this wiki locally