On Fri, Jan 05, 2018 at 01:23:47PM +0000, Mik J via nginx wrote:
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 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.
Can you compare this tcpdump, with the start of a tcpdump of a
working connection (when you have told nginx to listen on a dedicated
IP:port)? Perhaps that will show which part of the communication fails.
(If you can tcpdump on both the client and server, maybe that will show
if something is lost in the network.)
Do you see the same problem if you omit ssl? If so, that might make it
easier to test manually. If not, that's probably useful information.
> I forgot to say that I d-natted my IPv6 and the one I displayed is not a public IP.I was wondering if nginx treats it differently
nginx should not care; something outside of nginx might care.
If you make a "curl" request from the nginx machine to itself, do you
see the problem?
And - if you omit nginx and just use a tcp listener (such as netcat)
as the server, do you see a similar problem?