Remember the troubleshooting process in which nginx reports 502 and 504 after migrating the server, causing the second-level domain name to be inaccessible

This article explains and records the troubleshooting process in which nginx reports 502 and 504 after migrating the server once, causing the second-level domain name to be inaccessible.

Report 502 Bad Gateway or 504 Gateway Time-out and return the log:

[error] 7#7: *4 connect() failed (110: Connection timed out) while connecting to upstream, client: xx.xx.xx.xx, server: xxx.xubingtao.cn, request: "GET /xxxx/index.html HTTP/1.1", upstream: "http://172.18.0.x:90xxx/xxx/index.html", host: "xxx.xubingtao.cn"

For details, visit my personal website: https://www.xubingtao.cn/?p=2479

Follow my public account to release all kinds of useful information for you every day.

Guess you like

Origin blog.csdn.net/xubingtao/article/details/110440030