Home > Back-end >  Before and after the end of the separation, through nginx access, but the page 502 Bad Gateway
Before and after the end of the separation, through nginx access, but the page 502 Bad Gateway

Time:09-29

The log information is:
2020/04/15 17:44:44 [crit] # 12268:19088 * 3 SSL_do_handshake () failed (SSL: error: 14077102: SSL routines: SSL23_GET_SERVER_HELLO: unsupported protocol) while the SSL handshaking to upstream, client: 127.0.0.1, server: localhost, the request: "GET/RESMNG_F/resmng/report/segDistributeListAction HTTP/1.1", upstream: "https://127.0.0.1:8443/RESMNG_F/resmng/report/segDistributeListAction", host: "vop. Chinaunicom. Cn: 16010"
2020/04/15 17:44:44 [error] # 12268:19088 * 3 CreateFile () "D: \ workSoftware \ nginx 1.12.2/HTML/favicon. Ico" failed (2: The system always find The file specified), client: 127.0.0.1, server: localhost, The request: "GET/favicon. Ico HTTP/1.1", The host: "vop. Chinaunicom. Cn: 16010"
2020/04/15 17:44:44 [info] # 12268:19088 * 3 client 127.0.0.1 closed keepalive connection (10053: An established connection was aborted by the software in your host machine)

CodePudding user response:

Because nginx does not support the client's algorithm suites, 1. 2 renewable nginx modify ssl_ciphers configuration items

CodePudding user response:

Nginx solve the HTTPS proxy tomcat HTTP will be enough

CodePudding user response:

reference 1/f, you choose the city response:
because nginx does not support the client's algorithm suites, 1. Renewable nginx 2. Modify ssl_ciphers configuration items

The two modified ssl_cilphers configuration items is how to change
  • Related