From 9dba6baccff604a815256119b4842d63ad6b4077 Mon Sep 17 00:00:00 2001 From: Vuong Hoang Date: Fri, 2 Oct 2026 09:06:49 -0700 Subject: [PATCH] homepage: NH3-PVE-AMT card opens MeshCentral (AMT now phones home; LAN management is off) --- stacks/homepage/conf/services.yaml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/stacks/homepage/conf/services.yaml b/stacks/homepage/conf/services.yaml index 5d5628e..fb5d9bf 100644 --- a/stacks/homepage/conf/services.yaml +++ b/stacks/homepage/conf/services.yaml @@ -193,13 +193,13 @@ icon: si-proxmox description: Proxmox hypervisor (nh3-pve) # Intel AMT on nh3-pve's I226-LM (UDM port 6, nh3-mgmt, DHCP reservation). - # No siteMonitor/ping on purpose: AMT drops ICMP, and its TLS needs legacy - # renegotiation, which Homepage's fetch refuses, so a monitor reads DOWN forever. - # Remote screen needs MeshCommander, not this page (servers/nh3-pve/README.md). + # Since 2026-10-02 it PHONES HOME (CIRA) to TacticalRMM's MeshCentral and refuses LAN + # management, so the card opens MeshCentral (group PFI-AMT, device nh3-pve-amt), not + # 10.100.250.61:16993. No siteMonitor: MeshCentral shows the tunnel state itself. - NH3-PVE-AMT: - href: https://10.100.250.61:16993/ + href: https://rmm-mesh.phasefinal.com/ icon: si-intel - description: Intel AMT (vPro) — OOB for nh3-pve; login admin / MEBx password + description: Intel AMT OOB for nh3-pve — via MeshCentral (PFI-AMT / nh3-pve-amt) - NH3-VM-Docker: href: http://10.100.50.40:5001 icon: si-docker