Troubleshoot the causes and solutions of "504 Gateway Timeout" on WordPress website

It is also common to see "504 Gateway Timeout" error prompt after the website is opened. If you remember correctly, Lao Zuo had such a problem when generating static state in a dream making CMS program last year（ 504 gateway time-out problem occurs on the static page generated by dream weaving CMS program ）。 Today, I encountered a WordPress website with this problem. How can I solve it?

Here, Lao Zuo records the troubleshooting process to solve the "504 Gateway Timeout" problem on the current WordPress website.

Step 1. Access by different browsers

Sometimes it is caused by the cache problem of our browser. So I asked my colleagues to change their browsers to visit it. I also opened Chrome and Edge browsers separately. It really exists. It seems that there is a fault.

Step 2. Prohibit plug-ins and themes

I don't log in to the server directly here. I logged in to the FTP account first, and then changed the name of the theme and plug-in folder of the WP program at will, so that all themes and plug-ins could be logged out. Then we opened the website, and the problem remained. It seems that the problem lies in the server, not in the WP site itself.

Step 3: Check the server configuration

The login server panel and SSH remote can be opened here. Directly check the Nginx of the current site. First, I use the remote command to check whether the current BT panel is running normally, but it is detected that there is a failure Nginx failure error. It seems that the problem is here. I think it was this student who failed in collecting big data.

So when I logged in to his BT panel and restarted and Nginx still failed, I simply uninstalled and reinstalled Nginx. The problem was solved.

Therefore, through the troubleshooting of the "504 Gateway Timeout" problem, it can be seen that the Nginx failure is caused by his collection of big data.