If any issue still occurs after this switch, than a very serious issue exists due to some (severe) error in the config files, which error can be a typo, a wrong usage of stanza. PS To explain a bit: steps 1 to 4 are forcing your Plesk instance to restart and/or to reset the (relevant) services, while still maintaining a proper config of Apache + Nginx (read: the proper config is initiated with the switch to Nginx with the FPM application served by Apache). I know my app is being called successfully because I'm tailing my PHP app's log and I can see it actively writing to the log. There are other ways to achieve the same, but the steps 1 to 4 form a procedure that is fairly easy and provides some control while trying to solve the issue: this kind of control is really recommended, because it will give you more insight into the exact root cause of the problem and/or on what domain(s) this root cause is present.ДЄnyway, hope the above helps a bit.but keep us posted! I'm using PHP and Apache with nginx for a reverse proxy, all on Docker, and I have a couple of long running calls that are timing after 60 seconds, resulting in a 504 Gateway Time-out.

If the problem still persists, just do the followingДЎ - try to find the offending and problematic domainsДў - open Plesk Panel and go to 'Domains > PHP Settings (click) > Select: FPM Application served by Apache'ДЈ - check whether the problem persists on the domain that has been changed in step 2Д¤ - follow steps 1 to 2 for each offending domain, if (and only if) the check in step 3 indicates that your problems are not reoccurring Issue is related to a FastCGI problem, so there is no reason to change Nginx conf and/or php.ini.ДЄ) revert the php.ini file to default values: the pm.max_children = 950 is a really bad choice - whatever you are trying to achieve, this is not a solutionДЇrom the nf file - they should not be in that file, for many reasons (one of them is that the nf can be overwritten at upgrades)Д¬) check whether the file /etc/nginx/conf.d/nf exists (if not, create it) and make the contents of that fileДЄnd reload Nginx configuration with the command: service nginx reload (or equivalently, run the command: nginx -s reload)Д) verify that the files /etc/nginx/nf and /etc/nginx/fastcgi_params contain the lineДЇastcgi_param SCRIPT_NAME $fastcgi_script_name ДЄs this is related to one of the error messages in the log output that you provided.

Nginx gateway timeout signal 15