You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
This discussion was converted from issue #1868 on May 08, 2024 05:56.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
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.
Beta Was this translation helpful? Give feedback.
All reactions