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
scripts/deploy-remote.sh
+4 -3
View File
@@ -232,15 +232,16 @@ install_signal_relay() {
systemctl --user enable signal-relay.service
systemctl --user restart signal-relay.service
# The interpreter needs a moment to bind after restart; a one-shot curl
# raced the socket on 2026-09-17 and failed a healthy deploy.
# raced the socket on 2026-09-17 and failed a healthy deploy. The relay
# binds 169.254.1.2 (host.containers.internal), not loopback.
local i
for i in $(seq 1 15); do
if curl -fsS -m 5 http://127.0.0.1:18093/health >/dev/null; then
if curl -fsS -m 5 http://169.254.1.2:18093/health >/dev/null; then
return 0
fi
sleep 1
done
echo "signal-relay is not answering on 127.0.0.1:18093" >&2
echo "signal-relay is not answering on 169.254.1.2:18093" >&2
return 1
}