I installed nginx through yum in a local virtual machine. The installation was normal, but the access times were 403,
So check the nginx log, the path is /var/log/nginx/error.log. Open the log and find the error Permission denied. The detailed error is as follows:
1. open() "/data/www/1.txt" failed (13: Permission denied), client: 192.168.1.194, server: www. web1.com, request: "GET /1.txt HTTP/1.1", host: "www.web1.com"
No permission? So I found a lot of information and can solve this problem through the following four steps. You may just have a problem with the previous configuration, and you may not necessarily use all four steps.
1. Due to the inconsistency between the startup user and the nginx working user
1.1 Check the startup user of nginx and find that it is nobody, but it is started with root
Command: ps aux | grep "nginx: worker process" | awk'{print $1}'
1.2 Change the user of nginx.config to be consistent with the startup user,
Command: vi conf/nginx.conf
2. The index.html or index.php file is missing, which is the file specified in the index index.html index.htm line in the configuration file.
1. server {
2. listen 80;
3. server_name localhost;
4. index index.php index.html ;
5. root /data/www/;
6. }
If there is no index.php, index.html under /data/www/, Direct file will report 403 forbidden.
3. Permission issues. If nginx does not have permission to operate the web directory, a 403 error will also occur.
Solution: Modify the read and write permissions of the web directory, or change the startup user of nginx to the user of the directory, and restart Nginx to solve the problem
1. chmod -R 777 /data
2. chmod -R 777 /data/www/
4. The reason why SELinux is set to the open state (enabled).
4.1. Check the current status of selinux.
1. /usr/sbin/sestatus
4.2. Change SELINUX=enforcing to SELINUX=disabled state.
1. vi /etc/selinux/config
2.
3. #SELINUX=enforcing
4. SELINUX=disabled
4.3. Restart to take effect. reboot.
1. reboot
For more Nginx related technical articles, please visit the Nginx Tutorial column to learn!
The above is the detailed content of How to solve nginx 403. For more information, please follow other related articles on the PHP Chinese website!

NGINX is suitable for handling high concurrent requests, while Apache is suitable for scenarios where complex configurations and functional extensions are required. 1.NGINX adopts an event-driven, non-blocking architecture, and is suitable for high concurrency environments. 2. Apache adopts process or thread model to provide a rich module ecosystem that is suitable for complex configuration needs.

NGINX can be used to improve website performance, security, and scalability. 1) As a reverse proxy and load balancer, NGINX can optimize back-end services and share traffic. 2) Through event-driven and asynchronous architecture, NGINX efficiently handles high concurrent connections. 3) Configuration files allow flexible definition of rules, such as static file service and load balancing. 4) Optimization suggestions include enabling Gzip compression, using cache and tuning the worker process.

NGINXUnit supports multiple programming languages and is implemented through modular design. 1. Loading language module: Load the corresponding module according to the configuration file. 2. Application startup: Execute application code when the calling language runs. 3. Request processing: forward the request to the application instance. 4. Response return: Return the processed response to the client.

NGINX and Apache have their own advantages and disadvantages and are suitable for different scenarios. 1.NGINX is suitable for high concurrency and low resource consumption scenarios. 2. Apache is suitable for scenarios where complex configurations and rich modules are required. By comparing their core features, performance differences, and best practices, you can help you choose the server software that best suits your needs.

Question: How to start Nginx? Answer: Install Nginx Startup Nginx Verification Nginx Is Nginx Started Explore other startup options Automatically start Nginx

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.

To shut down the Nginx service, follow these steps: Determine the installation type: Red Hat/CentOS (systemctl status nginx) or Debian/Ubuntu (service nginx status) Stop the service: Red Hat/CentOS (systemctl stop nginx) or Debian/Ubuntu (service nginx stop) Disable automatic startup (optional): Red Hat/CentOS (systemctl disabled nginx) or Debian/Ubuntu (syst

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.


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

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

MinGW - Minimalist GNU for Windows
This project is in the process of being migrated to osdn.net/projects/mingw, you can continue to follow us there. MinGW: A native Windows port of the GNU Compiler Collection (GCC), freely distributable import libraries and header files for building native Windows applications; includes extensions to the MSVC runtime to support C99 functionality. All MinGW software can run on 64-bit Windows platforms.

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

WebStorm Mac version
Useful JavaScript development tools

Dreamweaver Mac version
Visual web development tools

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