Re: nginx serving wrong proxy content, static assets not affected

2023-01-05 Thread Eduardo Kortright
I'll bet that's it! There is nothing in my configuration that makes the IP addresses of the containers in the Docker network stay fixed. I would not be surprised if, when two or more containers are restarted (as they probably are every once in a while when logrotate runs), some or all of them

Re: nginx serving wrong proxy content, static assets not affected

2023-01-05 Thread Ángel
On 2023-01-03 at 20:54 +, Eduardo Kortright wrote: > I have no idea what triggers this behavior. Once it happens, the only > thing that can be done to correct it is to restart nginx. After that > (could be minutes, hours, or days), the server will function as > expected once again. Since I am u

Re: Upstream service php-fpm is up and running but reports {"errors": {"status_code": 502,"status": "php-fpm server is down"}}

2023-01-05 Thread Dan Swaney
Have you tried enabling "debug" mode logging and checked the log file for more details? For example, modify the settings in your nginx.conf and restart the nginx service: error_log /dev/stdout debug; http { access_log /dev/stdout; ... } On Thu, Dec 15, 2022, 11:23 AM Kaushal Shriyan wrote

Re: Upstream service php-fpm is up and running but reports {"errors": {"status_code": 502,"status": "php-fpm server is down"}}

2023-01-05 Thread Kaushal Shriyan
Hi, I will appreciate if someone can pitch in for my earlier post to this mailing list. I have the below location block. location /apis { # First attempt to serve request as file, then # as directory, then fall back to displaying a 404. fastcgi_intercept_err