Setup
Get started
Monitee is two pieces: the app on your phone, and an agent you run on the server you want to watch. The agent does the work. Install it first, then point the app at it.
Step 1
Install the agent on your server.
Eight routes to the same agent. Pick the one that matches how your box is already set up. Every route ends with you setting the username and password the app signs in with, in configuration.yml (or the add-on’s Configuration tab on Home Assistant), and the agent listening on 8080 and 8443. Whichever guide you follow, you are looking for Tomcat started on ports 8443 (https), 8080 (http) in the log.
NAS and appliances
Unraid, TrueNAS and Home Assistant, through their own app catalogues.
Linux, no container
Straight onto the host. Both routes need Java 21 or newer.
Step 2
Add the server in the app.
Install Monitee and tap +. On your own network it usually finds the server by itself: the agent announces itself over DNS-SD, so there is often nothing to type at all. Full connection guide.
1
On your network
The app finds the agent and offers it to you. If your network blocks discovery, type the LAN address instead, such as 192.168.0.166:8080. Find it with ifconfig on the server.
2
And from anywhere
A server can hold two addresses, local first and public second, so the same entry works at home and on mobile data. That needs a static IP or a domain and port 8443 or 8080 reachable, or your own VPN. SSL help.
3
Make it yours
Sign in with the credentials from configuration.yml, give the server a name and icon, and pick which drives and network adapters show on the dashboard.
If it will not connect
It is nearly always one of these four.
The agent is still starting
Look for the Tomcat started line in the log before you try again. On a Raspberry Pi the first start can take a minute.
Ports 8080 or 8443 were already taken
Then the agent never bound. Change the ports in application.properties or free them up, and restart.
The certificate is self-signed
The app shows it to you, and you have to trust it before it will connect. SSL troubleshooting covers the rest.
The credentials do not match
The username and password in configuration.yml are the ones the app needs. Check for a trailing space.
Still stuck? Read the FAQ, set up notifications, or report an issue on GitHub.