From 8cd7031fa0f07d7b3c72232cffd0741aa31f509d Mon Sep 17 00:00:00 2001 From: Kevin Fenzi Date: Thu, 10 Jan 2019 18:22:05 +0000 Subject: [PATCH] haproxy: fix haproxy config to listen for the fedmsgs that fedmsg-gateway emits. Turns out that 'localhost' resolves to ::1 now, but we aren't using ipv6 here but ipv4, so haproxy was listening in the wrong place for fedmsgs to appear. Signed-off-by: Kevin Fenzi --- roles/haproxy/templates/haproxy.cfg | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/haproxy/templates/haproxy.cfg b/roles/haproxy/templates/haproxy.cfg index e88684675c..1fe79f4294 100644 --- a/roles/haproxy/templates/haproxy.cfg +++ b/roles/haproxy/templates/haproxy.cfg @@ -599,7 +599,7 @@ backend fedmsg-raw-zmq-outbound-backend timeout queue 5000 timeout server 86400000 timeout connect 86400000 - server localhost localhost:9942 weight 1 maxconn 16384 + server localhost 127.0.0.1:9942 weight 1 maxconn 16384 # While the above fedmsg-raw-zmq-outbound forwards incoming connections to an # instance of the "fedmsg-gateway" daemon (which pushes internal messages out),