大网数据广告活动
服务器运维问答

nginx reverse-proxy upgrade from nginx 1.17 to nginx 1.18 gives SSL error

· 52CE 我爱测

I am having trouble upgrading nginx from 1.17 to 1.18 (or .19, .20) Everything works ok on 1.17, but higher versions give this error: 2021/08/27 01:14:45 [error] 22#22: *8 peer closed connection in SSL handshake (104: Connection …

问题原文

原帖链接 · Fernando Fabreti · CC BY-SA 4.0

I am having trouble upgrading nginx from 1.17 to 1.18 (or .19, .20) Everything works ok on 1.17, but higher versions give this error:

2021/08/27 01:14:45 [error] 22#22: *8 peer closed connection in SSL handshake (104: Connection reset by peer) while SSL handshaking to upstream, client: 192.168.**.**, server: api*******.hm.*******.gov.br, request: "GET /favicon.ico HTTP/1.1", upstream: "https://192.168.**.**:443/favicon.ico", host: "api*******.hm.********.gov.br"

The error only happens when upstream is a internal IIS server. When upstream is another nginx it works with versions above 1.17

config is basically:

location  / {
    proxy_pass https://$host.***.br$uri$is_args$args;

I tried to use proxy_ssl_verify off without success. IIS certificate is self-generated.

Please advise

已采纳解答

原帖链接 · Tero Kilkanen · CC BY-SA 4.0

This looks like a problem with TLS versions. Maybe your backend IIS server isn't new enough to support TLS protocol that nginx requires?

Try adding proxy_ssl_protocols directive that contains the SSL / TLS versions your IIS supports.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2021-08-27)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。