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
Hello,
I've had a problem since I upgraded the mesh server to version 1.1.32 and generated an https certificate that we applied to the server.
node in v17.4
I was surprised when I installed version 1.1.32 that mesh took into account the customization of the agent in the json configuration, resulting in a reinstallation of mesh in a different directory on all my workstations.
Once the server is launched, I get this continuous spam message:
A previous ticket had been opened and solved by reinstalling two PCs, but now it's impossible to reinstall everything and clearly identify the source of the problem.
An idea
Best regards,
The text was updated successfully, but these errors were encountered:
Finally I found 9 computer in default, I managed to uninstall and reinstall mesh on 8 computer remotely via psexec and I still have 1 on which I should intervene physically.
I've checked the dns of the workstations, which are the same as the workstations with no problems, so I don't think there's a dns entry problem.
Difficult to understand, maybe I'll try with a wireshark on the last pc to try to find an explanation and I'll give you my feedback next week.
Have a nice weekend.
Hello,
I've had a problem since I upgraded the mesh server to version 1.1.32 and generated an https certificate that we applied to the server.
node in v17.4
I was surprised when I installed version 1.1.32 that mesh took into account the customization of the agent in the json configuration, resulting in a reinstallation of mesh in a different directory on all my workstations.
Once the server is launched, I get this continuous spam message:
A previous ticket had been opened and solved by reinstalling two PCs, but now it's impossible to reinstall everything and clearly identify the source of the problem.
An idea
Best regards,
The text was updated successfully, but these errors were encountered: