About Nginx port mapping configuration method
This article mainly introduces the Nginx port mapping configuration method and multi-port mapping. The content is quite good. I will share it with you now and give it as a reference.
Antecedents
The traditional way to build a website is to use a web server to parse the file entry file, such as using Nginx or Apache to parse the corresponding entry. file, but with the development of technology, some languages can start a web service by themselves, such as Node and PHP. Using a development language to start a web service can only be accessed locally by default, such as http://localhost:8000/ http:// 127.0.0.1:8000/
But when we are developing and debugging the environment in Centos, we use a window browser for testing, so we need to use an intermediate web server for port mapping
Nginx port mapping configuration
server { listen 80; server_name rbac.dev-lu.com; # 80转发到8000端口 location / { proxy_pass http://127.0.0.1:8000; } }
nginx reverse proxy-multi-port mapping
Code Explanation
1.1 The default value of http:www.baidu.test.com is 80. Access "/" to use the reverse proxy, and then access the local 8083;
1.2 8083 represents the local front-end project access address , the front end needs to access the background data, "/", continue to proxy to the background address 9803;
1.3 In this way, multiple port access can be completed as long as port 80 is opened.
1.4 The root configuration can be an absolute path or a relative path.
server { listen 80; server_name www.baidu.test.com;#你要填写的域名,多个用逗号隔开 location / { proxy_pass http://localhost:8083; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; root /app/esop_web/esopschool; index index.html; try_files $uri $uri/ /index.html; } location /rest{ proxy_pass http://localhost:9803; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } }
The above is the entire content of this article. I hope it will be helpful to everyone’s study. For more related content, please pay attention to the PHP Chinese website!
Related recommendations:
About the binding operation of Laravel framework routing and controller
The above is the detailed content of About Nginx port mapping configuration method. 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

AI Hentai Generator
Generate AI Hentai for free.

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



How to fix Nginx 403 Forbidden error? Check file or directory permissions; 2. Check .htaccess file; 3. Check Nginx configuration file; 4. Restart Nginx. Other possible causes include firewall rules, SELinux settings, or application issues.

Answer to the question: 304 Not Modified error indicates that the browser has cached the latest resource version of the client request. Solution: 1. Clear the browser cache; 2. Disable the browser cache; 3. Configure Nginx to allow client cache; 4. Check file permissions; 5. Check file hash; 6. Disable CDN or reverse proxy cache; 7. Restart Nginx.

Steps to start Nginx in Linux: Check whether Nginx is installed. Use systemctl start nginx to start the Nginx service. Use systemctl enable nginx to enable automatic startup of Nginx at system startup. Use systemctl status nginx to verify that the startup is successful. Visit http://localhost in a web browser to view the default welcome page.

The server does not have permission to access the requested resource, resulting in a nginx 403 error. Solutions include: Check file permissions. Check the .htaccess configuration. Check nginx configuration. Configure SELinux permissions. Check the firewall rules. Troubleshoot other causes such as browser problems, server failures, or other possible errors.

There are two ways to solve the Nginx cross-domain problem: modify the cross-domain response header: add directives to allow cross-domain requests, specify allowed methods and headers, and set cache time. Use CORS modules: Enable modules and configure CORS rules that allow cross-domain requests, methods, headers, and cache times.

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.

The methods to view the running status of Nginx are: use the ps command to view the process status; view the Nginx configuration file /etc/nginx/nginx.conf; use the Nginx status module to enable the status endpoint; use monitoring tools such as Prometheus, Zabbix, or Nagios.

The error log is located in /var/log/nginx (Linux) or /usr/local/var/log/nginx (macOS). Use the command line to clean up the steps: 1. Back up the original log; 2. Create an empty file as a new log; 3. Restart the Nginx service. Automatic cleaning can also be used with third-party tools such as logrotate or configured.
