On Fri, Jan 05, 2018 at 01:23:47PM +, Mik J via nginx wrote:
Hi there,
I don't have a direct solution to the issue you report.
I do have a few things to try, which might help isolate where the problem
is (and therefore where the fix should be).
> The port seems open but there is no ssl tran
Hello Francis,
The port seems open but there is no ssl transaction.When I did a simple tcpdump
capture I saw syn then syn/ack, then ackThe brower displays an error that the
site is not accessible.
I forgot to say that I d-natted my IPv6 and the one I displayed is not a public
IP.I was wondering
On Fri, Jan 05, 2018 at 01:04:52AM +, Mik J via nginx wrote:
Hi there,
> I'm trying to finish to configure nginx for ipv6
> listen [::]:443 ssl;doesn't workbutlisten [fc00:1:1::13]:443 ssl;works
"listen [::]:443 ssl;" seems to work for me.
What does "doesn't work" mean to you, specifically?
Hello,
I'm trying to finish to configure nginx for ipv6
listen [::]:443 ssl;doesn't workbutlisten [fc00:1:1::13]:443 ssl;works
I need to explicitly specify the ipv6 address whereas in ipv4 I don't need to
# nginx -V
nginx version: nginx/1.12.1
server {
listen 443 ssl;
# listen [::]:443 ssl;
