We are using bind unix@/var/run/haproxy-host-<FQDN> ssl crt <CERT_PATH> but that socket
path is limited to 107 chars:
<path> is a UNIX socket path beginning with a slash ('/'). This is
alternative to the TCP listening port. Haproxy will then
receive UNIX connections on the socket located at this place.
The path must begin with a slash and by default is absolute.
It can be relative to the prefix defined by "unix-bind" in
the global section. Note that the total length of the prefix
followed by the socket path cannot exceed some system limits
for UNIX sockets, which commonly are set to 107 characters.
We could use use md5 hash of FQDN to avoid this, or perhaps service name.
That should be a simple change here and here
We are using
bind unix@/var/run/haproxy-host-<FQDN> ssl crt <CERT_PATH>but that socketpath is limited to 107 chars:
We could use use md5 hash of FQDN to avoid this, or perhaps service name.
That should be a simple change here and here