nginx not forwarding requests to backend servers.

Brian Pugh project722 at gmail.com
Wed Jul 27 14:07:28 UTC 2016


nginx-1.10.1-1.el6.ngx.x86_64 on RHEL 6. What do you mean by rename the
upstream? I thought if my backend applications are listening for requests
on https://myapplicationsite.net then thats what the upstream server needs
to be defined as in nginx? If I do rename and my backend server listen on
https://myapplicationsite.net then how does nginx know to use that in the
https header? What about the server_name decalaration and the info in proxy
pass? Would I need to change that to in order to match the new upstream
name?

On Wed, Jul 27, 2016 at 8:55 AM, crasyangel <nginx-forum at forum.nginx.org>
wrote:

> test ok with nginx 1.8.0,which nginx version you use? nginx must be
> confused
> by same domain name and upstream name, rename the upstream name!
>
> Posted at Nginx Forum:
> https://forum.nginx.org/read.php?2,268548,268550#msg-268550
>
> _______________________________________________
> 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/20160727/a77baa36/attachment.html>


More information about the nginx mailing list