Hi,
I'm trying to set up a balance as follows (example):
upstream loadbalance {
server server:9091;
server server:9092;
server server:9093;
}
location / {
proxy_set_headerHost $server_name;
proxy_request_buffering off;
proxy_buffering off;
proxy_re
People,
I have a number of Ruby test?.cgi scripts that work fine but this one
shows an error:fb_chatbot4.cg
2017/06/07 21:32:22 [debug] 15522#0: *32 http upstream check client,
write event:1, "/cgi-bin/fb_chatbot4.cgi"
2017/06/07 21:32:22 [debug] 15522#0: *32 http upstream recv(): -1 (11:
Re
> 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
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.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,272660,272675#msg-272675
___
nginx mailing lis
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello!
On 03/01/2017 12:15 AM, Maxim Dounin wrote:
> Hello!
>
> On Tue, Feb 28, 2017 at 10:57:01PM +0700, Dewangga Bachrul Alam
> wrote:
>
>> Currently I have problem with upstream with IPv6. For example I
>> have an origin with subdomain
>> dual-
Hello!
On Tue, Feb 28, 2017 at 10:57:01PM +0700, Dewangga Bachrul Alam wrote:
> Currently I have problem with upstream with IPv6. For example I have
> an origin with subdomain dual-stack-ipv4-ipv6.xtremenitro.org.
>
> dual-stack-ipv4-ipv6.xtremenitro.org IN A 192.168.1.1
> dual-stack-ipv4-ipv6.x
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello!
Currently I have problem with upstream with IPv6. For example I have
an origin with subdomain dual-stack-ipv4-ipv6.xtremenitro.org.
dual-stack-ipv4-ipv6.xtremenitro.org IN A 192.168.1.1
dual-stack-ipv4-ipv6.xtremenitro.org IN 2001:xx:xx
