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
shared/prometheus/alertmanager.yml
+2 -1
View File
@@ -2,7 +2,8 @@
# Deployed to /opt/alertmanager/config/alertmanager.yml on Dankclaw.
#
# The one delivery path is Signal. The webhook lands on the host-side
# signal-relay (a systemd user unit listening on 127.0.0.1:18093), which
# signal-relay (a systemd user unit listening on 169.254.1.2:18093, the
# host.containers.internal endpoint), which
# formats the group and hands it to signal-cli under Frank's existing
# account. There is deliberately no second receiver: a duplicate channel is
# how an alert starts arriving twice and getting muted everywhere.
shared/prometheus/prometheus.yml
+2 -2
View File
@@ -14,8 +14,8 @@ rule_files:
# The delivery half. Alertmanager runs on the same dankclaw_default network,
# so it is addressed by container name, like grafana and loki below. Its
# single receiver webhooks the host-side signal-relay (loopback :18093,
# reachable from the container only as host.containers.internal).
# single receiver webhooks the host-side signal-relay (169.254.1.2:18093,
# the host.containers.internal endpoint).
alerting:
alertmanagers:
- static_configs: