Doh, I think I fixed it. All I did was replacing fastcgi_param SCRIPT_FILENAME /private$fastcgi_script_name; with fastcgi_param SCRIPT_FILENAME $fastcgi_script_name; and that did actually do the trick. PHP-FPM now works on both paths. I guess $fastcgi_script_name already contains the relative path "/private" (aka "/phpmyadmin" :-P). Now I get some odd PHP/PHPmyAdmin specby OliverK - Php-fpm Mailing List - English
brianmercer Wrote: ------------------------------------------------------- > OliverK Wrote: > -------------------------------------------------- > ----- > > Thanks for you answer, > > > > however, I'm quite sure it does not, since I'm > > running PHP-FPM chrooted ("chroot = > > /srv/www/domain.tld/"). Also, this wouldn't > > explainby OliverK - Php-fpm Mailing List - English
Thanks for you answer, however, I'm quite sure it does not, since I'm running PHP-FPM chrooted ("chroot = /srv/www/domain.tld/"). Also, this wouldn't explain why one of the folders (the one called "public" is working fine).by OliverK - Php-fpm Mailing List - English
Hello, I don't speak English natively, so I'll come straight to the point. On my server there are three two directories I would like nginx to serve files from: "/srv/www/domain.tld/public" and "/srv/www/domain.tld/private". As a matter of fact I can't just simply move "private" into "public". I would like PHP to be functional in both directories and thereby OliverK - Php-fpm Mailing List - English
![]() |
![]() |
![]() |
![]() |
|