I'm normally not inept in compiling packages, using make, git, etc. and I believe I got it right .
The thing is: haproxy 2.4 could cope with my config line, at least it didn't bail out on reading the config. Whether the option was in effect might have been another question. Now, 2.8, complains about wrong syntax. I put it as a separate line in the global section at the beginning of the config file as someone - I believe it was Shawn - suggested. Haproxy seems to be running now. Is there a "testsuite" to test haproxy and its built in features from the outside? -- Christoph > Am 07.11.2023 um 14:38 schrieb Cyril Bonté <cyril.bo...@free.fr>: > > Hi, > > Le 07/11/2023 à 12:54, Christoph Kukulies a écrit : >> (...) Now haproxy fails on my config (which the former version 2.4 I was >> running before, didn't) >> This is the line in question: >> bind *:443 ssl crt /etc/haproxy/fullchain.pem crt ssl-skip-self-issued-ca >> How do I fix this? >> Put crt ssl-skip-self-issued-ca >> in a separate line? >> Where? > > It seems you're not expert in compiling haproxy and you missed some options > (I guess SSL is not enabled), which may also be a problem for you future > upgrades. > > Why not simply use available packages ? > > See https://haproxy.debian.net/ and > https://www.haproxy.com/blog/how-to-install-haproxy-on-ubuntu > > According to your previous information, it would result in: > https://haproxy.debian.net/#distribution=Ubuntu&release=jammy&version=2.8 > > -- > Cyril Bonté > >
smime.p7s
Description: S/MIME cryptographic signature
