关于FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream的一次解决过
来源:互联网 发布:mac 录音专业版 编辑:程序博客网 时间:2024/06/05 18:34
因为换了台电脑,不可避免的要重新折腾一次开发环境。
开发环境是LNMP,部署好站点后,访问站点的时候始终是“File Not Found”,于是就见了鬼了,历来环境都是这么弄的,配置的内容也是根据之前的配置copy的,路径都确认了没得问题的。所以,真的就见了鬼了。
一般有问题都要找哥找娘的,但是说法大都是说讲配置SCRIPT_FILENAME不对,应该怎样怎样改,这里就是最不解的地方,因为根据他们说的,我的配置是对的。所以继续折腾。得出了以下几点意见:
1) 软件安装应该是没得问题的,nginx和fpm通信应该是正常的,不然不会说“File Not Found”;
2) 配置是没有问题的,一个是之前的配置是这样的,二个是根据网上说的大多都是如此;
3) 经过确认配置的站点路径没得问题。
所以,明明就在眼前,一切正常,却访问不到,应该是权限的问题。查看了下跟目录的权限,“drwx------”,果然,明显有鬼。
仔细想了下,原来这个目录是我在图形界面直接copy的,copy的时候系统直接修改了权限,到账下面的文件无法被正常访问。为了确认这个问题,用相同的方式又copy了几个文件,确实如此。直接修改目录对应的权限后,站点就可以正常访问了。
总结:FastCGI sent in stderr: "Primary script unknown"的问题总的来说是无法找到对应的文件,除了路径外,还应该考虑下权限。
1 0
- 关于FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream的一次解决过
- FastCGI sent in stderr: "Primary script unknown" while reading response head
- "Primary script unknown" while reading response header from upstream, client: 192.168.1.102, server:
- nginx:*21 FastCGI sent in stderr: "Primary script unknown"
- nginx 错误502 upstream sent too big header while reading response header from upstream
- upstream sent invalid header while reading response header from upstream 错误解决
- 69331 upstream sent too big header while reading response header from upstream
- nginx 错误502 upstream sent too big header while reading response header from upstream
- nginx 错误502 upstream sent too big header while reading response header from upstream
- 502错误. Nginx日志:upstream sent too big header while reading response header from upstream
- 修复Nginx报错:upstream sent too big header while reading response header from upstream
- 修复Nginx 502错误:upstream sent too big header while reading response header from upstream
- Nginx 错误502 upstream sent too big header while reading response header from upstream
- 修复Nginx报错:upstream sent too big header while reading response header from upstream
- php-fpm upstream sent too big header while reading response header from upstream
- 1345#0: *640 upstream sent too big header while reading response header from upstream
- 错误502 upstream sent too big header while reading response header from upstream
- upstream sent too big header while reading response header from upstream
- Distributed tensorflow实现原理
- SOA微服务案例-基于springmvc+mybaties+dubbo+mq+gradle
- OpenGLES的简单应用绘图,以及照相机画面变色变形渲染(三)
- 你在执行composer self-update更新命令的时候可能会遇到错误:
- unicode,ansi,utf-8编码的区别--浅谈计算机编码发展史
- 关于FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream的一次解决过
- Python scikit-learn机器学习工具包学习笔记:cross_validation模块
- 字符串A删除字符串B
- java集合框架
- Mybaties中的foreach
- Hiv:SQuirrel连接hive配置
- 在 Office 中单击超链接,找不到 Internet 服务器或代理服务器
- UITableView和UICollectionView的局部刷新
- 序号互换