Re: session persistance with IP hash

Very thorough and detailed explanation, even if it was "simplified". Both you and Reinis have been a tremendous help. On Thu, Jul 28, 2016 at 11:07 AM, Robert Paprocki < rpapro...@fearnothingproductions.net> wrote: > Hello, > > On Thu, Jul 28, 2016 at 7:32 AM, Brian Pu

Re: session persistance with IP hash

Yesterday once I got the traffic going to the backend servers from nginx I noticed that I was pinned to "backend3", which is last in the order. And since I am the one setting this up I am the only user. So I changed up my order just to see the effects of calculating a new hash. Instead of: upstrea

Re: session persistance with IP hash

Reinis Rozitis said: The problem with this (if it matters) is that there is no (pre)defined value of the cookie BACKEND which would specifically route particular client to particular backend - I mean for example if you use values 'backend1', 'backend2', 'backend3' the hashed keys might (or not) asw

Re: session persistance with IP hash

Reinis Rozitis said: Yes, you can use different hash mechanisms/keys (for example specific cookies etc): https://nginx.org/en/docs/stream/ngx_stream_upstream_module.html#hash There are also some third-party sticky cookie modules. Took a look at the link, but I have no idea what that would look li

session persistance with IP hash

Running nginx free version 1.10.1-1.el6.ngx.x86_64 on RHEL 6.7. In my conf I am using http { upstream backend { # Use ip hash for session persistance *ip_hash;* server backend1:80; server backend2:80; server backend3:80; } My understanding is that the

Re: nginx not forwarding requests to backend servers.

plus? If my nginx server has an SSL cert loaded that validates the hostnames for the backend servers and my backend servers also have the same cert and communications are going over port 443 why would I need to do anything else? On Wed, Jul 27, 2016 at 12:16 PM, Brian Pugh wrote: > Ok. I

Re: nginx not forwarding requests to backend servers.

Ok. I was able to get it working by changing this: proxy_pass http://ssl_myapplicationsite.net <http://ssl_test-resolve.cspire.net/>; to this: proxy_pass *https*://ssl_myapplicationsite.net <http://ssl_test-resolve.cspire.net/>; On Wed, Jul 27, 2016 at 12:07 PM, Brian

Re: nginx not forwarding requests to backend servers.

Still not working. Logs show: 2016/07/27 11:59:35 [warn] 28038#28038: *3 upstream server temporarily disabled while reading response header from upstream, client: 192.168.254.202, server: myapplicationsite.net, request: "GET / HTTP/1.1", upstream: *"http://192.168.155.120:443/

Re: nginx not forwarding requests to backend servers.

Ok. This looks like progress. However it still fails. Here is my config as it stands now. in nginx.conf: http { upstream myappliationsite.net { ip_hash; server backendappsite1.net; server backendappsite2.net; server backendappsite3.net; } In default.conf: serve

Re: nginx not forwarding requests to backend servers.

in both nginx.conf and default.conf using the names/info I have provided? On Wed, Jul 27, 2016 at 9:48 AM, Francis Daly wrote: > On Wed, Jul 27, 2016 at 07:33:31AM -0500, Brian Pugh wrote: > > Hi there, > > > I am using nginx as a load balancer. However when I type in the U

Re: nginx not forwarding requests to backend servers.

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 http

nginx not forwarding requests to backend servers.

I am posting this again because a copy never appeared in my inbox. Please ignore if it was actually delivered to the group already. I am using nginx as a load balancer. However when I type in the URL for my site, which resolves to the IP of the load balancer, I get the default nginx page saying "n

nginx not forwarding requests to backend servers.

I am using nginx as a load balancer. However when I type in the URL for my site, which resolves to the IP of the load balancer, I get the default nginx page saying "nginx has been setup more configuration is required". I would expect nginx to forward my request through to the backend servers I have

Re: does nginx forward requests to backend servers using http or https?

e, Jul 5, 2016 at 9:26 AM, Brian Pugh mailto:bp...@cscontract.com>> wrote: I am using the free version of nginx on RHEL 6.7. The version is : nginx-1.10.1-1.el6.ngx.x86_64 When using nginx as a load balancer I would like to know if nginx forwards requests to back

does nginx forward requests to backend servers using http or https?

I am using the free version of nginx on RHEL 6.7. The version is : nginx-1.10.1-1.el6.ngx.x86_64 When using nginx as a load balancer I would like to know if nginx forwards requests to backend servers using http or https?? ___ nginx mailing list