On 12/12/2020 2:54 π.μ., Maxim Dounin wrote:
Glad it works now, and hope the previous behaviour is clear now as
well: it is a result of no IPv4 listening socket on port 443 in
the second vhost in the original configuration.
Thank you Maxim, I appreciate your detailed explanation and all your
Hello!
On Fri, Dec 11, 2020 at 01:44:06PM +0200, Nikolaos Milas wrote:
> On 10/12/2020 4:42 μ.μ., Maxim Dounin wrote:
> > How do you test it? Note well that the second vhost is only
> > available on port 443 via IPv6.
> >> Finally, what is the best way to successfully listen (i.e. the suggested
On 10/12/2020 4:42 μ.μ., Maxim Dounin wrote:
How do you test it? Note well that the second vhost is only
available on port 443 via IPv6.
Finally, what is the best way to successfully listen (i.e. the suggested
way to configure the "listen" directives) to 80 and 443 ports on both
IPv4 and IPv6 o
Hello!
On Wed, Dec 09, 2020 at 11:34:38PM +0200, Nikolaos Milas wrote:
> Hello,
>
> On a Centos 7 with nginx-1.18.0 I have configured two vhosts, as follows:
>
> First one:
>
> server {
>
> listen [::]:80 ipv6only=off;
>
> listen 443 ssl http2 default deferred;
> listen
Hello,
On a Centos 7 with nginx-1.18.0 I have configured two vhosts, as follows:
First one:
server {
listen [::]:80 ipv6only=off;
listen 443 ssl http2 default deferred;
listen [::]:443 ssl http2 default deferred;
server_name site1.world.example.com;
ssl_certificat
