1
Nginx and Apache present errors differently when there is a problem running a PHP script. Apache, when configured to display on screen, displays exactly the error, with file and line where it occurred, but Nginx usually displays only something like 502 bad gateway.
Most solutions, even in stackoverflow.com at most help you set up NGinx
and the PHP-FPM
to direct errors to a text file, but I personally could not get Nginx to display the errors exactly like the Apache would. I understand that in production it is not ideal to display screen errors to the user, but a constant problem when using Nginx instead of Apache for a developer to test their application is that most have difficulty debugging just by looking at log files.
For exactly specifies that it is all possible errors that theoretically Nginx could display. If a php-fpm worker is not active or has serious problems it would be acceptable to still have the same errors
Some user with enough score could create the tag
php-fpm
please? Not yet in en SO.– Emerson Rocha