Devices are not showing in MeshCentral

[darrieh]

Describe the bug
After MeshCentral is installed (following the official guide and using proper .yml files) I try to add a new device and install it on a Windows 11 Pro machine and nothing happens.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
I expected the device to show up in about 10ish minutes exactly like in the youtube videos that I was watching.

Screenshots
If applicable, add screenshots to help explain your problem.

Server Software (please complete the following information):

• OS: Ubuntu live server 22.04
• Virtualization: Docker compose
• Network: WAN
• Version:
• Node:

Client Device (please complete the following information):

• Device: Laptop
• OS: Windows 11 23H2
• Network: [e.g. Local to Meshcentral, Remote over WAN]
• Browser: Google Chrome
• MeshCentralRouter Version:

Remote Device (please complete the following information):

• Device: Laptop
• OS: Windows 11 23H2
• Network: Remote over WAN
• Current Core Version:

Additional context
I tried re-installing, restarting the docker container, editing the .json file and nothing helped.
The option to invite someone with an URL link to download the agent also does not work.

Your config.json file

{
  "$schema": "http://info.meshcentral.com/downloads/meshcentral-config-schema.json",
  "settings": {
    "cert": "10.101.1.111",
    "_WANonly": true,
    "_LANonly": true,
    "sessionKey": "N6wnKsJeNA4zjleWOaZK4SLgokexyyrc",
    "port": 443,
    "_aliasPort": 443,
    "redirPort": 80,
    "_redirAliasPort": 80,
    "AgentPong": 300,
    "TLSOffload": false,
    "SelfUpdate": false,
    "AllowFraming": "false",
    "WebRTC": "false",
    "AutoBackup": {
      "backupPath": "/opt/meshcentral/meshcentral-backups",
      "backupInvervalHours": 24,
      "keepLastDaysBackup": "10",
      "zippassword": "MyAwesomePasswordPleaseChangeMe"
    }
  },
  "domains": {
        "": {
        "_title": "MyServer",
    "_title2": "Servername",
    "_minify": true,
    "NewAccounts": "true",
        "_userNameIsEmail": true,
    "_certUrl": "my.reverse.proxy"
        }
  },
  "_letsencrypt": {
    "__comment__": "Requires NodeJS 8.x or better, Go to https://letsdebug.net/ first before>",
    "_email": "myemail@mydomain.com",
    "_names": "myserver.mydomain.com",
        "production": false
  }
}

[si458]

are u sure the device is Windows 11 23h2 and not 24h2? (thats a seperate issue if its 24h2)

can ur remote device access the web ui of meshcentral? (https://10.101.1.111 in your case)

also ideally you should use a DNS name instead of an IP address in cert because IP addresses can change!
where as dns can always point to a new ip address if needs be

[darrieh]

I am pretty sure it is 23H2 and I am able to open the admin panel from the remote machine (it is the same machine) by going to https://10.101.1.111:8086.

[si458]

https://10.101.1.111:8086/

ok so this is your issue,
meshcentral thinks you are using port: 443 (normal https without the :8086) because you have port set to 443,
and because you are docker, im also guessing you have ports set as 8086:443 in your compose/docker commands?

if you want to leave it set as port 8086, you can either
change port to 8086 and do the same for your compose/docker command 8086:8086
then restart and uninstall/redownload/reinstall the meshagent
OR
set aliasport: 8086 this tells meshcentral that
hey im listening on 443 BUT tell remote agents to talk to me on 8086 due to firewall or something else
this option is for the likes of firewalls where 443 isnt accessible AND in the case of docker as not everyone can use 443