<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class="">On 15 Aug 2018, at 14:05, Sergey Kandaurov <<a href="mailto:pluknet@nginx.com" class="">pluknet@nginx.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><br class=""><blockquote type="cite" class="">On 15 Aug 2018, at 13:02, Gerben Wierda <<a href="mailto:gerben.wierda@rna.nl" class="">gerben.wierda@rna.nl</a>> wrote:<br class=""></blockquote><br class="">[..]<br class=""><br class=""><blockquote type="cite" class="">But nginx reports (apparently once per session):<br class=""> 2018/08/15 11:34:48 [error] 242#0: *881 kevent() reported that connect() failed (61: Connection refused) while connecting to upstream, client: 192.168.2.67, server: MYHOST, request: “GET /gerbentest/?delimiter=%2F&max-keys=1000&prefix=duplicati-ifdb6b7ac174b4e5094b04e7321d10c6b.dindex.zip.aes HTTP/1.1”, upstream: “<a href="http://[::1]:9003/gerbentest/?delimiter=%2F&max-keys=1000&prefix=duplicati-ifdb6b7ac174b4e5094b04e7321d10c6b.dindex.zip.aes" class="">http://[::1]:9003/gerbentest/?delimiter=%2F&max-keys=1000&prefix=duplicati-ifdb6b7ac174b4e5094b04e7321d10c6b.dindex.zip.aes</a>”, host: “MYHOST:9000”<br class=""></blockquote><br class="">Note [::1]:9003 in upstream, which is likely the address nobody listens.<br class=""></div></div></blockquote><div><br class=""></div><div>Ha, yes, now I see, the address is the IPv<b class="">6</b> address for localhost. Silly me, I though in the network stack 127.0.0.1 and [::1] worked more or less as aliases for the same port, but apparently not. So, while minio is listening on 127.0.0.1:9003 it is not listening on [::1]:9003</div><div><br class=""></div><blockquote type="cite" class=""><div class=""><div class="">I’d like to find out why this happens. Can someone help me find the cause of these errors? The config for the minio servers is:<br class=""><blockquote type="cite" class=""><br class="">server {<br class=""> listen 9000 ssl;<br class=""> server_name MYHOST;<br class=""> ssl_certificate minio_certificate_chained.crt;<br class=""> ssl_certificate_key minio_certificate.key;<br class=""> ssl_protocols TLSv1.2;<br class=""> proxy_buffering off;<br class=""> client_max_body_size 1000m;<br class=""> location / {<br class=""> proxy_set_header Host $http_host;<br class=""> if ($http_authorization ~* "^AWS4-HMAC-SHA256 Credential=REMOVED") {<br class=""> proxy_pass <a href="http://localhost:9001" class="">http://localhost:9001</a>;<br class=""> }<br class=""></blockquote><br class="">If a domain name resolves to several addresses,<br class="">which is apparently the case for "localhost”,<br class=""></div></div></blockquote><blockquote type="cite" class=""><div class=""><div class="">all of them will be used in a round-robin fashion.<br class=""><br class="">See for details:<br class=""><a href="http://nginx.org/r/proxy_pass" class="">http://nginx.org/r/proxy_pass</a><br class=""></div></div></blockquote><div><br class=""></div><div>If I use dig or nslookup to resolve localhost, I get just 127.0.0.1. But my /etc/hosts contains both IPv4 and IPv6 for localhost and nginx round-robins over both apparently. Using 127.0.0.1 instead of localhost is the correct solution, then.</div><div><br class=""></div><div>G</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class="">-- <br class="">Sergey Kandaurov<br class=""><br class="">_______________________________________________<br class="">nginx mailing list<br class=""><a href="mailto:nginx@nginx.org" class="">nginx@nginx.org</a><br class="">http://mailman.nginx.org/mailman/listinfo/nginx</div></div></blockquote></div><br class=""></body></html>