Open Domkra opened 1 week ago
thank you for this, i think your issue is similar to https://github.com/Ylianst/MeshCentral/issues/6290
and i believe the issue is something to do with the win-userconsent
module
and sadly thats part of the meshagent code
so im going to have to dig into the agent and see whats wrong then build new agents etc 👎
one quick thing, are all your remote devices the same OS AND version?
have you tried a mix of different OS like windows 10/11/server 2019/etc? also have you tried different versions like 22h2, 24h2, etc ?
if you are happy to debug something for me please can you try these steps and in the extact order!
psexec.exe -i -s "c:\program files\MeshCentral\MeshAgent\meshagent.exe" run
(your file path might be different)eval "console.setInfoLevel(1);"
this is what im doing at the moment to get it crash as such for https://github.com/Ylianst/MeshCentral/issues/6290
My test devices were a mix of Windows 10 and Windows 11, with different versions, some with 22h2 and some with 23h2. We do not manage servers with Meshcentral, and it is not planned.
I followed the steps, but it doesn’t hang at any point. The request goes through, I can confirm it, and the connection is established. However, I noticed that during debugging, the connection was established much faster. The time until the user consent prompt appeared was 90-120 seconds in my previous tests, but during debugging, it was 10-20 seconds.
Do you need the logs that were output in psexec? If so, do the logs contain any sensitive data besides the server address and ports?
@Domkra wow ok that's interesting? That to me screams that there is an issue with your machines? And just a screenshot would be fine, hide anytbing you concider secret But I think it's similar output to the other issue that's linked to this issue and its screenshots
I find that strange if it could be due to the machines, because I’m sure it worked without these problems before. Since then, we haven’t made any changes to our machines. We only performed updates from Windows 10 to Windows 11.
I have attached the output I got from psexec.
Another quick note:
I just tried something else: I stopped the Background Agent and downloaded the Interactive Only Agent. When I use this agent, connect to the server, and then try to establish a connection, the problem does not occur, and the User Consent appears on the target computer within a short time.
Could it possibly be related to the Background and Interactive Agents?
**Describe the bug A clear and concise description of what the bug is.**
I noticed that when I try to connect to a desktop using Meshcentral, the request for user consent takes about 90 to 120 seconds before the customer can confirm access. However, when I use Meshcentral without the consent request, the connection to the desktop is established in 1 second.
**To Reproduce Steps to reproduce the behavior:**
If not set up, enable User Consent first:
Expected behavior A clear and concise description of what you expected to happen.
I expected the connection to the remote client to be established faster, as it was a few weeks or months ago. The time of 90 to 120 seconds seems too long to establish a connection to a customer.
Server Software (please complete the following information):
Client Device (please complete the following information):
Remote Device (please complete the following information):
Additional context Add any additional context about the problem here.
A few weeks or months ago, I am not sure exactly how long, this behavior did not occur, and the user prompt was much faster. No changes were made to the configuration, which is why this behavior surprises me. Only updates to Node.js and Meshcentral were performed.
Your config.json file This is what our configuration looks like, of course, we have changed all sensitive data.