I found the problem - thanks to your (Amaury) remark about the particular error message - : The ubuntu service I was starting referred to the binary /usr/sbin/haproxy while the built binary was installed in /usr/local/sbin/haproxy.
Not the noble way, but I exchanged the old binary against the new one and the config file works. Excuses for the confusion I have caused. -- Christoph > Am 08.11.2023 um 17:52 schrieb Amaury Denoyelle <adenoye...@haproxy.com>: > > On Wed, Nov 08, 2023 at 04:42:00PM +0100, Christoph Kukulies wrote: >> Christoph Kukulies >> k...@kukulies.org >> >> [...] >> which leads to haproxy failing on startup: >> Nov 8 16:38:28 mail haproxy[101582]: [ALERT] (101582) : parsing >> [/etc/haproxy/haproxy.cfg:26] : 'bind' : unsupported protocol family 2 for >> address 'quic4@0.0.0.0:443' >> So what can I do about it other than trusting upon the scripts and configs >> to work? Or ask here for help? > > This particular error message "unsupported protocol family" has been > removed in haproxy 2.6. Looks like you did not run the correct binary as > this does not corresponds to the version reported by -vv. Have you > ensure to run the binary directly on the command-line using an absolute > path ? > > -- > Amaury Denoyelle
smime.p7s
Description: S/MIME cryptographic signature