Thanks Maxim, Looks like the issue was a bad root cert in the chain. The CN was identical to what the intermediate called out but it wasn't the one that had issued the intermediate. Also didn't know that setting error to info would give us the ssl error information. We had it set to debug but couldn't figure anything out from that.by kpuscas - Nginx Mailing List - English
Our service uses 2-way ssl with our clients connecting to our systems. With each new client we add their intermediate and root CA chain to the concatenated certificates file used by ssl_client_certificate. We recently upgraded to 1.14.0 (and the included modules) and now some, but not all of our customers are unable to connect getting 400 errors. We've tried changing the order of the certificatesby kpuscas - Nginx Mailing List - English