[GH-ISSUE #1868] MeshAgent Message chat #1164

New issue

Closed

opened 2026-03-02 02:21:35 +03:00 by kerem · 0 comments

kerem commented

2026-03-02 02:21:35 +03:00

Owner

Originally created by @Avessalom608 on GitHub (May 8, 2024).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1868

For some reason the mesh message tab is not appearing on the Windows 10 22H2 host. The server is based on Ubuntu 22.05. The browser used is Google Chrome. The server was installed in normal mode. (without key --insecure)
However, the chat itself works.
If:
Disable the mesh agent service and run the MeshAgent.exe executable in interactive mode.
Or:
Enable the mesh agent service and connect in console mode via rdp to the host, blocking the locally authorized user.

How can I fix this problem?
The problem was discovered after upgrading from 17.05 to 18.2, but later I realized that this was also the case on 17.05.
I tried disabling "Sync Mesh Perms with TRMM" but it didn't help.

In my opinion, the problem is clearly on the MeshAgent side, but I don’t understand what can be done.
I didn't find any errors in MeshAgent.log

However, I noticed some differences:
When MeshAgent.exe run I observe:
Server verified meshcore... Launching meshcore..

Then, when I start the background service, I do not see this message in the MeshAgent.log file.

Originally created by @Avessalom608 on GitHub (May 8, 2024). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1868 For some reason the mesh message tab is not appearing on the Windows 10 22H2 host. The server is based on Ubuntu 22.05. The browser used is Google Chrome. The server was installed in normal mode. (without key --insecure) However, the chat itself works. If: Disable the mesh agent service and run the MeshAgent.exe executable in interactive mode. Or: Enable the mesh agent service and connect in console mode via rdp to the host, blocking the locally authorized user. How can I fix this problem? The problem was discovered after upgrading from 17.05 to 18.2, but later I realized that this was also the case on 17.05. I tried disabling "Sync Mesh Perms with TRMM" but it didn't help. In my opinion, the problem is clearly on the MeshAgent side, but I don’t understand what can be done. I didn't find any errors in MeshAgent.log However, I noticed some differences: When MeshAgent.exe run I observe: Server verified meshcore... Launching meshcore.. Then, when I start the background service, I do not see this message in the MeshAgent.log file.