Nginx does not listen on 443 IPV6 to more than one website where to dig?

In General, configuring using Benin mother support and the VPS over IPV6 are faced with the following jamb work
Conventionally, there is a pool of sites and one of them prescribed in the config Directive
listen 443 ssl http2; 
 listen [::]:443 ssl ipv6only http2=on;

This site is a single from a pool of sites only works on V4 and V6
when you try to make the Directive listen [::]:443 ssl ipv6only http2=on; other sites Nginx complains that
no way - this is supposedly already in this config.
If you try to go Kurla to other sites on V6 - server returns code 444 (empty response)
Question - where to dig?
April 7th 20 at 10:43
2 answers
April 7th 20 at 10:45
Logically, primitively speaking, this parameter may specify not gonfie host (single site), and in the config of the server. Not sure what you have for the farm, but I use nginx - I have config server and in the directory of each site are the configs of the virtual hosts... I have only certificates that specify, respectively, the site works in http or https... not my thing, sumnichat will not work probably ((
April 7th 20 at 10:47
this Directive tells whether to listen only on v6 wildcard [::] or both v6 and v4
the question is, what you want to achieve?)
if you want the server listened and 4 and 6 then write so
listen [::]:443 ssl http2;

if you want to listen v6 only write

listen [::]:443 ssl ipv6only http2=on;

in any of the configs and they will only listen to the v6

nginx.org/en/docs/http/ngx_http_core_module.html#listen
Your truth... were a few moments, and then you know what happened? :)
The first site of the 10 first stopped responding, and the rest are reversed, and so on,
agreed -
1. Nah this v6
2. Locally and globally, almost no one is ready for it, even my dash MGTS (Moscow!) officially it does not work...
Play and will.. - Chelsey79 commented on April 7th 20 at 10:50
I have all sites only work via v6. savings on v4 addresses significant. and to avoid problems with the availability of v6 clients just all proximedia using cloudflare
about the readiness of the v6 I agree. all so sad that the sadness takes the.. - Godfrey76 commented on April 7th 20 at 10:53
@Godfrey76, I presented how potentially your sites lose customers who do not suspect that your site has but only on the v6 that made me sad...
after all, if the default city from a huge provider, there is no support for v6 then sadness bore down.... - Chelsey79 commented on April 7th 20 at 10:56
@Godfrey76, if not a secret - how can you work only in v6 if its support through the stump deck?
If your only streaming and torrents it probably makes sense and the usual sites, well XS.. so many customers to lose.. - Chelsey79 commented on April 7th 20 at 10:59
I wrote cloudflare.com
we will not lose) - Godfrey76 commented on April 7th 20 at 11:02
@Godfrey76, I'm probably being obtuse, had a rough day - just a little know - how you are losing customers if brow ISP does not support ipv6 with all the consequences? - Chelsey79 commented on April 7th 20 at 11:05
@Chelsey79between the client which does not have ipv6 and a server that does only ipv6 is proxeny for the ipv4 service cloudflare.com .
The client only sees the address of proxenia, where he throws further traffic - not the client business. - royal_Marvin commented on April 7th 20 at 11:08
@royal_Marvin, I understand the reverse proxy, I first thought about it but thought you never know, Thank you! - Chelsey79 commented on April 7th 20 at 11:11

Find more questions by tags NginxNetwork administration