Answer the question
In order to leave comments, you need to log in
After switching from apache to nginx + php-fpm, a strange problem began for a specific user. What could be the problem?
Greetings! I ran into a very interesting problem. After switching to nginx + php-fpm, only one user had problems with the project. The server responds to many of its actions: NetworkError: 500 Internal Server Error
At the same time, nothing is written to the logs.
At random, one of the problems (loading the map) was solved. In code
<? foreach ($map as &$hex) : ?>
...
<? endforeach; unset($hex); ?>
Answer the question
In order to leave comments, you need to log in
Enable php-fpm logging and read its log. Enable logging in nginx with debug mode, and read it. There was a similar problem due to the FireFox extension - FirePHP, very large headers were sent in response and the server responded with an error. Cookies have nothing to do with it, the useragent was guilty (the FirePHP text is sent in it, this is how the extension works), so try connecting from the console via curl, for example - read the logs, see the headers.
Is the user's login by chance something like "';DROP TABLE "? :)
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question