configs/homepage: re-enable irv-ml1-docker provider — host recovered 2026-04-25
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.
This commit is contained in:
@@ -24,16 +24,9 @@ ana-ml2-docker:
|
|||||||
# irv-ml1 — reachable ONLY via WireGuard tunnel, so docker auto-discovery
|
# irv-ml1 — reachable ONLY via WireGuard tunnel, so docker auto-discovery
|
||||||
# traffic traverses the tunnel. If WG drops, homepage will show irv-ml1
|
# traffic traverses the tunnel. If WG drops, homepage will show irv-ml1
|
||||||
# services as offline until reconnect.
|
# services as offline until reconnect.
|
||||||
#
|
irv-ml1-docker:
|
||||||
# DISABLED 2026-04-26 because the host is down post-CUDA-upgrade
|
host: 10.100.79.3
|
||||||
# (see STATUS.md "🟥 Blocked — irv-ml1 stalled"). The 20s-per-poll
|
port: 2375
|
||||||
# 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
|
|
||||||
|
|
||||||
# Example TLS socket (if/when a host moves off plaintext 2375):
|
# Example TLS socket (if/when a host moves off plaintext 2375):
|
||||||
# ana-pfi-docker:
|
# ana-pfi-docker:
|
||||||
|
|||||||
Reference in New Issue
Block a user