MeshCentral: Peering is broken

Describe the bug Peers cannot connect. Agents connected with 1 peer appear offline in the others.

To Reproduce Setup peering as per https://www.youtube.com/watch?v=j8xIRGScju0 Same data folder and everything. For convenience I use mongodb Atlas. I will change to a local replica when it works.

dubug -peer server 1

PEER: OutPeer s2: Connecting to: wss://ip.of.server.2:443/meshserver.ashx
PEER: OutPeer s2: Connected
PEER: OutPeer: BAD MESSAGE(A1)
PEER: OutPeer s2: Disconnected

server 2

PEER: InPeer: Connected (ip.of.server.1)
PEER: InPeer: Soft disconnect null (ip.of.server.1)
PEER: InPeer disconnect undefined (ip.of.server.1)

Server Software (please complete the following information):

• OS: Ubuntu 22.04
• Virtualization: Docker (official image)
• Network: WAN, no proxy
• Version: 1.1.11
• Node: v18.17.1

Additional context I tried commenting out the “BAD MESSAGE” check to see how far it will go but it errors again in the next statement on line 107 with PEER: OutPeer: Server hash mismatch..

I then tried disabling TLS altogether and peering over ws:// but then errored out on line 130 with PEER: OutPeer: Server sign check failed.

Something is really wrong with the certificate comparison going on in multiserver.js

Your config.json file

{
  "$schema": "https://raw.githubusercontent.com/Ylianst/MeshCentral/master/meshcentral-config-schema.json",
  "settings": {
    "plugins":{"enabled": false},
    "mongoDb": "mongodb+srv://username:password@mycluster.mongodb.net/?retryWrites=true&w=majority&replicaSet=atlas-dvh64d-shard-0",
    "MongoDbBulkOperations": true,
    "mongoDbChangeStream": true,
    "cert": "my.domain",
    "SessionKey": "SOME_SESSION_KEY",
    "WANonly": true,
    "port": 443,
    "redirPort": 80,
    "AgentPong": 300,
    "SelfUpdate": false,
    "AllowFraming": false,
    "WebRTC": true,
  },
  "domains": {
    "": {
      "hide": 5,
      "newAccounts": false,
      "userNameIsEmail": true,
      "agentSelfGuestSharing": false
    },
    "my-second.domain": {
      "dns": "my-second.domain",
      "hide": 5,
      "newAccounts": false,
      "userNameIsEmail": true,
      "agentSelfGuestSharing": false
    }
  },
  "peers": {
    "serverId": "s1",
    "servers": {
      "s1": { "url": "wss://server.public.ip:443/" },
      "s2": { "url": "wss://server.public.ip:444/" }
    }
  }
}

In the second configuration file the only thing that changes is the serverId to s2 and I use docker port mapping to map the second instance’s ports to +1 (81,444,4434).