Activity

1. AutonomousDev

   added

   bugSomething isn't workingSomething isn't working

   on Nov 10, 2026
2. Yeraze commented on Nov 10, 2026

   

   Yeraze

   on Nov 10, 2026 – with Claude

   Owner

   More actions

   Thanks for the report. I checked for duplicates and found none open. The earlier MeshCore Virtual Node issues (#4535, #5350, #5597, #5916, #5933) are all closed and were about protocol behaviour once a client is connected. Yours is a connection-level failure.

   What I found in the code

   • Saving a MeshCore source's settings restarts its manager, and the Virtual Node server starts after the companion connects (startVirtualNodeServer in meshcoreManager.ts). If the source is not currently connected to the Heltec, the VN listener is never bound.
   • Your error says port 54346, but you configured 5000. "Connection refused" means nothing was listening at that address and port. The app may be using a different port than the one you configured.
   • The default docker-compose.yml publishes only 8080:3001 and 1883:1883. The Virtual Node port is not published, so a client on another machine can't reach it even if the VN is running inside the container.

   Things to try

   1. Add the VN port to the ports: section of your compose file, for example - "5000:5000", then run docker compose up -d. Alternatively, use network_mode: host.
   2. Confirm the source shows as Connected in MeshMonitor after you save.
   3. In your client, enter the host's LAN IP with port exactly as configured (5000).

   Information that would help

   • The container logs just after saving the source (docker logs meshmonitor 2>&1 | grep -i "virtual node"). Look for "Failed to start Virtual Node server" or a "listening on port" line.
   • Your docker-compose.yml ports section.
   • The VN port shown in the source settings (it should be 5000), and where port 54346 comes from.
   • The output of ss -ltn | grep 5000 on the host.

   If the logs show the server listening and the port published, but connections are still refused, I'll dig further.

   -- Authored by Roger 🤓

   ---

   Generated by Claude Code
3. Yeraze commented on Nov 10, 2026

   

   Yeraze

   on Nov 10, 2026

   Owner

   More actions

   One more note on the error text. In a Dart/Flutter SocketException for a refused connection, port = 54346 is usually the phone's own local (ephemeral) port, not the port it dialled. So the app probably did try 5000, and nothing answered there.

   That points to the port not being reachable from the phone. Two quick checks:

   1. The MeshCore source's Dashboard card shows a Virtual Node badge when the server is listening. The source's Virtual Node section shows Server running. If neither appears, the source isn't connected to the Heltec, or the server failed to start (see the log line from my earlier comment).
   2. If it is running, publish the port in your compose file (- "5000:5000") and recreate the container. See the MeshCore Virtual Node docs for a compose example.

   -- Authored by Roger 🤓

   ---

   Generated by Claude Code
4. AutonomousDev commented on Nov 10, 2026

   

   AutonomousDev

   on Nov 10, 2026

   Author

   More actions

   This was my fault. I needed to open the port on the docker image.
5. AutonomousDev

   closed this as completedon Nov 10, 2026