> With that config when I try to launch nginx it fails with these errors
>
> Aug 09 11:29:21 myhost nginx[10095]: nginx: [emerg] bind() to [::]:443
> failed (98: Address already in use)
Try to remove the ipv6only=on option it should work just fine without.
Imo the [FE80:...:0001]:443 conf
Thanks for the help.
I'm really feeling pretty stupid atm since I can't seem to find & understand a
how-to document to get this right :-/
So I have this config
server {
listen 80 http2 default_server;
listen [::]:80 http2 ipv6only=on d
> "In versions prior to 0.8.21 this parameter is named simply default. "
>
> Was that a typo? Or is there a new or different usage now ?
Not a typo just nginx being backwards compatible and me using it since 0.5.x or
even earlier (and being lazy).
As far as I remember the directive has been re
I'll get a set up I can fool around with that more easily and see how that
works here.
I notice that you're not using 'default_server" in your listen directive, just
'default'.
Reading here
https://nginx.org/en/docs/http/ngx_http_core_module.html#listen
It's not a listed option and it says
> certificate (and also the test 403 response) for nondefined subdomain requests
> and the order of server {} block
Missed the ending of sentence - .. the order of server {} blocks doesn't matter
(in the test case).
rr
___
nginx mailing list
nginx@ngi
> > Just for testing purposes (if possible) you could either add the IP to
> > both listen directives or remove the ip part from the full-domain
> > server {} block to see if it changes anything.
>
> Hm. That doesn't really make sense to me.
>
> This server has multiple IPs. The hosted server n
Hi,
> you can't expect that they will get the return code.
Okay I guess that makes sense.
Is there any other way to get an attempt to connect to a un-hosted site to get
a "nobody home, go away" response?
Something other than the current "there's a problem with the cert" mis-message?
> I might
> I expect it to fail with a 444, and only have info about the failed subdomain.
The SSL handshake happens before the http status and since the browser doesn't
get a valid certificate it immediately throws an error and ignores the rest.
Unless the users override the error on the browser side (iir
Hi,
My own domain, let's say 'example.com', is registered in the HSTS preload
database (https://hstspreload.org).
I setup my domain as virtual host in Nginx,
/etc/nginx/sites-enabled/example.conf
server {
listen 172.17.0.1:80;
map $cookie_test_debug $forward_to_gray {
# forward to gray1
9cb88042edc55bf85c22e89cf880c63b 10.0.0.1;
}
location ~ ^/test/ {
root /data/www/project;
index index.html;
if ( $uri !~ (css|js)$ ) {
rewrite ^.*$ /test/index.html break;
}
10 matches
Mail list logo
