Linux MeshAgent Continuous reconnection

[Coolguy3289]

On a Linux Mint 20.1 desktop, with MeshAgent installed, the workstation has registered to the MeshCentral server, but I was seeing agent disconnections on the server GUI. When running the meshagent manually I'm seeing the following over and over again, and I'm looking for some insight to this error and what can be done to fix this:

Connecting to: wss://meshcentral.domain.com:443/agent.ashx
Connected.
Server verified meshcore... Launching meshcore...
Mesh Server Connection Error [13]
Connecting to: wss://meshcentral.domain.com:443/agent.ashx
Connected.
Server verified meshcore... meshcore already running...
Mesh Server Connection Error [13]
Connecting to: wss://meshcentral.domain.com:443/agent.ashx
^CConnected.

[si458]

what version of meshcentral are you running
what nodejs version
what database are you using
do you use a reverse proxy or direct ssl access
is your certificate self-signed or valid/trusted for the web site?
what does your config.json look like (hide secret info like passwords/domain names)

[Coolguy3289]

what version of meshcentral are you running

MeshCentral v1.1.38, Hybrid (LAN + WAN) mode, Production mode.

what nodejs version

v20.16.0

what database are you using

MongoDB

do you use a reverse proxy or direct ssl access

Nginx Reverse Proxy

is your certificate self-signed or valid/trusted for the web site?

Valid/Trusted SSL Cert via Nginx Reverse Proxy

what does your config.json look like (hide secret info like passwords/domain names)

{
  "$schema": "https://raw.githubusercontent.com/Ylianst/MeshCentral/master/meshcentral-config-schema.json",
  "__comment1__": "This is a simple configuration file, all values and sections that start with underscore (_) are ignored. Edit a section and remove the _ in front of the name. Refer to the user's guide for details.",
  "__comment2__": "See node_modules/meshcentral/sample-config-advanced.json for a more advanced example.",
  "settings": {
    "cert": "mc.domain.com",
    "MongoDb": "mongodb://127.0.0.1:27017/meshcentral",
    "_WANonly": true,
    "_LANonly": true,
    "port": 4430,
    "aliasPort": 443,
    "redirPort": 8000,
    "redirAliasPort": 443,
    "tlsOffload": "127.0.0.1",
    "trustedProxy": "127.0.0.1"
  },
  "domains": {
    "": {
      "title": "Remote Access",
      "title2": "Mesh",
      "_minify": true,
      "newAccounts": false,
      "_userNameIsEmail": true,
      "certUrl": "https://127.0.0.1",
      "authStrategies": {
        "azure": {
          "newAccounts": true,
          "clientid": "OMITTED",
          "clientsecret": "OMITTED",
          "tenantid": "OMITTED"
        }
      }
    }
  },
  "_letsencrypt": {
    "__comment__": "Requires NodeJS 8.x or better, Go to https://letsdebug.net/ first before trying Let's Encrypt.",
    "email": "myemail@mydomain.com",
    "names": "myserver.mydomain.com",
    "skipChallengeVerification": true,
    "production": false
  }
}

[Coolguy3289]

It's also important to note that this doesn't seem to be happening to every client, only specific ones such as the client with the info I mentioned in the original issue.

[Coolguy3289]

Don't mean to pester, but is there any further diagnostics I can do on this to help narrow down why this is happening?