Release history
Yeraze/meshmonitor releases
All releases
92 shown
Review required
v4.8.1
Breaking risk
Auth
RCE / SSRF
Automations, reconnect fix, security hardening
Review required
v4.7.2
Breaking risk
Dependencies
Auth
Fix MQTT crash + URL import + message order
Config change
v4.7.0
Mixed
Auth
RBAC
Breaking upgrade
Remote admin, MQTT dashboard restore, topic rewrite
Upgrade now
v4.6.4
Mixed
Auth
Path Management, Passive Mode Stability, Visibility Toggles, PublicKey Fix
Upgrade now
v4.0.1
Bug fix
Breaking upgrade
Dependencies
Preserves legacy telemetry & neighbor data
Config change
v4.0.0
Breaking risk
Auth
RBAC
Breaking upgrade
Multi-Source + Per-Source Permissions
v3.2.2
Mixed
⚠ Upgrade required
- Do not install this version if using MySQL or PostgreSQL; a breaking bug will prevent the installation from starting.
- Migration 056 now gracefully handles unexpected backup_history table schemas, but any incompatible records in that table will be lost (disk files remain).
- LXC deployments lack auto‑upgrade support; manual updates require downloading new template files.
Notable features
- Added Proxmox-compatible LXC container template with installation guide
Full changelog
🔧 Hotfix Release
This hotfix resolves a migration issue that prevented v3.2.1 from starting on some installations.
NOTE: Do not install if using MySQL or PostGres. There is a breaking bug that will prevent your installation from starting.
Bug Fixes
- Fixed migration 056 failing on startup - The backup_history column migration now handles unexpected table schemas gracefully. Previously, if the table had an unexpected structure (missing
timestampcolumn), the migration would fail and prevent the server from starting. (#1585)
Technical Details
Migration 056 now:
- Checks if the table exists before proceeding
- Creates the table with the correct schema if it doesn't exist
- Detects and handles tables with unexpected schemas by recreating them
- Validates required columns exist before attempting data migration
- Logs column names for easier debugging
Note: If you had device backup history records in an incompatible schema, they will be lost during migration. The actual backup files on disk remain intact.
Pull Requests
- #1585 - fix(migration): make backup_history migration more robust
Full Changelog: https://github.com/Yeraze/meshmonitor/compare/v3.2.1...v3.2.2
Proxmox LXC Template
This release includes a Proxmox-compatible LXC container template for MeshMonitor.
Installation
- Download the
.tar.gztemplate file - Verify the SHA256 checksum (optional but recommended)
- Upload to your Proxmox server:
scp meshmonitor-*.tar.gz root@proxmox:/var/lib/vz/template/cache/ - Create a new LXC container from the template via Proxmox web UI
- Configure
/etc/meshmonitor/meshmonitor.envwith your Meshtastic node IP - Start the container and access the web UI on port 8080
Documentation
See the Proxmox LXC Deployment Guide for detailed instructions.
Limitations
- Auto-upgrade feature is not supported in LXC deployments
- Manual updates required (download new template for each version)
- Community-supported (Docker remains the primary deployment method)
🚀 MeshMonitor v3.2.2
📦 Installation
Docker (recommended):
docker run -d \
--name meshmonitor \
-p 8080:3001 \
-v meshmonitor-data:/data \
ghcr.io/Yeraze/meshmonitor:3.2.2
🧪 Testing
✅ All tests passed
✅ TypeScript checks passed
✅ Docker images built for linux/amd64, linux/arm64, linux/arm/v7
📋 Changes
See commit history for detailed changes.