Hi,

a similar issue has been discussed here:
https://forum.nginx.org/read.php?2,264392,264392
In short: If you have any http2 directives for a port in your
configuration, every connection on that port can use http2.
Im not sure if specifying the listen IP will help in this case, but its
worth a try. Modify your listen directives to "listen ip:port options;",
for example for your last vhost: "listen 192.168.1.163:443 ssl http2;"

Mit Freundlichen Grüßen
Sven Kirschbaum

2016-03-15 0:39 GMT+01:00 Roswebnet <nginx-forum@forum.nginx.org>:

> Thank you for your fast response.
>
> However, could you please provide an example of "IP on the listen
> directive"
>
> I am accessing content from Firefox like https://192.168.1.162 for https
> connection and
> https://192.168.1.163 for http2. Moreover, those ip also accessible by
> http:// and served also well, but in my opinion it should gave some kind
> of
> error, because those server names do not have port 80 configured.
>
> Posted at Nginx Forum:
> https://forum.nginx.org/read.php?2,265326,265328#msg-265328
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx