I already replied to that
since June 21st, in your other ticket. Let me remind you:
you should ask your host exactly WHAT the block to directly access a .php file is because it'd seem that just "fastcgi_pass unix:/var/run/php/php7.0-fpm.sock" doesn't cut it. This is the part that's 100% host specific and I cannot possibly guess. Also that's the first thing I'd try.
I can tell you what I needed to use for the NginX setup I create on Windows from scratch, just to reply to your ticket #27980,
as I already told you on June 27th:
I wanted to be super extra sure so I set up NginX from scratch on my Windows 10 computer as well using the barebones official binaries. I still cannot reproduce this issue. I can tell you, however, that I noticed something interesting there. I had to change the fastcgi_pass code block setting to have both the fastcgi_pass localhost:9123 and the include fastcgi_params lines. Otherwise I'd get a 403 Forbidden. So, if you cannot find something that causes a redirection maybe try modifying the fastcgi_pass code block as well.
To cut a long story short, my FastCGI pass block reads:
fastcgi_pass 127.0.0.1:9170;
fastcgi_index index.php;
include fastcgi_params;
Remember that this was on Windows, hence the need to use a TCP/IP port instead of a UNIX pipe. You can use a UNIX pipe like you do without a problem. The differenciating factor for me was the need to include the fastcgi_params file. The fastcgi_params file is the one shipped with NginX and it's described in
NginX's documentation page "PHP FastCGI Example". As we tell you in
our documentation this is the only FastCGI setup we can test with and support. Anything else will require you to manually edit the generated NginX configuration file.
Do note that adding a file into the list for directly accessible .php files simply creates a location rule with an exact match to the file path you specified, the contents of with are the FastCGI pass block you have configured in NginX Conf Maker followed by a single break; directive to stop the processing of any further rules. In short, it doesn't have any logic that we have built in. It simply uses your defined path with your defined FastCGI block.
As I've been telling you for well over a week, your FastCGI block is wrong. Can you
please stop asking us -who have NOT set up your server- and ask your host exactly what you should put in there? I can only tell you what you need to put in the servers I built and/or manage myself - including the MAMP Pro installations I told you about in the other ticket.
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
