I'm having the same problem. You are lucky because even though I restarted php-fpm, it didn't go back to normal...by NaZz - Php-fpm Mailing List - English
Maxim Dounin Wrote: ------------------------------------------------------- > From nginx point of view, "your upstream server" is _exact_ thing > to dig into. Sounds like this Nginx guy you are talking about is the type of guy who never wants to admit his mistakes. :Dby NaZz - Nginx Mailing List - English
Okay, thank you...Sad story is that everything worked fine until I updated to latest Nginx version, that's why I came here. Oh wellby NaZz - Nginx Mailing List - English
I don't understand this "upstream" "upstream" "upstream backend server". The upstream is served by fastcgi - fpm.sock on my own server. How do I attend this problem? Where do I dig exactly?by NaZz - Nginx Mailing List - English
If its unrelated to nginx why are people suggesting to edit various settings in nginx.conf to fix this particular problem?by NaZz - Nginx Mailing List - English
Where should I dig exactly? I am using Nginx with PHP-FPM and I have checked the logs but I can't find anything. Where do I dig? I thought this is connected to Nginx configuration?by NaZz - Nginx Mailing List - English
Hello, thank you for help. Yes I have already tried that. (tried putting it to client_max_body_size 20M;) My php post_max_size and max_upload_filesize are = 20M (for the sake of fixing this problem)by NaZz - Nginx Mailing List - English
I have a joomla website and when I am trying to update a larger extension I get bad gateway (502) error. I am able to update all small (normal) extensions. I am getting this error in nginx error log: "upstream sent invalid status "-1 Copy failed" while reading response header from upstream" I have checked the php-fpm log and there is nothing there connected to this partby NaZz - Nginx Mailing List - English