On 9/26/25 18:26, Bren wrote:
> Hello,
>
Hi
> We used to sync some stick tables on reload like this:
>
> peers local
> peer server 127.0.0.1:10000
>
> That was really slick. Now we've moved to using bind with SSL and I haven't
> been able to replicate the above setup.
>
> peers synced
> bind server:83 ssl crt cert.pem
> server server1
> server server2 IP:83 sni server2.domain.net
> server server3 IP:83 sni server3.domain.net
>
> Any way to sync stick tables to the local process on reload when using bind?
> We have some million+ tables that get flushed on reload so this would be real
> handy.
Normally if the server directive without address (here "server1", which
corresponds to the local server for which the bind settings are applied)
matches with the localpeer name it should be functionally equivalent to
the old "peer" writing style, thus the peers resync mechanism should
work as before
If it doesn't work as expected I suspect this may be related to the use
of SSL (perhaps haproxy fails to connect to itself using SSL), not to
the bind directive itself, I think the local server should contain SSL
related keywords so it may connect to itself with proper SSL settings,
and here "server1" lacks ssl-related settings while external servers
(server2, server3) do have ssl-related settings set.
Aurelien
