Nginx reverse proxy 404 error and 500 error essay

Recently, I encountered two very interesting errors when configuring the company's Nginx reverse proxy backend Tomcat core machine. Mark them here

1. The project can be accessed normally. After refreshing, a 404 appears. After refreshing again, the access is normal.

After checking, I found that the error was caused by the Nginx setting of the front-end machine being load balanced, which evenly distributed external requests to the two back-end core machines, and one of them did not deploy the corresponding project. The problem was solved after redeployment

2. 500 caused by the database

It is worth mentioning that MySQL table names under WINDOWS are not case-sensitive, but they are case-sensitive under Linux. So I changed the table name in the SpringMVC model and the problem was solved.

What I want to say here is that I have seen many people asking about the cause of the 500 error. In fact, many times there is no need to do so. You can try to find the 500 problem yourself before asking. Reading the error page description and the following line, it is easy to find the crux of this issue. Find the corresponding information and solve it easily

The above is an introduction to the Nginx reverse proxy 404 error and 500 error essay, including the relevant content. I hope it will be helpful to friends who are interested in PHP tutorials.