• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

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