MeshCentral: Intel AMT certificate provisioned with wrong common name FQDN | only works by IP

Describe the bug The certificate loaded during provisioning does not use the dedicated FQDN specified in AMT config, im not sure how to specify it (or reprovision?)

To Reproduce Steps to reproduce the behavior:

Configure AMT to use a dedicated IP and dedicated FQDN Provision with MeshCentral

curl https://10.0.0.124:16993 --insecure -v #works

curl https://IntelAMT-6398b0b2a9ff:16993 --insecure -v --resolve IntelAMT-6398b0b2a9ff:16993:10.0.0.124 #works

However curl https://dedicated-fqdn.xxx.yyy --insecure -v fails because the certificate doesnt match

Certificate: image

AMT config image

Expected behavior Maybe i did something out of order, but i’d expect the certificate loaded by MeshCentral to match the Computer Host Name . Domain Name

Screenshots See above

Server Software (please complete the following information):

  • OS: Debian 12
  • Virtualization: Proxmox LXC
  • Network: Local certificate by certbot (symlink’d)
  • Version: v1.1.33
  • Node: v20.18.1

Client Device (please complete the following information):

  • Device: Intel BNUC11TNHv70L00
  • OS: Proxmox
  • Network: Local
  • Browser: Google Chrome

Additional context Add any other context about the problem here.

Your config.json file

{
  "$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 th>
  "__comment2__": "See node_modules/meshcentral/sample-config-advanced.json for a more advanced example.",
  "settings": {
    "cert": "meshcentral.xxx.yyy",
    "_WANonly": true,
    "_LANonly": true,
    "_sessionKey": "MyReallySecretPassword1",
    "_redirAliasPort": 80,
    "_port": 80,
    "_redirPort": 81,
    "_aliasPort": 443,
    "_TLSOffload": false
  },
  "domains": {
    "": {
      "title": "XXX",
      "title2": "meshcentral",
      "_minify": true,
      "_newAccounts": true,
      "_userNameIsEmail": true,
      "agentConfig": [
        "webSocketMaskOverride=1"
      ],
      "certUrl": "https://meshcentral.xxx.yyy:443/"
    }
  },
  "_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
  }
}

About this issue

Most upvoted comments

@k1n6b0b I’m having a similar issue at the moment with my AMT v12 machine, it seems to be flaky with its DHCP lease and gets it when it feels like it as i can’t ping it and get a reply but that’s for the info about power mode, I will do some investigating

So the issue I’m having is none of my AMT CIRA stuff is working, maybe i’m following the wrong thread to debug

AMT: Start Management node//IsmcdV9$fjIO4@B4IHO9jhrTb6IfxGR8TGB61kTE5mH@I@46sGmIQ58Hj6Pflox8 2
AMT: pve4 Checking Intel AMT state...
AMT: pve4 Attempt Initial Contact CIRA-LMS
AMT: pve4 LMS-Connect TLS admin
AMT: pve4 Initial Contact Response 408
AMT: pve4 Attempt Initial Contact CIRA-LMS
AMT: pve4 LMS-Connect NoTLS admin
AMT: pve4 Initial Contact Response 408
AMT: pve4 Remove device node//IsmcdV9$fjIO4@B4IHO9jhrTb6IfxGR8TGB61kTE5mH@I@46sGmIQ58Hj6Pflox8 2 14

image image