New answers tagged

0

Kudos to @w3d for pointing this out. Internally proxying the request is going to skip the .htaccess file. Of course it does. I have updated my VHost file to the below, following the answer from this thread: Apache 2.4 + PHP-FPM + ProxyPassMatch


0

Check to make sure your php config doesn't have any syntax errors or permissions problems - I'm not familiar with Centos7 but in Ubuntu 14.04 it's sudo /usr/sbin/php-fpm7.0 --fpm-config /etc/php/7.0/fpm/php-fpm.conf that will tell you if there are any errors. When I've ran into this problem in the past, it was because the directory PHP-FPM was trying to ...


0

If the user and folder permissions are fine then check if SElinux is disabled or not.


0

I solve this problem by changing user and group tho the current user:group in php-fpm.d/www.conf By default the user and group is 'nginx', change this.... Hope this helps


2

Without testing this myself, I can't be sure, but it seems like this is just a case of a bad regex line for directing requests to your php-fpm engine. location ~ [^/]\.php(/|$) { Will only match location requests which end with ".php/" (which is uncommon), or explicitly end with ".php". I'm assuming you used the guide here, which is fine (though I've ...


2

On systemd systems, you may have to configure this via systemd rather than system V init scripts The below steps are tested and working on Ubuntu 16.04 LTS. And this is your culprit for redirected init scripts: /lib/lsb/init-functions.d/40-systemd 1. Edit your php-fpm pool configuration e.g. /etc/php/7.0/fpm/pool.d/www.conf and configure root as the ...


3

I finally found a solution. It turned out Ubuntu was using systemd to start and restart PHP-FPM and was therefor ignoring the init.d files. If you experience issues with adjustments to init.d files being ignored and you're on Ubuntu 15.04 or later, big chance that service has a systemd service file as well. So the fix for my problem: My system has a file ...


0

after almost one year I've fixed the error some months ago. The problem was that I've enabled the gzip compression in nginx and also in my CMS Joomla. I had only on a few pages with a failure (Encoding Error) in the backend. Now I've disabled the gzip compression on Joomla and everything works right. No more errors every few seconds in my log. I hope this ...


0

The default PHP FPM listens on a Unix socket. You have it commented out: #fastcgi_pass unix:/var/run/php5-fpm.sock; If you want to use the socket, uncomment that line in your NGINX configuration to point to the proper socket. If you want to connect to PHP via IP as you have currently configured, you will need to edit the php fpm pool settings. (default ...


0

This part of vhosts configuration is relevant when you access that website with https, you should have another instance in vhosts , can you look again and update your post?


1

You have a weird configuration. http2 can only work over https, in practice. You should define a server that forwards to https, not one server that serves both. You should define your servers in one per file You should read my Nginx tutorial, but here are key parts. Add this to your nginx.conf. I changed what most people use, sites-enabled to enabled-sites,...


0

A more valid explanation to the ptrace(PEEKDATA) failed seems to be this - ... the worker is free to go when the master is determining slow execution. When stopping to be traced, it may have completed that execution and is in any stage serving another request, so the tracer gets the chance of failure or worse, dumping out the stack of an ...


0

I see there is no /run/php/php7.0-fpm.pid file. This file is created when php7.0-fpm starts. So I solved this issue by adding to Dockerfile: RUN service php7.0-fpm start Of course after php-fpm installation :)


0

On CentOS 7 sudo systemctl enable php-fpm // Just incase is disabled. Also ensures it starts automatically with the server sudo systemctl start php-fpm // Start the service sudo systemctl stop php-fpm // Stop the service sudo systemctl status php-fpm // View status


0

I have solved the problem by reading the Configuring Virtual Hosts document and creating 3 XML-files: $JETTY_BASE/webapps/site1.xml $JETTY_BASE/webapps/site2.xml $JETTY_BASE/webapps/site3.xml With the following content at the top of each file: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD ...


0

The 403 is often because of a missing ScriptAlias line. eg, if the Location is "/" and root for the server is /var/my-www/, put it immediately before the directive: ScriptAlias / /var/my-www/ <Location /> ... ...


0

PHP7/Debian people (similar/same reason): The reason for that, is, how mention above, the missing XML extension. Must of us will use dotdeb, and the have removed xml from being build-in to being a separate package: source: https://www.dotdeb.org/2016/06/24/php-7-0-8-for-jessie/ Please also note that bcmatch, dba, mbstring, soap, xml and zip now ...


0

In the end, I just defined some [HOST=] sections in my /etc/php5/fpm/php.ini configuration. http://php.net/manual/en/ini.sections.php This felt more secure than using mod_env or .user.ini.


0

I think you should install openssl-devel(yum install openssl-devel). Then you could recompile PHP with latest OpenSSL.



Top 50 recent answers are included