Php nginx-无法打开主脚本
我收到错误消息:Php nginx-无法打开主脚本,php,wordpress,nginx,Php,Wordpress,Nginx,我收到错误消息: FastCGI在stderr中发送:“无法打开主脚本:/home/mesi/web/wordpress/index.php(没有这样的文件或目录)”,同时从上游读取响应头,客户端:xxx.xxx.xxx.xxx,服务器:www.domain.com,请求:“GET/HTTP/1.1”,上游:fastcgi://unix:/var/run/php5-fpm.sock:,主机:“www.domain.com 以下是我的配置文件: /etc/php5/fpm/php.ini cgi.
FastCGI在stderr中发送:“无法打开主脚本:/home/mesi/web/wordpress/index.php(没有这样的文件或目录)”,同时从上游读取响应头,客户端:xxx.xxx.xxx.xxx,服务器:www.domain.com,请求:“GET/HTTP/1.1”,上游:fastcgi://unix:/var/run/php5-fpm.sock:,主机:“www.domain.com
以下是我的配置文件:
/etc/php5/fpm/php.ini
cgi.fix_pathinfo=0
doc_root =
user_dir =
....
/etc/php5/fpm/php fpm.conf
[global]
pid = /var/run/php5-fpm.pid
error_log = /var/log/php5-fpm.log
include=/etc/php5/fpm/pool.d/*.conf
[www]
user = www-data
group = www-data
listen = /var/run/php5-fpm.sock
listen.owner = www-data
listen.group = www-data
listen.mode = 0666
pm = dynamic
pm.max_children = 5
pm.start_servers = 2
pm.min_spare_servers = 1
pm.max_spare_servers = 3
chdir = /
security.limit_extensions = .php .php3 .php4 .php5
php_flag[display_errors] = on
php_admin_value[error_log] = /var/log/fpm-php.www.log
php_admin_flag[log_errors] = on
user nginx;
worker_processes 1;
error_log /var/log/nginx/error.log warn;
pid /var/run/nginx.pid;
events {
worker_connections 1024;
}
http {
include /etc/nginx/mime.types;
server_tokens off;
default_type application/octet-stream;
log_format main '$remote_addr - $remote_user [$time_local] "$request" '
'$status $body_bytes_sent "$http_referer" '
'"$http_user_agent" "$http_x_forwarded_for"';
access_log /var/log/nginx/access.log main;
sendfile on;
#tcp_nopush on;
keepalive_timeout 65;
#gzip on;
include /etc/nginx/sites-enabled/*;
}
/etc/php5/fpm/pool.d/www.conf
[global]
pid = /var/run/php5-fpm.pid
error_log = /var/log/php5-fpm.log
include=/etc/php5/fpm/pool.d/*.conf
[www]
user = www-data
group = www-data
listen = /var/run/php5-fpm.sock
listen.owner = www-data
listen.group = www-data
listen.mode = 0666
pm = dynamic
pm.max_children = 5
pm.start_servers = 2
pm.min_spare_servers = 1
pm.max_spare_servers = 3
chdir = /
security.limit_extensions = .php .php3 .php4 .php5
php_flag[display_errors] = on
php_admin_value[error_log] = /var/log/fpm-php.www.log
php_admin_flag[log_errors] = on
user nginx;
worker_processes 1;
error_log /var/log/nginx/error.log warn;
pid /var/run/nginx.pid;
events {
worker_connections 1024;
}
http {
include /etc/nginx/mime.types;
server_tokens off;
default_type application/octet-stream;
log_format main '$remote_addr - $remote_user [$time_local] "$request" '
'$status $body_bytes_sent "$http_referer" '
'"$http_user_agent" "$http_x_forwarded_for"';
access_log /var/log/nginx/access.log main;
sendfile on;
#tcp_nopush on;
keepalive_timeout 65;
#gzip on;
include /etc/nginx/sites-enabled/*;
}
/etc/nginx/nginx.conf
[global]
pid = /var/run/php5-fpm.pid
error_log = /var/log/php5-fpm.log
include=/etc/php5/fpm/pool.d/*.conf
[www]
user = www-data
group = www-data
listen = /var/run/php5-fpm.sock
listen.owner = www-data
listen.group = www-data
listen.mode = 0666
pm = dynamic
pm.max_children = 5
pm.start_servers = 2
pm.min_spare_servers = 1
pm.max_spare_servers = 3
chdir = /
security.limit_extensions = .php .php3 .php4 .php5
php_flag[display_errors] = on
php_admin_value[error_log] = /var/log/fpm-php.www.log
php_admin_flag[log_errors] = on
user nginx;
worker_processes 1;
error_log /var/log/nginx/error.log warn;
pid /var/run/nginx.pid;
events {
worker_connections 1024;
}
http {
include /etc/nginx/mime.types;
server_tokens off;
default_type application/octet-stream;
log_format main '$remote_addr - $remote_user [$time_local] "$request" '
'$status $body_bytes_sent "$http_referer" '
'"$http_user_agent" "$http_x_forwarded_for"';
access_log /var/log/nginx/access.log main;
sendfile on;
#tcp_nopush on;
keepalive_timeout 65;
#gzip on;
include /etc/nginx/sites-enabled/*;
}
/etc/nginx/sites enabled/wordpress
server {
listen 80;
server_name www.domain.com;
root /home/messi/web/wordpress;
error_log /var/log/nginx/err.wordpress.log;
index index.php;
location / {
try_files $uri $uri/ /index.php?$args;
}
location = /favicon.ico {
log_not_found off;
access_log off;
}
location = /robots.txt {
allow all;
log_not_found off;
access_log off;
}
location ~ /\. {
deny all;
}
location ~* /(?:uploads|files)/.*\.php$ {
deny all;
}
location ~ \.php$ {
fastcgi_split_path_info ^(.+\.php)(/.+)$;
fastcgi_pass unix:/var/run/php5-fpm.sock;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
include /etc/nginx/fastcgi_params;
}
}
设置用户权限:
#adduser www-data messi
#chown -R www-data:www-data /home/messi/web
#chmod -R 664 /home/messi/web/wordpress
我如何解决这个问题?
谢谢这可能是权限问题
namei-om/path/to/file
默认情况下,SELinux将在CentOS/RHEL 7+上导致此错误:( 要测试SELinux是否是你痛苦的根源,请执行以下操作
setenforce 0
…然后看看是否一切正常。如果这解决了它,你可以关闭SELinux(弱,你比这更好),或者用
setenforce 1
…然后正确解决问题
如果你这样做
tail -f /var/log/audit/audit.log
…您将看到SELinux问题。在我的例子中,它拒绝PHP-FPM访问web文件。您可以运行以下指令来修复它:
setsebool -P httpd_can_network_connect_db 1
setsebool -P httpd_can_network_connect 1
起初,这实际上并没有为我修复它,但后来恢复SELinux上下文就解决了
restorecon -R -v /var/www
希望能有所帮助。我的案例中也有SELinux。我在这里阅读了一些文档:
最后得到了命令:
chcon -R -v --type=httpd_sys_content_t html/
..这将文件的上下文更改为httpd类型,这就是我的web服务器(Nginx)的运行方式
您可以使用以下内容查找web服务器运行的上下文:
ps axZ | grep nginx
…就我而言,这给了我:
system_u:system_r:**httpd_t**:s0 6246 ? Ss 0:00 nginx: master process /usr/sbin/nginx -c /etc/nginx/nginx.conf
system_u:system_r:**httpd_t**:s0 6249 ? S 0:00 nginx: worker process
看到运行服务的上下文是httpd\t,我将网站根文件夹的上下文更改为该上下文(递归)
SELinux的要点是只允许服务和进程访问与它们相同类型的文件。由于web服务器作为httpd_t运行,因此将站点中文件/文件夹的上下文设置为相同是有意义的
顺便说一句,我是新手……但这似乎是对我来说最好的方法。它保持了SELinux的启用,没有降低它的安全性,并且将文件的上下文与流程/服务匹配起来。这个答案在低质量的帖子评论队列中,因为它只是没有解释的代码。请通过解释来改进你的答案ning您的代码是什么以及它如何回答问题。请阅读。对于我来说,从Ubuntu 12.04切换到14.04时出现了问题。在12.04中,默认情况下
/home
中的用户文件夹将具有755
(drwxr-xr-x
)权限。而在14.04中,它们将具有700
权限(drwx------
)由于web服务器在www-data
user下运行,因此www-data
用户将无法访问www-data
下的wordpress目录,因为user1404
具有700
权限。如果要在CentOS 7下禁用它,请编辑/etc/selinux/config
set“SELINUX=已禁用"
然后重新启动。经过一个小时的努力,这对我很有帮助!谢谢!在CentOS 7上工作得很好。同样的情况也发生在CentOS 6上,restorecon命令也起作用。我还可以验证restorecon是否也对我起作用,没有任何setsebool命令。PS谢谢,我花了几个小时试图找出403错误的来源导致了几篇关于你为什么想要或不想要SELinux的文章