Hi! Trying to configure haproxy to act as a connection broker and load balancer for RDP (aka Microsoft Terminal Services).
While configuring the backend, I found haproxy choke on tcp-check connect port 3389 ssl with message: [ALERT] 242/124152 (6066) : parsing [/etc/haproxy/haproxy.cfg:33] : 'tcp-check connect' expects 'comment', 'port', 'send-proxy' or but got 'ssl' as argument. Within the handbook I find (section "tcp-check connect"): tcp-check connect port 443 ssl If it chokes on this -- is it a bug? Or anything else? # haproxy -v HA-Proxy version 1.7.9 2017/08/18 Copyright 2000-2017 Willy Tarreau <wi...@haproxy.org> backend bk_rdp mode tcp balance leastconn timeout server 1h timeout connect 4s log global option tcplog stick-table type string len 32 size 10k expire 8h peers nxmux stick on rdp_cookie(mstshash) option tcp-check tcp-check connect port 3389 ssl default-server inter 3s rise 2 fall 3 #server nxnode01 10.169.16.105:3389 weight 10 check #server nxnode02 10.169.16.106:3389 weight 10 check server nxnode03 10.169.16.107:3389 weight 10 check server nxnode04 10.169.16.108:3389 weight 10 check -- Thomas
