Re: duplicate ports across servers in nginx.conf

2023-05-31 Thread Francis Daly
On Wed, May 31, 2023 at 06:14:41AM +, Yuval Abadi via nginx wrote: Hi there, I don't speak for the project, but my guess is: > If the configuration has 2 servers sharing the same name and the same port > I got this warning: > "nginx: [warn] conflicting server name "http://www.mut.com/"; on 0

RE: duplicate ports across servers in nginx.conf

2023-05-30 Thread Yuval Abadi via nginx
me? Is NGINX set the bit default_server ,on the first "ngx_http_conf_addr_t", of the first server, that read from conf file? (if no default_server was defined)? Thanks -Original Message- From: nginx On Behalf Of Francis Daly Sent: Tuesday, 30 May 2023 19:57 To: Yuval

Re: duplicate ports across servers in nginx.conf

2023-05-30 Thread Francis Daly
On Tue, May 30, 2023 at 06:50:19AM +, Yuval Abadi via nginx wrote: Hi there, > When I have 2 servers in nginx.conf with same listen port if the server > have name, nginx issue warning ignore … but nit failed to load. > What happens is only the first server in conf binds the socket. > A

duplicate ports across servers in nginx.conf

2023-05-29 Thread Yuval Abadi via nginx
Hi When I have 2 servers in nginx.conf with same listen port if the server have name, nginx issue warning ignore … but nit failed to load. What happens is only the first server in conf binds the socket. And worse, If no server names I did not get a warning. Only if the keyword “default ser