Weird problem cannot standup nginx on 443 ipv4

[Julian Brown]

I finally figured it out, and I cannot believe it passed a syntax checker.

This is what I had:

server {
    server_name learngigs.com www.learngigs.com

    listen 443;
    listen [::]:443;

I did not have a semi colon after the server name directive.   The syntax
checker said it was fine, so I do not know what it was trying to do.
 Anyway thank you all.

Julian


On Thu, Apr 25, 2019 at 6:21 PM OiledAmoeba <nginx-forum at forum.nginx.org>
wrote:

> 25. April 2019 21:27, "Julian Brown" <julian at jlbprof.com> schrieb:
>
> > listen 443;
> > listen [::]:443;
>
> I'm lazy, so I used "listen [::]:443 ssl http2 ipv6only=off" instead of two
> listen-directives. Maybe you want to try this, so nginx must use IPv4 and
> IPv6 because of the ipv6only=off directive.
>
> If I try learngigs.com my browser points me to an IPv4-SSL-site (so it
> looks
> like it works). If I try http://learngigs.com:80/ my browser is searching
> forever...
>
> Posted at Nginx Forum:
> https://forum.nginx.org/read.php?2,283924,283928#msg-283928
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20190425/cd6317f6/attachment.html>