Reputation: 10302

"No input file specified" with php Fast/CGI

I am trying to set a config for Nginx and am facing some issues.

In my sites-available there is default file which contains the below code:

server {
    server_name www.test.com test.com;
    access_log /sites/test/logs/access.log;
    error_log /sites/test/logs/error.log;
    root /sites/test;

 location ~ / {
    
index index.php
    include /etc/nginx/fastcgi_params;
    fastcgi_pass  127.0.0.1:9000;
    fastcgi_index index.php;
    fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
}

Above code works perfectly when I write URL

www.test.com/service/public/

when I write

www.test.com/service/public/testservice (testservice is folder within public) it says No input file specified.

How can this be fixed?

I tried below, but no luck

http://nginxlibrary.com/resolving-no-input-file-specified-error/
http://blog.martinfjordvald.com/2011/01/no-input-file-specified-with-php-and-nginx/

Upvotes: 28

Answers (20)

Michael Quad

Reputation: 330

THIS IS NOT NGINX!

it is an answer from PHP fastcgi that it cant reach document root. you have to specify correct paths for the php-cgi process

Upvotes: 0

Bruce Tong

Reputation: 1431

I set up Laravel Forge with Linode to run a static website from my github repo.

SSH into my Linode and verified that my html was updated however, upon visiting the public ip of my linode I saw the error msg 'No input file specified.

Went to Nginx configuration file in my forge and deleted the word 'public' so now its

root /home/forge/default;

Restarted nginx server within forge and deployed again and now it can be accessed.

Upvotes: 0

Simon Ouellet

Reputation: 99

Same problem.
Cause : My root wasn't specified in open_basedir.
Fix : Adding my site root directory in :

/etc/php5/fpm/pool.d/mysite.conf

by adding this directive :

php_value[open_basedir] = /my/root/site/dir:/other/directory/allowed

Upvotes: 4

ekene

Reputation: 301

Check the error log file. On windows, I checked and saw that the document root I specified in nginx.conf was using the back slash path separator "C:\nginx..." instead of the forward shash "C:/nginx...". So I suggest you check the error log file when you get "No input file specified" on your site to get a clue.

Upvotes: 0

hljubic

Reputation: 139

It is possible that PHP-FPM service is not started or is listening on some other port than 9000.

Upvotes: 0

Vitalicus

Reputation: 1379

For localhost - I forgot to write in C:\Windows\System32\drivers\etc\hosts

127.0.0.1 localhost

Also removed proxy_pass http://127.0.0.1; from other server in ngnix.conf

Upvotes: 0

francisco javier ruiz utrilla

Reputation: 11

use in windows

fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;

wasn't putting -b

php-cgi.exe -b 127.0.0.1:9000

Upvotes: 0

Arun Panneerselvam

Reputation: 2335

Okay, I assume you using php7.2 (or higher) on Ubuntu 16 or higher

if none of this worked, you must know nginx-fastCGI uses different pid and .sock for different sites hosted on the same server.

To troubleshoot 'No input file specified' problem, you must tell the nginx yoursite.conf file which one of the sock file to use.

Uncomment the default fastcgi_pass unix:/var/run/php7.2-fpm.sock Make sure you have the following directives in place on the conf file,

location / {
    try_files $uri $uri/ /index.php$is_args$args;
}
location ~ \.php$ {
        try_files $uri /index.php =404;
        #fastcgi_pass unix:/var/run/php7.2-fpm.sock;
        fastcgi_pass unix:/var/php-nginx/158521651519246.sock/socket;
        fastcgi_index index.php;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        include fastcgi_params;
}

have a look at the list of sock and pid files using ls -la /var/php-nginx/(if you have recently added the file, it should be the last one on the list)

3.copy the filename of the .sock file (usually a 15 digit number) and paste it to your location ~ \.php directive

fastcgi_pass unix:/var/php-nginx/{15digitNumber}.sock/socket;

and restart nginx. Let me know if it worked.

Upvotes: 2

Jimbo

Reputation: 21

I tried all the options mentioned above, but found finally the solution. On my server the .php file was set to be readable by everyone, but it worked when I set the php-fpm to run under same user as nginx. I changed it in /etc/php/7.2/fpm/pool.d/www.conf and in the configuration file I set

user = nginx group = nginx

and then reloaded the php-fpm process Hope this helps

Upvotes: 2

Verter

Reputation: 331

This answers did not help me, my php adminer showed me "No input file specified" error anyway. But I knew I changed php-version before. So, I found the reason: it is not nginx, it is php.ini doc_root parameter! I found

doc_root =

in php.ini and changed it to

;doc_root =

After this patch my adminer work good.

Upvotes: 3

sffc

Reputation: 6414

My case: SELinux was enabled and denying php-fpm from executing my scripts.

Diagnosis: Temporarilly disable SELinux and see if the problem goes away.

$ sudo setenforce permissive
### see if PHP scripts work ###
$ sudo setenforce enforcing

Solution: Put the PHP directory in the httpd_sys_content_t context. You can use chcon or make the change persistent via semanage:

$ sudo semanage fcontext -a -t httpd_sys_content_t "/srv/myapp(/.*)?"
$ sudo restorecon -R -F /srv/myapp

You can use the context httpd_sys_rw_content_t where write permissions are needed.

Upvotes: 0

ᴍᴇʜᴏᴠ

Reputation: 5256

Same problem.

Reason old open_basedir settings copied with a rogue user.ini file in a backup

Solution delete it

Upvotes: 1

Rudra Pratap Sinha

Reputation: 169

I tried all the settings above but this fixed my problem. You have to define nginx to check if the php file actually exists in that location. I found try_files $uri = 404; solving that problem.

location ~ \.php$ {
        try_files  $uri =404;
        fastcgi_split_path_info ^(.+\.php)(/.+)$;
        fastcgi_pass unix:/var/run/php5-fpm.sock; 
        include fastcgi_params;
        fastcgi_index index.php;
}

Upvotes: 3

Fresco

Reputation: 299

I solved it by replacing

fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;

$document_root with C:\MyWebSite\www\

fastcgi_param SCRIPT_FILENAME C:\MyWebSite\www\$fastcgi_script_name;

Upvotes: 3

evergreen

Reputation: 8165

Resolving "No input file specified" error

If you are using nginx with php-cgi and have followed the standard procedure to set it up, you might often get the “No input file specified” error. This error basically occurs when the php-cgi daemon cannot find a .php file to execute using the SCRIPT_FILENAME parameter that was supplied to it. I’ll discuss about the common causes of the error and it’s solutions. Wrong path is sent to the php-cgi daemon

More often than not, a wrong path (SCRIPT_FILENAME) is sent to the fastCGI daemon. In many of the cases, this is due to a misconfiguration. Some of the setups I have seen are configured like this :

server {
    listen   [::]:80;
    server_name  example.com www.example.com;
    access_log  /var/www/logs/example.com.access.log;  

    location / {
        root   /var/www/example.com;
        index  index.html index.htm index.pl;
    }

    location /images {
        autoindex on;
    }

    location ~ \.php$ {
        fastcgi_pass   127.0.0.1:9000;
        fastcgi_index  index.php;
        fastcgi_param  SCRIPT_FILENAME  /var/www/example.com$fastcgi_script_name;
        include fastcgi_params;
    }
}

Now, there are many things wrong with this configuration. An obvious and glaring issue is the root directive in the location / block. When the root is defined inside the location block, it is available/defined for that block only. Here, the location /images block will not match for any request because it does not have any $document _root defined and we will have to redundantly define root again for it. Obviously, the root directive should be moved out of the location / block and defined in the server block. This way, the location blocks will inherit the value defined in the parental server block. Of course, if you want to define a different $document_root for a location, you can put a root directive in a location block.

Another issue is that the value of the fastCGI parameter SCRIPT_FILENAME is hard-coded. If we change the value of the root directive and move our files somewhere else in the directory chain, php-cgi will return a “No input file specified” error because will not be able to find the file in the hard-coded location which didn’t change when the $document_root was changed. So, we should set SCRIPT_FILENAME as below :

fastcgi_param  SCRIPT_FILENAME  $document_root$fastcgi_script_name;

We should keep in mind that the root directive should be in the server block or else, only the $fastcgi_script_name will get passed as the SCRIPT_FILENAME and we will get the “No input file specified” error.

source(Resolving "No input file specified" error)

Upvotes: 24

Sam Najian

Reputation: 376

Simply restarting my php-fpm solved the issue. As i understand it's mostly a php-fpm issue than nginx.

Upvotes: 12

FireGnome

Reputation: 130

I had the same Error and my Problem was, that I had my php-file in my encrypted home-directory. And I run my fpm with the www-data user and this user can't read the php-files even if the permissions on the file were right. The solutioin was that I run fpm with the user who owns the home-directory. This can be changed in folowing file:

/etc/php5/fpm/pool.d/www.conf

hope this will help you :)

Upvotes: 0

ang yao

Reputation: 451

You must add "include fastcgi.conf" in

location ~ \.$php{
  #......
  include fastcgi.conf;
}

Upvotes: 35

Poonam Bhatt

Reputation: 10302

server {
    server_name www.test.com test.com;
    access_log /sites/test/logs/access.log;
    error_log /sites/test/logs/error.log;
    root /sites/test;

 location ~ / {

index index.php
    include /etc/nginx/fastcgi_params;
    fastcgi_pass  127.0.0.1:9000;
    fastcgi_index index.php;
    fastcgi_param SCRIPT_FILENAME `$document_root/service/public$fastcgi_script_name`;
}

Upvotes: 1

Johnride

Reputation: 8736

This is likely because with the trailing slash, NGinx tries to find the default index file which is probably index.html without configuration. Without the trailing slash it tries to match the file testservice which he can't find. Either this and/or you don't have any default index file in the testservice folder.

Try adding this line to your server configuration :

index  index.php index.html index.htm; // Or in the correct priority order for you

Hope this helps!

Edit

My answer is not very clear, see this example to understand what I mean

listen 80;

    server_name glo4000.mydomain.com www.glo4000.mydomain.com;


    access_log  /var/log/nginx/glo-4000.access.log;
    error_log /var/log/nginx/glo-4000.error_log;

    location / {
        root   /home/ul/glo-4000/;
        index  index.php index.html index.htm;
    }

    location ~ \.php$ {

        include fastcgi_params;
        fastcgi_pass   unix:/tmp/php5-fpm.sock;
        fastcgi_index  index.php;
        fastcgi_param  SCRIPT_FILENAME /home/ul/glo-4000/$fastcgi_script_name;
    }
}

Upvotes: 2

&quot;No input file specified&quot; with php Fast/CGI

Answers (20)

Related Questions

"No input file specified" with php Fast/CGI