On 2016-11-14 11:13 AM, E H wrote: > Citando Thomas Ward : >> Thanks to Simon for looking at this first. >> >> Please read >> https://www.nginx.com/resources/wiki/start/topics/tutorials/config_pitfalls/ >> and the section on "Using a hostname to resolve addresses" - this is a >> pitfall because of errors like these, and is why NGINX and myself >> suggest using IP addresses and not host names for upstream definitions. > > As I said, it is a "proxy" directive. > > The incriminating line is > proxy_pass http://api.football-data.org/v1/; > > According to the nginx documentation: > http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_pass > it should be a URL and there is no mention of it needing an IP (the > first example even uses "http://localhost..."; rather than 127.0.0.1!
localhost is a special case as it's almost always "resolvable" from /etc/hosts. In your case, nginx was unable to resolve api.football-data.org when it attempted to start, hence the error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641564 Title: nginx service fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1641564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
