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

Liam Moncur liam at moncur.me.uk
Fri Apr 3 14:07:00 UTC 2020


It seems to related to apache set ups on the origin that were running openssl 1.1.1e since the upgrade to 1.1.1f it seems better and the SSL_read errors are gone.

https://github.com/openssl/openssl/issues/11381#issuecomment-607732081

Liam

Sent from ProtonMail mobile

-------- Original Message --------
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 Message ‐‐‐‐‐‐‐
> On Thursday, April 2, 2020 2:26 PM, Liam Moncur <liam at moncur.me.uk> wrote:
>
>> 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 reading response header from upstream, client: 2a00:23c6:8238:6501:54e9:28f4:54e:1a91, server: www.findafishingboat.com, request: "GET /boat-list/fishing-boats-for-sale-over-15m HTTP/2.0", upstream: "https://194.39.167.98:443/boat-list/fishing-boats-for-sale-over-15m", host: "www.findafishingboat.com"
>>
>> Then shortly after I get a loop of the following:
>>
>> 2020/04/02 14:09:10 [debug] 12875#12875: *338 http write filter 0000000000000000
>> 2020/04/02 14:09:10 [debug] 12875#12875: *338 http copy filter: -2 "/boat-list/fishing-boats-for-sale-over-15m?"
>> 2020/04/02 14:09:10 [debug] 12875#12875: *338 http output filter "/boat-list/fishing-boats-for-sale-over-15m?"
>> 2020/04/02 14:09:10 [debug] 12875#12875: *338 http copy filter: "/boat-list/fishing-boats-for-sale-over-15m?"
>> 2020/04/02 14:09:10 [debug] 12875#12875: *338 lua capture body filter, uri "/boat-list/fishing-boats-for-sale-over-15m"
>> 2020/04/02 14:09:10 [debug] 12875#12875: *338 http postpone filter "/boat-list/fishing-boats-for-sale-over-15m?" 0000000000000000
>> 2020/04/02 14:09:10 [debug] 12875#12875: *338 http write filter: l:0 f:0 s:0
>> 2020/04/02 14:09:10 [debug] 12875#12875: *338 http write filter limit 0
>> 2020/04/02 14:09:10 [debug] 12875#12875: *338 http write filter 0000000000000000
>> 2020/04/02 14:09:10 [debug] 12875#12875: *338 http copy filter: -2 "/boat-list/fishing-boats-for-sale-over-15m?"
>> 2020/04/02 14:09:10 [debug] 12875#12875: *338 http output filter "/boat-list/fishing-boats-for-sale-over-15m?"
>> 2020/04/02 14:09:10 [debug] 12875#12875: *338 http copy filter: "/boat-list/fishing-boats-for-sale-over-15m?"
>> 2020/04/02 14:09:10 [debug] 12875#12875: *338 lua capture body filter, uri "/boat-list/fishing-boats-for-sale-over-15m"
>> 2020/04/02 14:09:10 [debug] 12875#12875: *338 http postpone filter "/boat-list/fishing-boats-for-sale-over-15m?" 0000000000000000
>> 2020/04/02 14:09:10 [debug] 12875#12875: *338 http write filter: l:0 f:0 s:0
>> 2020/04/02 14:09:10 [debug] 12875#12875: *338 http write filter limit 0
>>
>> Any thoughts would be lovely.
>>
>> Thanks,
>> Liam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20200403/f259f7d1/attachment.htm>


More information about the nginx mailing list