After a few days, AMT devices appears down in Meshcentral

[Poulpatine]

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

1. Go to MeshCentral home page
2. See your devices in unknown state whereas you can reach them with MeshCommander or directly.

Expected behavior Unreachable devices should be greyed out, reachable devices should appears as "AMT, Powered".

When the devices are down in MeshCentral we can still reach them with MeshCommander or directly on their embedded web-ui. AmtInfo is still responding when launched from OS. But it's impossible to have them back on MeshCentral interface.

Screenshots

If applicable, add screenshots to help explain your problem.

Server Software (please complete the following information):

• OS: Debian 11
• Virtualization: Docker
• Network: LAN with Traefik reverse proxy for MeshCentral
• Version: 1.1.1
• Node: v18.12.1

Client Device (please complete the following information):

• Device: Laptop
• OS: archLinux
• Network: VPN to MeshCentral
• Browser: Firefox v107
• MeshCentralRouter Version: [if applicable]

Remote Device (please complete the following information):

• Device: Intel NUC - AMT Only (no agent)
• OS: Debian 11
• Network: MeshCentral hosted in Docker. LAN to devices.
• Current Core Version (if known):

  {
  "meshVersion": "v1.1.1",
  "nodeVersion": "v18.12.1",
  "runMode": "LAN mode",
  "productionMode": true,
  "database": "MongoDB",
  "dbChangeStream": false,
  "dbBulkOperations": false,
  "platform": "linux",
  "arch": "x64",
  "pid": 29,
  "uptime": 16788.956189471,
  "cpuUsage": {
      "user": 23202483,
      "system": 4677049
  },
  "memoryUsage": {
      "rss": 118337536,
      "heapTotal": 51535872,
      "heapUsed": 41856568,
      "external": 49161951,
      "arrayBuffers": 48259439
  },
  "warnings": [],
  "allDevGroupManagers": []
  }

Additional context We have also another issue where AMT devices are unreachable after a few weeks. 16992/16993 are not even reachable anymore.

Your config.json file

{
  "$schema": "http://info.meshcentral.com/downloads/meshcentral-config-schema.json",
  "settings": {
    "plugins":{"enabled": false},
    "mongoDb": "mongodb://mongodbadmin:<REDACTED>@mongodb:27017",
    "WANonly": false,
    "LANonly": true,
    "sessionKey": "<REDACTED>",
    "port": 80,
    "redirPort": 0,
    "aliasPort": 443,
    "AgentPong": 300,
    "TLSOffload": true,
    "SelfUpdate": false,
    "AllowFraming": false,
    "WebRTC": false,
    "autoBackup": {
      "mongoDumpPath": "/usr/bin/mongodump",
      "backupIntervalHours": 24,
      "keepLastDaysBackup": 31,
      "backupPath": "/opt/meshcentral/meshcentral-backup",
      "zipPassword": "<REDACTED>"
    }
  },
  "domains": {
    "": {
      "title": "MeshCentral",
      "title2": "<REDACTED>",
      "minify": true,
      "newAccounts": true,
      "newAccountEmailDomains": [ "<REDACTED>" ],
      "orphanAgentUser": "<REDACTED>",
      "userNameIsEmail": true,
      "localSessionRecording": false
      }
    }
  }

Traefik configuration

  labels:
      - "traefik.enable=true"
      - "traefik.http.routers.meshcentral.entrypoints=web"
      - "traefik.http.routers.meshcentralsecure.entrypoints=websecure"
      - "traefik.http.routers.meshcentral.rule=Host(`meshcentral.<REDACTED>`)"
      - "traefik.http.routers.meshcentralsecure.rule=Host(`meshcentral.<REDACTED>`)"
      - "traefik.http.routers.meshcentral.middlewares=redirect-to-https"
      - "traefik.http.routers.meshcentralsecure.tls.certresolver=letsencrypt"
      - "traefik.http.middlewares.redirect-to-https.redirectscheme.scheme=https"

[bravery-only]

I also have this problem. This problem is mostly on mini cases that support Intel® AMT. The service runs, but the agent does not go online!!! When the agent service is restarted, it connects, but the system shuts down, and the Agentis offline again

[silversword411]

It's traefik, where's the websocket support?

[Poulpatine]

I also have this problem. This problem is mostly on mini cases that support Intel® AMT. The service runs, but the agent does not go online!!! When the agent service is restarted, it connects, but the system shuts down, and the Agentis offline again

I forgot to precise that we are not using agent, only AMT.

[scrav42]

+1 We're experiencing the same issue with a couple of Intel NUC devices that are AMT capable. The devices are accessible if they're rebooted, but end up appearing offline later. No issue accessing them using MeshCommander.

[dinger1986]

AMT @si458