Re: (SSL: error:1409441A:SSL routines:ssl3_read_bytes:tlsv1 alert decode error:SSL alert number 50) while reading response header from upstream

2020-04-03 Thread Liam Moncur
On 3 Apr 2020, 07:20, Liam Moncur wrote: > We were able to resolve this by enabling proxy_buffering. The root cause for > why it started happening is still being investigated. > > Thanks, > Liam > > Sent with ProtonMail Secure Email. > > ‐‐‐ Original Me

Re: (SSL: error:1409441A:SSL routines:ssl3_read_bytes:tlsv1 alert decode error:SSL alert number 50) while reading response header from upstream

2020-04-02 Thread Liam Moncur
We were able to resolve this by enabling proxy_buffering. The root cause for why it started happening is still being investigated. Thanks, Liam Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Thursday, April 2, 2020 2:26 PM, Liam Moncur wrote: > Hey, > I am see

(SSL: error:1409441A:SSL routines:ssl3_read_bytes:tlsv1 alert decode error:SSL alert number 50) while reading response header from upstream

2020-04-02 Thread Liam Moncur
Hey, I am seeing an issue where nginx seems to get stuck in a loop soon after the above error. From the debug I am seeing: 2020/04/02 14:09:10 [error] 12875#12875: *338 SSL_read() failed (SSL: error:1409441A:SSL routines:ssl3_read_bytes:tlsv1 alert decode error:SSL alert number 50) while readin