Thanks Bruno,
I'll see if I can get this working.
--
Kevin
On 2020-09-09 9:41 p.m., Bruno Henc wrote:
Hi,
I take it that means theres no internal debug logging for the tls
errors that we can just expose via logfile?
Proof of concept patches are attached with build instructions. You may
Corrected build instructions attached. openssl-2.2.2.2 should be haproxy-2.2.3.
Regards,
Bruno
apt-debuild
Description: Binary data
Hi,
> I take it that means theres no internal debug logging for the tls errors that
> we can just expose via logfile?
Proof of concept patches are attached with build instructions. You may wish to
edit the haproxy-2.2.3/rules/debian folder to increase the -j setting to your
current number of
Thanks Bruno,
My first step would be to setup a custom log format that uses log
converters with the appropriate fetches [1]:
log-format "%ci:%cp [%tr] %ft %b/%s %TR/%Tw/%Tc/%Tr/%Ta %ST %B %CC %CS
%tsc %ac/%fc/%bc/%sc/%rc %sq/%bq %hr %hs %{+Q}r %[ssl_fc_protocol]
%[ssl_fc_cipher]"
For some
‐‐‐ Original Message ‐‐‐
On Tuesday, September 1, 2020 6:57 PM, Kevin McArthur
wrote:
> Hi haproxy
>
> I'm wondering if there is any way to debug the error message "www-https/1:
> SSL handshake failure"? I've tried increasing log levels to debug etc, but
> nothing seems to log about
Hi haproxy
I'm wondering if there is any way to debug the error message
"www-https/1: SSL handshake failure"? I've tried increasing log levels
to debug etc, but nothing seems to log about why the failure occurred.
Haproxy 2.2.2-1ppa1~focal on Ubuntu 20.04
We've had a strange regression when
6 matches
Mail list logo