- Node.js application shows the following error if PHP support is set as PHP FPM handler served by nginx in Domains > example.com > PHP Settings:
CONFIG_TEXT: 403 Forbidden
The following error may be found in
CONFIG_TEXT: 2017/02/03 09:29:53 [error] 11357#0: *5259384 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 203.0.113.2, server: example.com, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:///var/www/vhosts/system/example.com/php-fpm.sock:", host: "example.com"
The following rows can be found in
CONFIG_TEXT: [ E 2017-11-01 06:28:15.9276 989090/Ty age/Cor/App/Implementation.cpp:304 ]: Could not spawn process for application /home/httpd/vhosts/example.com/app.example.com: An error occurred while starting the web application. It exited before signalling successful startup back to Phusion Passenger.
Plesk does not support the scenario when PHP-FPM is being used along with Node.js on the same domain.
If it is needed to have 2 technologies on one site — both PHP and Node.js, it is recommended to use separate subdomains for each application.
For example, a site with PHP application —
www.example.com, chat as Node.js application —
Otherwise, change handler type from FPM to the FastCGI under Domains > example.com > PHP Settings.