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 d
25. April 2019 21:27, "Julian Brown" 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
I just tried both, (removed the ipv6 entry) and tried both of the above.
Now nothing is on 443, not even ipv6 (which is ok).
This is totally wierd.
Thank you
Julian
On Thu, Apr 25, 2019 at 2:37 PM Rainer Duffner
wrote:
>
>
> Am 25.04.2019 um 21:27 schrieb Julian Brown :
>
> listen 443;
>
> Am 25.04.2019 um 21:27 schrieb Julian Brown :
>
> listen 443;
> listen [::]:443;
You most certainly want
listen 443 ssl
or
listen 443 ssl http2
Not sure if it solves your problem.
___
nginx mailing list
nginx@nginx.org
http://mailma
Sorry this is a bit long:
On Debian Stretch 9.8, fresh install. I want to setup nginx as a load
balancer to just one node at this time just to play with it and understand
it.
I installed the apt package nginx-full, which I assume will have all there.
So I slightly modified nginx.conf, where I
Hi.
I have one URL for all my websites, applications and so.
Let's say it's system.mydomain.com. Most of my websites is Apache + PHP and
the applications is Tomcat. So far so good, no problem there.
My nginx config that's working for everything else:
server {
listen 80;
server_nam
