A question about Nginx reverse proxy
I am starting to tinker with nginx for the first time, please understand the newbie issues, thank you!
Nginx can reverse proxy Apache to process the dynamic part into a LANMP combination.
I have a few questions from this:
1. Is Apache in LANMP scenario apache mod_php? Or apache php-fpm or fcgi, etc. can be used?
2. Does nginx php-fpm under LNMP also process .php? Is combining LANMP and Apache just to solve the stability problem under LNMP?
3. If the LANMP architecture uses apache php-fpm, is it better to use LNMP directly? Are the instability factors mainly in php-fpm?
4. It is said that the performance of mod_php is not as good as php-fpm. If LANMP is built to pursue the stability or scalability of apache mod_php, then will LANMP be inferior to LNMP in terms of performance?
Reply content:
I’m starting to tinker with nginx for the first time, please understand the novice questions, thank you!
Nginx can reverse proxy Apache to process the dynamic part into a LANMP combination.
I have a few questions from this:
1. Is Apache in LANMP scenario apache mod_php? Or apache php-fpm or fcgi, etc. can be used?
2. Does nginx php-fpm under LNMP also process .php? Is combining LANMP and Apache just to solve the stability problem under LNMP?
3. If the LANMP architecture uses apache php-fpm, is it better to use LNMP directly? Are the instability factors mainly in php-fpm?
4. It is said that the performance of mod_php is not as good as php-fpm. If LANMP is built to pursue the stability or scalability of apache mod_php, then will LANMP be inferior to LNMP in terms of performance?
1. Generally speaking, apache mod_php;
2. In terms of performance, nginx handles static files better than apache, and the mod loading method of apache mod_php has better performance than nginx php-fpm. Combining LANMP is for optimal performance;
3. apache php-fpm, I have not seen anyone using it so far. Because Apache's internal processing mechanism is very strong, it is usually made into a mod. On the contrary, nginx does almost nothing by itself, and everything is handled externally.
4. I have never heard that the performance of mod_php is not as good as php-fpm. To be precise, this is related to the traffic model.
And in terms of performance, ordinary low-end servers cannot show any obvious difference between the two. Of course, if you use the default configuration file, then nginx with more static requests will definitely win. Just the memory consumed by apache after starting will give you the illusion of being a big boss. However, in fact, just for the warm-up exercise of dynamic processing, it has already surpassed nginx, a small engine that can only do static and forwarding.
1.php generally does not limit whether it is mod_php, php-fpm or fcgi, it depends on your php version. Nowadays, php-fpm is generally used. This only refers to php
2.nginx only does reverse proxy, right? Of course, nginx can also be used as a server, but it should not be used as a server here.
3. The instability factor may not necessarily be in php-fpm, but may also be in the concurrent processing middleware. For details, you can search and compare the performance advantages of apache and nginx.
4. Generally speaking, there may be some differences in ease of use and stability as the system grows. Simple architecture may not have much impact.

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



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.

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

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.

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.

In Linux, use the following command to check whether Nginx is started: systemctl status nginx judges based on the command output: If "Active: active (running)" is displayed, Nginx is started. If "Active: inactive (dead)" is displayed, Nginx is stopped.

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.
