MeshCentral: [Intel AMT] stuck on "Trying Credentials"

Describe the bug The general tab of my device shows that it’s “Trying Credentials”, and it hasn’t updated for days.

To Reproduce Steps to reproduce the behavior:

  1. Add an AMT-capable device in a group (AMT only, or AMT+agent, does not matter)
  2. Go to the general tab of the device
  3. See that it’s stuck on “Trying Credentials”
  4. See error

Expected behavior The credentials should be accepted, and the device should be manageable from the MeshCentral UI.

Screenshots Screenshot from 2024-04-02 12-54-29

Screenshot from 2024-04-02 12-55-03

Screenshot from 2024-04-02 12-55-47

Server Software (please complete the following information):

  • OS: CentOS Stream 9 (also tried on Debian 12)
  • Virtualization: Docker image (also tried the npm manual installation)
  • Network: LAN
  • Version: 1.1.22
  • Node: N/A

Remote Device (please complete the following information):

  • Device: Lenovo ThinkCentre M900
  • OS: N/A
  • Network: N/A
  • Current Core Version (if known): N/A

Additional context I can control my device without issues when using the “Intel AMT” tab, but all the other tabs don’t work until I go into it first.
It seems MeshCentral does not even attempt to connect, as if I try to enter wrong credentials, it doesn’t show up in the AMT logs (if I manually try to log in with wrong credentials, it’s reported).

Your config.json file

{
  "$schema": "https://raw.githubusercontent.com/Ylianst/MeshCentral/master/meshcentral-config-schema.json",
  "settings": {
    "plugins":{"enabled": false},
    "_mongoDb": null,
    "cert": "<my MeshCentral server FQDN here>",
    "_WANonly": true,
    "_LANonly": true,
    "sessionKey": "[…]",
    "port": 443,
    "_aliasPort": 443,
    "redirPort": 80,
    "_redirAliasPort": 80,
    "AgentPong": 300,
    "TLSOffload": false,
    "SelfUpdate": false,
    "AllowFraming": false,
    "WebRTC": false
  },
  "domains": {
    "": {
      "_title": "MyServer",
      "_title2": "Servername",
      "minify": true,
      "NewAccounts": true,
      "localSessionRecording": false,
      "_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
  }
}

About this issue

Most upvoted comments

Same issue here. Always just says Trying Credentials despite everything seeming to work just fine. 🤷🏻‍♂️

EDIT: By the way this is on a 6th gen i7-6700t and Intel® ME reports: Activated, v11.8.50, Trying Credentials. Also when you click on details it doesn’t display all the information that I get on my 12th gen i7-12700t which Intel® ME reports: v16.1.30, Activated, Admin Control Mode (ACM), Secured using TLS, Admin Credentials: Known. Hopefully this extra information may help. I’m willing to try anything needed…

EDIT2: I think this is a function of the various versions of AMT. I think the older versions don’t implement https on 16993 and therefore don’t populate the details tab in mesh central and also don’t “appear” to save credentials, even though they do actually save them. I can’t be certain if this is truly the case or why… but maybe the developers can look into this? My 12th gen machine only responds on https:16993 and DOES NOT respond on http:16992; this is the reverse for the 6th gen machine.