-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello!
Yes I've force my system to read IPv4 first. But, just curios, why IPv6 upstream can't serve the traffic? If I access the IP Address using browser, it's normal. I am using Cent OS 7. On 03/01/2017 09:04 PM, Lukas Tribus wrote: >> Did anyone have a solution for this? I also have many of these >> errors logged because I am using Google Container Engine that >> does not support IPv6. > > Try ´man gai.conf´ to configure getaddrinfo behavior [1]. > > > You could also try forcing a ipv6=no nginx resolver by using a > variable: > > set $blablaserver "dual-stack-ipv4-ipv6.xtremenitro.org"; server > $blablaserver; > > Not sure if that works with upstream servers, it does work with > proxy_pass. > > > cheers, lukas > > [1] http://man7.org/linux/man-pages/man5/gai.conf.5.html > _______________________________________________ nginx mailing list > nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQI4BAEBCAAiBQJYuEmoGxxkZXdhbmdnYWJhQHh0cmVtZW5pdHJvLm9yZwAKCRDl f9IgoCjNcK0SEACqb3fBlvvN7K5rf+3xQ7Cr7CssL0XnKwAoF/UbtvLZITsHcxyy /FO2xqKQ9QG5eTqtMCPMkG+VoyZmpOBbzErYyF4+8AKPFlADyuk3zC3W0Wfpy2TE FXUOBL/fQvJa3F4HW1q7YTLxt2TUyPXxdjZkVaZTAaExpJRDZWuzq00l2ycmvLPL RmvVy14p+1XFZSEzHcn0pC49OCrhPHv8Moo7e+HbLS3+f/LYAyKT7tzVtdn9UXYO sBf4k46ZoVW2kYBz7NgQ6RMSMbaAySStSbTPUifmQFR3h87a6mHpDzJ7DK9VDh1v W37ROP0SWBs2BpA3iPwe9z+dGp+a2jmx3FbZCjnD5A++eGapY6+mqSFFdDM6fZmf y2e9mM5nFQi0aRw+M53a2UI6HcE0pxQLBG1cpPLGtK6PMcB1dOTVvrZHN2R+HIAp zDsh90r08u/Ntxj8M6eapLrhGQz4xKP3MoJJhtUON3fxiP5j6Edyf5+Z+XOpIyf/ 2ipoEJIt+0zc5fJcHVbmqrXkDE0GPeYlxpIqCb4LIRpxLZ4DsHLNZGlAtPCTudgS XCUiYduGSgir+Ga02Knprbk01OS5Jczg/ZtWtcIO4CH0A8aYKMB3gnuQhAMYHI6P uaxMFIiq04KL9g+k763U0pR0y+URXRU+7Y2ZAVeVaIDDk4Y+MCr85Y7WyQ== =PHsr -----END PGP SIGNATURE----- _______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
