invalid default_server parrameter

Jeff Dyke jeff.dyke at gmail.com
Mon Apr 24 19:19:12 UTC 2017


if you're using sni, you should be able to use _ as the server_name or
remove default server b/c if this is going to represent many servers, from
memory, default_server is not a value you want.  for example i run nginx
behind haproxy to create letsencrypt certs, which will listen to currently
dozens of request:  (of course you may not require proxy_protocol)

----
listen 8888 proxy_protocol;
server_name _;
----

On Mon, Apr 24, 2017 at 3:10 PM, Joel Parker <joel.parker.gm at gmail.com>
wrote:

> I have many servers sending ssl which I am trying to terminate. So I
> wanted to create a statement that was a catch all instead of listening for
> each ip address. I thought this would do it :
>
> server {
>
>       listen 443 ssl  default_server;
>
> ......
>
> }
>
> but when I run nginx -t, I keep getting the error : nginx: [emerg] the
> invalid "default_server" parameter in /etc/nginx/nginx.conf:13
>
> Is this the correct way of doing a catch all incoming ssl traffic and what
> is wrong with my syntax ?
>
> Joel
>
> _______________________________________________
> 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/20170424/3b0792a7/attachment.html>


More information about the nginx mailing list