From 5ef502e7ccdbb59128075b5f0028e7f9f1ce3b3f Mon Sep 17 00:00:00 2001 From: Vuong Hoang Date: Mon, 27 Apr 2026 15:15:46 -0700 Subject: [PATCH] =?UTF-8?q?configs/homepage:=20re-enable=20irv-ml1-docker?= =?UTF-8?q?=20provider=20=E2=80=94=20host=20recovered=202026-04-25?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Driver bump survived after all (595.58.03, kernel 6.1.0-37, both GPUs detected and modules loaded). 5 GPU stacks back up clean (comfyui, cosyvoice, qwen3-tts, index-tts, parakeet — all healthy). Homepage discovery can resume polling 10.100.79.3:2375 over the WG tunnel. --- configs/homepage/docker.yaml | 13 +++---------- 1 file changed, 3 insertions(+), 10 deletions(-) diff --git a/configs/homepage/docker.yaml b/configs/homepage/docker.yaml index 8aba4fe..f47ca10 100644 --- a/configs/homepage/docker.yaml +++ b/configs/homepage/docker.yaml @@ -24,16 +24,9 @@ ana-ml2-docker: # irv-ml1 — reachable ONLY via WireGuard tunnel, so docker auto-discovery # traffic traverses the tunnel. If WG drops, homepage will show irv-ml1 # services as offline until reconnect. -# -# DISABLED 2026-04-26 because the host is down post-CUDA-upgrade -# (see STATUS.md "🟥 Blocked — irv-ml1 stalled"). The 20s-per-poll -# ETIMEDOUTs were drowning homepage's logs and apparently blocking -# the ana-pfi-docker discovery from completing — News group's Miniflux -# card never surfaced until this was commented out. Re-enable once -# irv-ml1 is back on the network. -# irv-ml1-docker: -# host: 10.100.79.3 -# port: 2375 +irv-ml1-docker: + host: 10.100.79.3 + port: 2375 # Example TLS socket (if/when a host moves off plaintext 2375): # ana-pfi-docker: