permission denied php fpm
I am trying configure a PHP server using nginx in Windows 10, but i’m having some problems on the way.
What i’m trying to do?
If i access localhost i see phpinfo page (OK)
If i access localhost/phpmyadmin i see Access denied. (FAIL)
If i access localhost/laravel/public i see the welcome page of laravel framework.
Foder structure
D:/Server/apps/phpmyadmin (phpmyadmin app)
D:/Server/bin/nginx
D:/Server/bin/php
D:/Server/conf/nginx/nginx.conf
D:/Server/conf/php/php.ini
D:/Server/logs/nginx
D:/Server/logs/php
D:/Server/www/index.php (phpinfo page)
D:/Server/www/laravel (laravel project)
What i’ve tried? I add phpmyadmin.app do windows hosts file and add another server block to nginx.conf and works, but i dont want to do it this way.
error.log
host.access.log
nginx-start.bat
nginx.conf
From Nginx HTTP Server book:
alias Context: location. Variables are accepted. alias is a directive that you place in a location block only. It assigns a different path for Nginx to retrieve documents for a specific request. As an example, consider the following configuration: http < server < server_name localhost; root /var/www/website.com/html; location /admin/ < alias /var/www/locked/; >> > When a request for http://localhost/ is received, files are served from the /var/www/website.com/html/ folder. However, if Nginx receives a request for http://localhost/admin/, the path used to retrieve the files is var/www/locked/. Moreover, the value of the document root directive (root) is not altered. This procedure is invisible in the eyes of dynamic scripts. Syntax: Directory (do not forget the trailing /) or file path
Update
@Richard Smith suggested change alias to root and C:/Server/apps/phpmyadmin/ to C:/Server/apps and add the ^
PHP FPM gives permission denied?
I read several entries on why PHP-FPM might give me permission denied but I can not solve it.
The error logs read like:
Im a little but lost:
my /etc/nginx/conf.d/ is empty my /mnt/web/nginx/conf.d contain A LOT of website configurations which all include «wordpress.conf»:
UPDATE: found the problem, put it in the answer
6 Answers 6
I had set the /var/lib/nginx/tmp to ec2-user/ec2-user (i even +777 everything to check)
. after also chown/chgrp the parent nginx folder : no more errors.
Took me some hours.
This generally happens. When the user setting in nginx.conf is changed from
to something else. In this case,
The chmod command is not necessary per Chris’s comment, and could open up a security hole.
Check the current user and group ownership on /var/lib/nginx.
This tells you that a possibly non-existant user and group named nginx owns this folder. This prevents file uploading.
Change the folder ownership to the user defined in nginx.conf in this case ec2-user (sudo may not be required).
Verify that it actually changed.
The permission denied error should now go away. Check the error.log (based on nginx.conf error_log location).
If that doesn’t work you might need to reload nginx and php-fpm.
None of the other solutions worked for me, but I found this to work:
I have got the similar problem with file upload. nginx 500 error 2015/07/05 03:50:36 [crit] 3656#0: *7 open() «/var/lib/nginx/tmp/client_body/0000000007» failed (13: Permission denied), client: 10.0.2.2, server: www.test.com, request: «POST /api/v1/users HTTP/1.1», host: «test»
Just solved my issue with permissions. The easiest way and most simple was to not run php-fpm or nginx as sudo (super user). What you would have to do is:
By not using root i didn’t have to change php-fpm user or group or any listening user or groups. Make sure you also comment out nginx.conf ‘user’ as it will be the current users name.
Instead of editing permissions on /var/lib/nginx/whatever, wouldn’t it make more sense to just tell nginx to use a different path like /tmp/nginx? This fixed the problem for me:
php-fpm.sock failed (13 permission denied) – Fix it now
Are you seeing php-fpm.sock failed (13 permission denied) error in web server logs? We’ll help you fix it.
Often bad permissions or unavailability of the PHP-FPM handler results in these website errors.
Thus web server will not be able to communicate with the PHP FastCGI Process Manager or FPM.
At Bobcares, we resolve PHP-FPM errors as part of our Server Management Services.
Today, we’ll see how we resolve php-fpm.sock failed error and make websites working.
Where do we see php-fpm.sock failed (13 permission denied) error?
PHP FastCGI Process Manager (PHP-FPM) is a popular way of handling PHP pages. It allows a website to handle high loads. And, it works very well with high traffic websites too.
Usually, the php-fpm socket failure errors show up in the web server error logs as:
On the website page, this would result in errors like 502 Bad Gateway or 503 Service Temporarily Unavailable.
Top causes for php-fpm.sock failed (13 permission denied) error
In general, PHP-FPM maintains a set of pools. These pools are workers available to respond to PHP requests. They will only execute PHP scripts as per the web server’s request. Finally, it sends the result back to the webserver. Thus, enabling PHP-FPM to service content will be quicker than usual methods.
However, when the webserver cannot communicate with the FPM handler, it eventually results in website errors.
Now, let’s see the top reasons for the PHP FPM socket failure.
Permission errors
One of the common reasons for the PHP FPM failure will be related permissions. When the permissions are wrong, the Apache or Nginx server will not be able to connect to the FPM daemon.
Recently, when a customer updated the PHP packages on his server, it reset the permissions of the files. The php-fpm socket was created with wrong ownership. Thus, the Nginx was not able to connect to the php-fpm socket.
The correct socket file permissions should be 0660
Often, extended access control lists also restrict access to the directory in which the socket lies. Thus, it makes php-fpm inaccessible for the web user.
Failed PHP-FPM service
Similarly, a failure in the PHP FPM service also can cause php-fpm.sock failed (13 permission denied) error.
In a cPanel server, a failed status of the cpanel_php_fpm status shows up as:
This can be related to an incorrect php-fpm configuration or wrong server settings. Likewise, insufficient server memory can also prevent the start-up of php-fpm.
How we fix php-fpm.sock failed (13 permission denied) error
Moving on, let’s see how our Support Engineers fix the PHP FPM socket errors and make website working.
PHP-FPM status
We begin by checking the status of the FPM status. On a cPanel server, we check it by using the command:
If it is not running, we simply restart it.
Next, we check the error logs at /usr/local/cpanel/logs/php-fpm/error.log
It will show up any type of configuration errors. We correct these errors and make fpm running again. Here, we also check the memory usage of the server. Then add more memory in case of any resource constraints.
Correcting permissions of the socket
To fix the permissions of the socket file on an Nginx server, we did the following steps.
Edited the /etc/php-fpm.d/www.conf file and corrected these variables:
Here, the webserver was running under the user nginx. So we set the php-fpm user as nginx itself. Then, we saved the file and restarted PHP FPM
This corrected the permissions on the socket file.
Finally, the website started working again.
[Need help to fix PHP FPM errors? We are available 24×7.]
Conclusion
In short, php-fpm.sock failed (13 permission denied) error happens due to incorrect PHP FPM configuration or service failure. Today, we saw how our Support Engineers fix the socket permissions and make the websites working.
Related posts:
PREVENT YOUR SERVER FROM CRASHING!
Never again lose customers to poor server speed! Let us help you.
Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.
OpenSUSE php-fpm.conf permission denied
I cannot launch php-fpm on OpenSUSE. When I run systemctl restart php-fpm.service I receive the following error, after copying etc/php8/fpm/php-fpm.conf.default to etc/php8/fpm/php-fpm.conf
2 Answers 2
I had to switch to php7-fpm to make it works. It seems that php-fpm does not work properly on OpenSUSE Tumbleweed.
No problem with apache mod php.
I had some of the issues as can be found in your post.
My setup:
php8 with nginx (fast-cgi NOT USING SOCK) works fine on my laptop
hardware: HP mobile workstation Compaq 8510w
Operating System: openSUSE Tumbleweed 20210
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
Kernel Version: 5.13.8-1-default (64-bit)
Graphics Platform: X11
Processors: 2 × Intel® Core™2 Duo CPU T9300 @ 2.50GHz
Memory: 3.8 GiB of RA
Graphics Processor: AMD RV630
for peace of mind:
for convenience:
To use these aliases you type the aliasname, a blank and the path to the file like for example for editing a file als sudo with nano try:
or, to retrieve the status of php-fpm with just a few keystrokes:
I copied /etc/php8/php.ini to «php.ini.commented» and deleted all comments and non required options in the original I also copied /etc/php8/cli/php.ini to php.ini.commented and deleted all comments and non required options in the original I did the same with /etc/php8/fpm/php-fpm.d/www.conf
for avoiding conflicts:
Before any other software operation, make sure that your system is running without errors.
Use
Solve found errors first!
After verification you should execute a
with following commands
I have changed ownership and permissions of all contents, that will be accessed by php-fpm.
STEP BY STEP
Allowing access to anybody else is opening the doors for hackers. Keep in mind that you are using a browser to see your data, but other people may be able to browse them as well.
After having a running system it is easy to add further steps. To start up there is no need for using sites-enabled in nginx and you need to create just one pool in /etc/php8/fpm/php-fpm.d/www.conf
TROUBLESHOOTING FREQUENT ERRORS:
MySql-errors:
I presume here, that your mariadb/mysql has been setup correctly.
Missing or wrong permissions will cause «not found» errors.
Troubleshooting in mysql is documented very well and mysql has an interactive help function. Read the documentation and test access following steps of the mysql manuals. It would lead too far, to add a guide for that to this document.
php-fpm not starting:
failed to open configuration file ‘/etc/php8/fpm/php-fpm.conf’: Permission denied (13)
you will find more details about what and how.
Possibly there is an access-issue when php-fpm tries creating a logfile «access.public.log» in /var/log by following the line access.log = «access.$pool.log» (look in file www.conf).
This error can be caused/suppressed by settings in apparmor. Options are:
In case you made modifications the result can be found as below in:
or temporary comment the line
access.log = /var/log/$pool.access.log in your www.conf
To get started this file is not absolutely required and commenting it helped me to suppress the «php-fpm could not be started» error.
The most important and detailed logfile is
To debug, after every modification You should use
You will see that most errors are permission errors either because mysql can’t access your database or php-fpm can’t use your php/html-files!
here my /etc/nginx/nginx.conf:
filecontents of /etc/php8/fpm/php-fpm.d/www.conf
With this configuration I run several mysql-databases and content management as well as phpmyadmin. The picture below is a screenshot of my Content Management System using a mysql database and self-designed forms in php-format. In the location definitions there are no further instructions required, neither for loading stylesheets nor for pictures/movies.
A check with Google’s developer tools in Chrome proofs, that all references and links to stylesheets, json-files and further directories have been found and that there are no errors.
In my little network here, I am using a 24/7 running Raspberry Pi 3 B+ with 64 bit OS as server, that stores data on two USB drives.
The configuration for accessing local files on this server is nearly the same as the configuration on my laptop.
There are just two little differences:
nginx error connect to php5-fpm.sock failed (13: Permission denied)
I update nginx to 1.4.7 and php to 5.5.12, After that I got the 502 error. Before I update everything works fine.
25 Answers 25
I had a similar error after php update. PHP fixed a security bug where o had rw permission to the socket file.
Uncomment all permission lines, like:
Note: if your webserver runs as user other than www-data, you will need to update the www.conf file accordingly
All the fixes currently mentioned here basically enable the security hole all over again.
What I ended up doing is adding the following lines to my PHP-FPM configuration file.
Make sure that www-data is actually the user the nginx worker is running as. For debian it’s www-data by default.
@Xander’s solution works, but does not persist after a reboot.
Sample from www.conf:
Edit: Per @Chris Burgess, I’ve changed this to the more secure method.
/var/run Only holds information about the running system since last boot, e.g., currently logged-in users and running daemons. (http://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard#Directory_structure).
Side note:
If you have tried everything in this post but are not having success getting PHP to work, this is what fixed it for my case:
Make sure you have these lines uncommented in /etc/php5/fpm/pool.d/www.conf:
Make sure /etc/nginx/fastcgi_params looks like this:
These two lines were missing from my /etc/nginx/fastcgi_params, make sure they are there!
Then, restart php5-fpm and nginx. Should do the trick.
In fact, «listen.mode» should be: «0660» and not «0666» as Other Writable or Other Readable is never a good choice here.
So try to find out as which user/group your webserver runs. I use CentOs and it runs as user «nginx» So add to your php-fpm.conf:
finally restart php-fpm
Check which user runs nginx. As of Ubuntu 12.04 nginx runs by nginx user which is not a member of www-data group.
and restarting nginx and php5-fpm daemons solves the problem.
Alternative to broadening permissions in your php config, you could change the user specified in your nginx config.
On the first line of your nginx.conf excerpt above, the user and group are specified as www and www, respectively.
Meanwhile, your php config probably specifies a user and group of www-data:
You might change the line in your nginx.conf, to any of the following, then:
Consideration must also be given to your individual FPM pools, if any.
I couldn’t figure out why none of these answers was working for me today. This had been a set-and-forget scenario for me, where I had forgotten that listen.user and listen.group were duplicated on a per-pool basis.
If you used pools for different user accounts like I did, where each user account owns their FPM processes and sockets, setting only the default listen.owner and listen.group configuration options to ‘nginx’ will simply not work. And obviously, letting ‘nginx’ own them all is not acceptable either.
For each pool, make sure that
Otherwise, you can leave the pool’s ownership and such alone.
I just got this error again today as I updated my machine (with updates for PHP) running Ubuntu 14.04. The distribution config file /etc/php5/fpm/pool.d/www.conf is fine and doesn’t require any changes currently.
I found the following errors:
The strange thing was that I have 2 sites running that utilize PHP-FPM on this machine one was running fine and the other (a Tiny Tiny RSS installation) gave me a 502, where both have been running fine before.
Both configuration files now contain the following block and are running fine again:
Update
It should be noted that Ubuntu ships two fastcgi related parameter files and also a configuration snippet which is available since Vivid and also in the PPA version. The solution was updated accordingly.
Diff of the fastcgi parameter files:
Configuration snippet in /etc/nginx/snippets/fastcgi-php.conf
The following simple fix worked for me, bypassing possible permissions issues with the socket.
In your nginx config, set fastcgi_pass to:
This must match the listen = parameter in /etc/php5/fpm/pool.d/www.conf, so also set this to:
Then restart php5-fpm and nginx
The problem in my case was that the Nginx web server was running as user nginx and the pool was running as user www-data.
I solved the issue by changing the user Nginx is running at in the /etc/nginx/nginx.conf file (could be different on your system, mine is Ubuntu 16.04.1)
then restart Nginx: service nginx restart
I had the similar error.
All recommendations didn’t help.
The only replacement www-data with nginx has helped:
I have fixed same issue on Amazon Linux AMI 2016.09 (Centos 7) by taking following steps.
Open your www.conf files (Example : sudo nano /etc/php-fpm.d/www.conf) Lastly, find the lines that set the listen.owner and listen.group and change their values from «nobody» to «nginx»:
Lastly, find the lines that set the user and group and change their values from «apache» to «nginx»:
Restart php-fpm (sudo service php-fpm restart)
The most important thing here is wich user is using nginx then do you need specify it as well
in your case the user and group is «www» so just replace it.
Just to add, on CentOS (and probably Red Hat and Fedora) the file to change the permissions to is at:
If you have different pool per user make sure user and group are set correctly in configuration file. You can find nginx user in /etc/nginx/nginx.conf file. nginx group is same as nginx user.
Also check SELINUX (/etc/selinux):
In my case php-fpm wasn’t running at all, so I just had to start the service 😂
Just see /etc/php5/php-fpm.conf pid = /var/run/php5-fpm.pid IS PID file
In file /etc/php5/fpm/pool.d/www.conf
listen = /var/run/php5-fpm.sock IS SOCKET file
After upgrading from Ubuntu 14.04 lts to Ubuntu 16.04 lts I found a yet another reason for this error that I haven’t seen before.
During the upgrading process I had somehow lost my php5-fpm executable altogether. All the config files were intact and it took me a while to realize that service php5-fpm start didn’t really start a process, as it did not show any errors.
In order to solve this problem I upgraded php from version 5.5 to 7.0. apt-get install php-fpm did the trick as a side effect. After that and installing other necessary packages everything was back to normal.
This upgrading solution may have problems of its own, however. Since php has evolved quite a bit, it’s possible that the software will break in unimaginable ways. So, even though I did go down that path, you may want to keep the version you’re fond of just for a while longer.
Luckily, there seems to be a neat way for that, as described on The Customize Windows site:
Neater solution as it might be, I didn’t try that. I expect the next couple of days will tell me whether I should have.