• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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