> I'm new to servers and proxies,
> But don't you think running both nginx and Apache on port 80 of same machine
> will cause one of those to fail to start.
> In my opinion backend should be on different IP:port combination.
> Please correct me if I'm wrong.
It is correct (though you can work ar
Thank you. In my setup all 3 servers in the upstream block will answer
requests for "myapplication.net" . Knowing that, would you say my config I
have is sufficient?
It should be yes.
rr
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.
I'm new to servers and proxies,
But don't you think running both nginx and Apache on port 80 of same machine will cause one of those to fail to start.
In my opinion backend should be on different IP:port combination.
Please correct me if I'm wrong.
On 05-Jul-2016 21:41, "NdridCold ." wrote: I wa
Thank you. In my setup all 3 servers in the upstream block will answer
requests for "myapplication.net" . Knowing that, would you say my config I
have is sufficient?
On Tue, Jul 5, 2016 at 1:42 PM, Reinis Rozitis wrote:
> But I am confused on a few concepts here. First of all, should my server
>
But I am confused on a few concepts here. First of all, should my server
name in the "upstream" directive be the same name in the "server_name"
directive in the "server" stanza? Here is what I have so far:
And to recap, should my server name in the "upstream" directive be the
same name in the
I was getting a host not found problem while trying to start nginx.
nginx: [emerg] host not found in upstream "backendservers.com" in
/etc/nginx/conf.d/default.conf:37
I am fairly certain that this is because there is no name resolution for "
backendservers.com" in our DNS. So I changed up a fe
