nginx: [emerg] host not found in upstream "baafile.yiche.com" in /usr/local/etc/nginx/nginx.conf:67

场景:nginx之前配置好的,直接启动即可,过了一段时间,突然启动报错。

nginx: [emerg] host not found in upstream "baafile.yiche.com" in /usr/local/etc/nginx/nginx.conf:67

应该是 baafile.yiche.com  这个域名 之前可以访问,现在不能访问了。把此处的注释重启即可。

原文地址:https://www.cnblogs.com/kpengfang/p/12698756.html

时间: 2024-08-02 00:12:15

nginx: [emerg] host not found in upstream "baafile.yiche.com" in /usr/local/etc/nginx/nginx.conf:67的相关文章

nginx: [error] invalid PID number “” in “/usr/local/var/run/nginx/nginx.pid”

在Mac上用brew安装Nginx,然后修改Nginx配置文件,再重启时报出如下错误: nginx: [error] invalid PID number "" in "/usr/local/var/run/nginx/nginx.pid" 解决办法: $ sudo nginx -c /usr/local/etc/nginx/nginx.conf $ sudo nginx -s reload

nginx: [error] open() "/usr/local/var/run/nginx.pid" failed (2: No such file or directory)

nginx: [error] open() "/usr/local/var/run/nginx.pid" failed (2: No such file or directory) 2017年09月14日 09:15:45 阅读数:7742 启动Nginx出现这个错误 nginx: [error] open() "/usr/local/var/run/nginx.pid" failed (2: No such file or directory) 1  解决方法:找

Nginx 提示host not found in upstream 错误解决方法

Nginx DNS resolver配置实例,本文讲解在proxy_pass 和 upstream server 通信的时候需要手动指定 resolver,本文就给出了配置实例. nginx 通过 proxy_pass 和 upstream server 通信的时候需要手动指定 resolver.某些时候 DNS 解析失败就会出现这个错误: domain.com could not be resolved. 可以指定多个 DNS 并重置域名 TTL 延长 nginx 解析缓存来保障解析成功率:

nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) 错误解决

今天在做LNMP的时候,启动nginx服务,无法开启,导致网页打不开.把服务从起一下发现提示错误如下: Starting nginx: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)nginx: [emerg] bind() to 0.0.0.0:80 fai

nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)

nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) 报错信息 nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol) 1 2 定位方法 1.先使用p

nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)解决

nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) 报错信息 nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)定位方法 1.先使用ps -e |

Nginx学习日记第五篇 -- upstream及fastcgi

一.Nginx upstream Ngx_http_upstream_module模块可实现七层负载均衡,定义的服务器组可被proxy_pass.fastcgi_pass.uwsgi_pass.scgi_pass和memcached_pass所引用. 1.实验场景 Nginx upstream IP:192.168.0.110 apache node1 IP:192.168.0.40 apache node2 IP:192.168.0.30  2.Nginx upstream配置(结合proxy

Nginx自学手册(一) upstream及fastcgi

(一)nginx upstream实现负载均衡 Ngx_http_upstream_module模块可实现七层负载均衡,定义的服务器组可被proxy_pass.fastcgi_pass.uwsgi_pass.scgi_pass和memcached_pass所引用,具体可以参考官方文档: http://nginx.org/en/docs/http/ngx_http_upstream_module.html 1,当前的环境: Nginx upstream IP:192.168.180.2 node1

Windows下Nginx Virtual Host多站点配置详解

Windows下Nginx Virtual Host多站点配置详解 此教程适用于Windows系统已经配置好Nginx+Php+Mysql环境的同学. 如果您还未搭建WNMP环境,请查看 windows7配置Nginx+php+mysql教程. 先说明一下配置多站点的目的:在生产环境中,如果将系统所有代码文件都放在公开目录中,则很容易被查看到系统源码,这样是很不安全的,所以需要只公开index.php的入口文件目录.而同一个服务器中,可能运行多个系统,这样就必须公开多个入口文件目录,以便用不同的