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
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
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
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
Hi
On Mon, Apr 24, 2017 at 05:58:34PM +0200, Sékine Coulibaly wrote:
> Hi,
>
> I'm gathering some information regarding UDP load balancing. I've come
> accross this in
> https://www.nginx.com/resources/admin-guide/udp-health-check/ and I'm quite
> puzzled :
>
> "NGINX can mark the server as unav
Hi,
I'm gathering some information regarding UDP load balancing. I've come
accross this in
https://www.nginx.com/resources/admin-guide/udp-health-check/ and I'm quite
puzzled :
"NGINX can mark the server as unavailable and stop sending UDP datagrams to
it for some time if the server replies with
> Reinis I found that www-data was also a member of group 33 so I changed my
> user in nginx.conf to that and it is now working.
>
> Many thanks for your help with this one.
It is most likely also the correct user just nginx in configuration expects the
human-readable name ('www-data') instead o
Reinis I found that www-data was also a member of group 33 so I changed my
user in nginx.conf to that and it is now working.
Many thanks for your help with this one.
Not sure how I mark this as 'Completed' though.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,273798,273813#msg-27381
Reinis thanks very much for your response. The owner shown for :
/var/run/php/php7.0-fpm.sock is 33 & group is 33. Both have read/write
access but other groups have no access rights.
I therefore added the following line at the beginning of nginx.conf
user 33 33;
However when I tried to restart
