Re: invalid default_server parrameter

2017-04-24 Thread Joel Parker
I'm still trying to figure this all out. I am just going to remove default_server for now like you suggested. The config checker doesn't complain anymore ... we'll see if it works. Joel On Mon, Apr 24, 2017 at 2:10 PM, Joel Parker wrote: > I have many servers sending ssl which I am trying to te

Re: invalid default_server parrameter

2017-04-24 Thread Maxim Dounin
Hello! On Mon, Apr 24, 2017 at 02:10:47PM -0500, Joel Parker 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 4

Re: invalid default_server parrameter

2017-04-24 Thread Jeff Dyke
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 dozen

invalid default_server parrameter

2017-04-24 Thread Joel Parker
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 erro