Why does nginx appear 404
General reason: The requested Header
is too large
Solution: Configure nginx.conf
Related settings
client_header_buffer_size 16k;
large_client_header_buffers 4 64k;
Other common reasons:
413 Request Entity Too Large
General reasons: usually appear when uploading files
Solution: Configure nginx.conf related settings
client_max_body_size 10m;
Configure php.ini as follows (required Consistent with nginx.conf configuration)
post_max_size=10Mupload_max_filesize=2M
499 Client Closed Request
General reason: The client is waiting for the server to respond The client descriptor is closed before returning. It usually occurs when the client actively closes the socket after setting a timeout.
Solution: Modify the client timeout based on the actual processing time of the Nginx backend server.
500 Internal Server Rrror
General reasons: script error, (php syntax error, lua syntax error)
The number of visits is too large, system resources Restrictions, cannot open too many files
Insufficient disk space. (Enabling access log may cause disk overflow. Close it)
Solution: Check nginx_err_log php_err_log for syntax errors.
File visits:
1. Modify the nginx configuration file
worker_rlimit_nofile 65535;
2. Modify /etc/security/limits.conf
* soft nofile 65535* hard nofile 65535
502 Bad Gateway, 503 Serveice Unavailable
General reasons: The back-end service cannot be processed and the business is interrupted.
Solution: Obtain the error cause from the backend log and solve the backend server problem.
504 Gateway Timeout
General reason: The backend server did not respond to the Nginx proxy request within the timeout period
Solution: According to the backend server According to the actual processing situation, adjust the backend request timeout.
proxy_read_timeout 90;proxy_send_timeout 90;
General reason: The website page cache may be large, and the fastcgi default process response cache area is 8k
Solution: Configure nginx.conf related settings
fastcgi_buffers 8 128ksend_timeout 60;
For more Nginx related technical articles, please visit the Nginx Tutorial column Get studying!
The above is the detailed content of Why does nginx appear 404. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

You can query the Docker container name by following the steps: List all containers (docker ps). Filter the container list (using the grep command). Gets the container name (located in the "NAMES" column).

The methods that can query the Nginx version are: use the nginx -v command; view the version directive in the nginx.conf file; open the Nginx error page and view the page title.

How to configure an Nginx domain name on a cloud server: Create an A record pointing to the public IP address of the cloud server. Add virtual host blocks in the Nginx configuration file, specifying the listening port, domain name, and website root directory. Restart Nginx to apply the changes. Access the domain name test configuration. Other notes: Install the SSL certificate to enable HTTPS, ensure that the firewall allows port 80 traffic, and wait for DNS resolution to take effect.

How to configure Nginx in Windows? Install Nginx and create a virtual host configuration. Modify the main configuration file and include the virtual host configuration. Start or reload Nginx. Test the configuration and view the website. Selectively enable SSL and configure SSL certificates. Selectively set the firewall to allow port 80 and 443 traffic.

How to confirm whether Nginx is started: 1. Use the command line: systemctl status nginx (Linux/Unix), netstat -ano | findstr 80 (Windows); 2. Check whether port 80 is open; 3. Check the Nginx startup message in the system log; 4. Use third-party tools, such as Nagios, Zabbix, and Icinga.

Create a container in Docker: 1. Pull the image: docker pull [mirror name] 2. Create a container: docker run [Options] [mirror name] [Command] 3. Start the container: docker start [Container name]

Starting an Nginx server requires different steps according to different operating systems: Linux/Unix system: Install the Nginx package (for example, using apt-get or yum). Use systemctl to start an Nginx service (for example, sudo systemctl start nginx). Windows system: Download and install Windows binary files. Start Nginx using the nginx.exe executable (for example, nginx.exe -c conf\nginx.conf). No matter which operating system you use, you can access the server IP

Docker container startup steps: Pull the container image: Run "docker pull [mirror name]". Create a container: Use "docker create [options] [mirror name] [commands and parameters]". Start the container: Execute "docker start [Container name or ID]". Check container status: Verify that the container is running with "docker ps".
