• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

No input file specified

lvalics

Silver Pleskian
Plesk Guru
I installed a new servver with PLESk 11.5 and started to move domains there. When I test first domain I get "No input file specified" if is in FastCGI mode. NGINX wasn't enabled, so not this the case.
If I put it in Apache Module, all work fine (just I don't want that).
I tried to install NGINX and restart all but same error.
I tried to look in logs (error_log of the domain) but nothing helpful :-(

Anyone had this issue? I don't want to lose too much time with hunting down :-9
 
I found the issue, but it seems to me pretty strange that can happen.
Because of move from another server where it wasn't used FastCGI, it was a few folder 777 rights.

This created that message, which message wasn't very clear to be easy to debug.
Now I expect from PLESK that fix this in next release, that when I choose FastCGI or CGI, then execute 2 simple command.

find ./ -type d -exec chmod 0755 '{}' \;
find ./ -type f -exec chmod 0644 '{}' \;


This will solve the issues in many cases if before was used 777 rights
 
I found the issue, but it seems to me pretty strange that can happen.
Because of move from another server where it wasn't used FastCGI, it was a few folder 777 rights.

This created that message, which message wasn't very clear to be easy to debug.
Now I expect from PLESK that fix this in next release, that when I choose FastCGI or CGI, then execute 2 simple command.

find ./ -type d -exec chmod 0755 '{}' \;
find ./ -type f -exec chmod 0644 '{}' \;


This will solve the issues in many cases if before was used 777 rights

Hi.

In that folder you have to use the command?

Thanks
Alberto G.
 
Back
Top