Reputation: 1
Facing SSL handshake failure with the the below HAProxy configuration and Outage in our production environment.
Flow:
HAPROXY Configuration:
global
log /dev/log local0 debug
log /dev/log local1 notice
chroot /var/lib/haproxy
stats socket /run/haproxy/admin.sock mode 660 level admin expose-fd listeners
stats timeout 30s
user haproxy
group haproxy
daemon
###Default SSL material locations
ca-base /etc/haproxy/ssl
crt-base /etc/haproxy/ssl
log global
mode http
option httplog
option dontlognull
timeout connect 5000
timeout client 50000
timeout server 50000
errorfile 400 /etc/haproxy/errors/400.http
errorfile 504 /etc/haproxy/errors/504.http
frontend haproxy.service
bind *:80
bind *:443 ssl crt /etc/haproxy/ssl/test.pem ssl-min-ver TLSv1.2 ciphers ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256
http-request redirect scheme https unless { ssl_fc }
default_backend backend.services
backend backendservices
balance roundrobin
server backend.service 127.0.0.1:5001
I found in Internet that SSL handshake may happen due to the below scenarios
Outputs of the below related commands:
curl -v --tls-max 1.2 https://server.com/health
Error Message:
ALPN, server did not agree to a protocol
Solution for the SSL handshake failure
Cipher suite suggestions
What are the further areas we can test.
Suggestions/solutions to handle this error
ALPN, server did not agree to a protocol
Upvotes: 0
Views: 1229