MeshCentral: Upgrade to 1.0.49 Unable to connect web socket, click to reconnect.

I just upgraded from 1.0.48 to 1.0.49. No other changes made. Now I’m getting this error after logging on: “Unable to connect web socket, click to reconnect.”

To Reproduce Steps to reproduce the behavior:

  1. Lot into MechCentral
  2. Error “Unable to connect web socket, click to reconnect.” appears
  3. If you click to reconnect, it takes you back to the login screen.

ce1bd645-1946-4caf-8484-6062c88ce033 1

Expected behavior You would normally see the list of systems after logging in.

Server Software (please complete the following information):

  • OS: Windows 10
  • Virtualization: N/A
  • Version: 1.0.49
  • Node: 16.16.0
  • Browser: Google Chrome 103.0.5060.114 64-bit

Remote Device (please complete the following information):

  • Device: Laptop / Desktop
  • LAN/WAN
  • OS: Windows 10
  • Version: 21H2

Config.json

{
  "settings": {
    "cert": "mesh.XXXXX.com",
    "_minify": true,
	"AllowHighQualityDesktop": true
  },
"letsencrypt": {
 "email": "XXX@XXXX.com",
 "names": "mesh.XXXX.com,
 "rsaKeySize": 3072,
 "production": true,
 "desktopMultiplex": true
}
}

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 19 (5 by maintainers)

Commits related to this issue

Most upvoted comments

Now it works! Thank you very much!

I removed the domain for the cookie as that is not going to work well for many people. I am almost done on the improved version with the fix.

Hello .

I confirm the bug. The problem appears on Chrome and Firefox when trying to access by IP address, not by hostname.

MeshCentral v1.0.50 is published. Cookies and web relay should both work.

Wow, that was quick! I Installed the update, but now the “MeshCentral” service doesn’t start at all.

It works! Thank you very much!

I tried logging in with clear cookies but that didn’t solve the problem. When accessing through the hostname - the problem does not appear.

Try clearing cookies It worked for me

@Ylianst Thank you, you’re amazing! That worked and both issues are resolved.

If you run node node_modules/meshcentral --help you should see this:

MeshCentral v1.0.50, remote computer management web portal.
This software is open source under Apache 2.0 license.
Details at: https://www.meshcentral.com

Run as a background service
   --install/uninstall               Install MeshCentral as a background service.
   --start/stop/restart              Control MeshCentral background service.

Run standalone, console application
   --user [username]                 Always login as [username] if account exists.
   --port [number]                   Web server port number.
   --redirport [number]              Creates an additional HTTP server to redirect users to the HTTPS server.
   --exactports                      Server must run with correct ports or exit.
   --noagentupdate                   Server will not update mesh agent native binaries.
   --nedbtodb                        Transfer all NeDB records into current database.
   --listuserids                     Show a list of a user identifiers in the database.
   --cert [name], (country), (org)   Create a web server certificate with [name] server name.
                                     country and organization can optionally be set.

Server recovery commands, use only when MeshCentral is offline.
   --createaccount [userid]          Create a new user account.
   --resetaccount [userid]           Unlock an account, disable 2FA and set a new account password.
   --adminaccount [userid]           Promote account to site administrator.

You can try:

node node_modules/meshcentral --uninstall
node node_modules/meshcentral --install