[SUPPORT] MeshMonitor Settings

[valter-bruno]

MeshMonitor Settings

Good morning,
via the web, pointing to the node's IP address
it connects to: https://client.meshtastic.org/nodes

However, with MeshMonitor with Web UI Port 8080 and the node's IP address, it doesn't connect to http://localhost:8080/

So it's not possible to configure and use the software.

Where could the problem be?

Thanks, Valter

[Yeraze]

Hi Valter, thanks for opening this!

I think there's a mix-up between two different things:

1. https://client.meshtastic.org/nodes (or the node's own IP directly) — this is the built-in web client that lives on the Meshtastic node's own firmware. It's served by the node itself.
2. MeshMonitor — this is a separate application that you install and run yourself (most commonly as a Docker container). It does not run on the Meshtastic node — it runs on its own host (your PC, a Raspberry Pi, a NAS, a server, etc.) and then connects out to your node over the network (TCP port 4403) to pull data from it.

So http://localhost:8080 (or whatever port you mapped) only works if MeshMonitor is actually running on that machine — pointing your browser at the node's IP on port 8080 won't work, because the node isn't running MeshMonitor; only its own built-in firmware web UI is there (on its own port).

To get MeshMonitor running, you need to deploy it somewhere (e.g. Docker Compose is the easiest way) and configure it to point at your node's IP — not host it on your node:

services:
  meshmonitor:
    image: ghcr.io/yeraze/meshmonitor:latest
    container_name: meshmonitor
    ports:
      - "8080:3001"
    restart: unless-stopped
    volumes:
      - meshmonitor-data:/data
    environment:
      - MESHTASTIC_NODE_IP=192.168.1.100  # <-- your node's IP goes here
      - ALLOWED_ORIGINS=http://localhost:8080

volumes:
  meshmonitor-data:
    driver: local

Then browse to http://<the-machine-running-meshmonitor>:8080 — e.g. http://localhost:8080 if it's on the same computer you're browsing from, or the Docker host's LAN IP if it's on another machine.

Helpful docs:

• MeshMonitor Getting Started guide (Docker Compose quick start, other deployment options like Desktop App, Helm, Proxmox LXC, bare metal): https://meshmonitor.org/getting-started
• MeshMonitor Docker Compose Configurator (generates a ready-to-use compose file for your setup): https://meshmonitor.org/configurator
• MeshMonitor Deployment Guide (Kubernetes/Helm, bare metal): https://meshmonitor.org/deployment/DEPLOYMENT_GUIDE
• Official Meshtastic docs on the node's built-in web client: https://meshtastic.org/docs/software/other/web-client/

If you deploy MeshMonitor and still can't connect from MeshMonitor to your node, let us know the deployment method (Docker/bare metal/etc.) and any error message shown, and we can help troubleshoot further.

-- Authored by Roger 🤓

---

Generated by Claude Code

[valter-bruno]

Yeraze, thanks for your reply.
Sorry, but I don't quite understand.
I installed MeshMonitor on a Windows PC using its executable file.
Isn't this method sufficient for connecting to a Lora node, via the LAN, pointing to its IP address?
Thanks, Valter

[Yeraze]

You would load the MeshMonitor interface at http://localhost:8080 (or whatever port you configured it for), and then point MeshMonitor at your node by IP address.

Does that answer your question?

If not, can you please start over and explain your situation/problem a bit better? Maybe it's a language issue but your original post doesn't make much sense.

[valter-bruno]

Let me explain better.
Here are my steps:
a) I run MeshMonitor on a Windows 11 Pro PC.
b) Then, in Settings and Advanced Options,
c) Web UI Port = 8080 (default port).
d) Allowed Origins (CORS) = Lora node IP 192...* (which is on the LAN).
e) Start MeshMonitor.
The software opens the web page http://localhost:8080/
and continues to stay in Starting mode, and the node is not connected.
Thanks for your help, Valter

[Yeraze]

The "Allowed Origins" should be the address of the MeshMonitor Webserver, the URL you type into the address bar of a computer attempting to load the MeshMonitor Web UI.

If you only plan to access it directly from teh system running MeshMonitor then it should be localhost .. If you plan to access it from other computers, then it should be the MeshMonitor computer's IP address or DNS name.

[valter-bruno]

Thanks for the reply.
The page http://localhost:8080/ doesn't start or run.
I access it directly from the PC where MeshMonitor is running.
There's something missing, but what?

[Yeraze]

Hi Valter — thanks for the extra detail. "Software opens the page and stays in Starting" almost always means the backend server (which the desktop app spawns in the background) failed to start or crashed shortly after. On Windows, the top suspects (in the order I'd check them):

1. Port 8080 is already in use on your PC. It's a very popular port — IIS, Docker Desktop, Jenkins, a VPN client, or a corporate agent will often own it. Quick check: open Command Prompt and run

   netstat -ano | findstr :8080
   

   If anything comes back, that's your problem. The easiest fix is to change Web UI Port in MeshMonitor to something less contested — try 18080 — and restart the app.

2. Windows Defender / antivirus sometimes quarantines the bundled Node server the desktop app launches, silently. If the Web UI is still stuck after changing the port, this is likely next.

3. Windows Firewall pop-up on first launch — occasionally it opens behind the MeshMonitor window. Alt-Tab to check for a hidden "Allow access" prompt.

Please share the log files — they'll almost certainly tell us the exact reason. On Windows they live at:

%APPDATA%\MeshMonitor\logs\

Paste %APPDATA%\MeshMonitor\logs into File Explorer's address bar and attach whatever is inside (there should be at least a desktop.log, and likely a server log). Plus the output of the netstat command above.

With those two things we should be able to pin this down in one round.

-- Authored by Roger 🤓

---

Generated by Claude Code

[valter-bruno]

Thanks, Roger
With port 10080, nothing changes; it doesn't connect.
I'm attaching the logs here, if they're helpful.
Thanks, Valter

apprise.log
desktop.log
server-stderr.log
server-stdout.log

P.S.
I'm letting you know that two of us are having the same problem: me with Windows 11 Pro and a friend of mine with Windows 10.
Two different machines with two different operating systems.

[Yeraze]

It looks like you've configured it to be at http://localhost:18080 .. Have you tried that?

Also the stderr seems to indicate a problem.. Let me take a look.

[valter-bruno]

Yes, exactly
http://localhost:18080/