MeshMonitor
MeshMonitor is a web-based dashboard for monitoring off-grid mesh networks, including Meshtastic, MeshCore, and MQTT, providing node status, history, and…
Platform availability
Available on 3 of 10 platforms
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
78/100 Good
- Maintained
- 100last commit 6 days ago
- Popular
- 57730 GitHub stars
- Easy to install
- 553 install platforms, install notes, Docker image
- Light to run
- 85512 MB minimum RAM
Availability: platform listings confirmed today, links checked 20 days ago
- GitHub stars
- 730
- Open issues
- 18
- Last commit
- 2026-11-15
- Latest release
- v4.17.3
- License
- BSD-3-Clause
- Activity
- steady
Checked 6 days ago - source: GitHub (Yeraze/meshmonitor)
Resources & Compatibility
Minimum requirements: 512 MB RAM, 1 CPU core(s), 1 GB disk.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Point the app at your Meshtastic node Before starting, set MESHTASTIC_NODE_IP in your .env to the IP address of your Meshtastic device. If it's missing or wrong, MeshMonitor may load but won't be able to find your mesh. source
- Save your data in the right folder Create the data folder, such as /var/lib/meshmonitor/data, and make sure the app's user can read and write to it. If permissions are wrong, MeshMonitor may start but fail to save settings, logs, or node history. source
- Match the web address you use (CORS) Set ALLOWED_ORIGINS to the exact web address you'll use, like http://localhost:8080 or http://192.168.1.50:8080. If it doesn't match, your browser may block the app from loading mesh data even though the page opens. source
Fetched 47 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
How can MeshMonitor be deployed with Helm?
A local checkout can be installed with helm install meshmonitor ./helm/meshmonitor -f custom-values.yaml. The Helm chart supports ingress, TLS, persistence, and a full values reference.
How is reverse-proxy single sign-on enabled?
Set PROXY_AUTH_ENABLED=true and, if needed, PROXY_AUTH_AUTO_PROVISION=true, then set TRUST_PROXY=1 or the appropriate hop count/subnet. MeshMonitor must not be directly accessible, and the proxy must validate authentication before forwarding requests.
What session issue appears with multiple MeshMonitor instances on the same IP or domain?
Running multiple instances on the same host with the same IP or domain but different ports can cause random logouts, CSRF validation failures, or session conflicts.
Where can I find the detailed guides?
The README links to a documentation site that includes getting started, FAQ, configuration, and development pages.
Answers sourced from github.com, meshmonitor.org
Community
Collected 48 days ago - public community threads