> But, just curios, why IPv6 upstream can't serve the traffic?
Because if you configure IPv6 on your system but don't have
IPv6 connectivity, it will try and fail.
> If I access the IP Address using browser, it's normal.
Because the browser probably recognizes the broken
configuration and work
-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
> 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 $blablas
