如果用nginx部署PHP网站，报错upstream sent unsupported FastCGI protocol version: 72 while reading response header from upstream可能的原因是php-fpm的配置文件中的，user和group没有配置为 nginx
upstream sent unsupported FastCGI protocol version: 72 while reading response header from upstream
免责声明！
本站转载的文章为个人学习借鉴使用，本站对版权不负任何法律责任。如果侵犯了您的隐私权益，请联系本站邮箱yoyou2525@163.com删除。
猜您在找
【nginx】 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream
FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream,
nginx log 错误502 upstream sent too big header while reading response header from upstream
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+php部署FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream错误
Linux 配置lnmp环境 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 127.0.0.1, server: localhost 可能的问题
[error] 1507#0: *22 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 10.0.0.1, server: www.wordpress.com, request: "GET /info.p
解决flask的502错误：upstream prematurely closed connection while reading response header from upstream
upstream timed out (110: Connection timed out) while reading response header from upstream