dank/serverAppConfigs
1
0
Fork 0
Code Issues 6 Pull Requests Actions Packages Projects Releases Wiki Activity

relay: bind 169.254.1.2 (host.containers.internal), not loopback

Browse Source 
A socket bound to 127.0.0.1 refuses container traffic that arrives via
the podman bridge: the first live webhook failed with 'dial tcp
169.254.1.2:18093: connection refused'. The relay now binds the
host-gateway endpoint — link-local to the podman bridge, off the LAN —
and the deployer's health probe follows it there.
This commit is contained in:
Frank
2026-09-17 13:26:24 -07:00
parent 5f55efcb9d
commit 8f747a2104
9 changed files with 31 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files
dankclaw/observability/quadlet/prometheus.container
+2 -2
View File
@@ -29,8 +29,8 @@
# /etc/prometheus/rules/ (installed from shared/prometheus/rules/ by the
# deployer). Delivery went live 2026-09-17: the alerting block in
# prometheus.yml points at alertmanager:9093, which webhooks every firing
# group to the host-side Signal relay (127.0.0.1:18093, reached as
# host.containers.internal), which sends through signal-cli account 318311.
# group to the host-side Signal relay (169.254.1.2:18093, the
# host.containers.internal endpoint), which sends through signal-cli account 318311.
# The Grafana dashboard's ALERTS panel remains the second surface.
#
# The config volume is also why rules belong in git: editing them in the UI is