Thanks for you answer.
It turned out a monitoring system was doing DNS lookups in the mean time,
therefore it appeared that 2 client got the same DNS response.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,272713,273041#msg-273041
___
nginx
Hi,
On 03/03/17 03:40, polder_trash wrote:
Hi,
I already tried adding both IP addresses to the DNS. But this, rather
predictably, only sent a handful of users to the secondary node.
This should not be the case ( well, for bind anyway ), as it should be
delivering them in a round robin fashi
So I have a few different thoughts:
1. Yes nginx does support SSL pass through . You can configure nginx to stream
your request to your SSL backend. I do this when I don't have control of the
backend and it has to be SSL. I don't think that's your situation.
2. I suspect that there's something
Hi
Firstly, I am fairly new to nginx.
>From what I understand you have a standard sort of setup.
2 nodes (vm's) with haproxy, allowing nginx to be active / passive.
You have SSL requests which once nginx terminates the SSL, it injects a
security header / token and then I presume it passes thi
Alexsamad,
I might not have been clear, allow me to try again:
* currently 2 NGINX revproxy nodes, 1 active the other on standby in case
node 1 fails.
* Since I am injecting an authentication header into the request, the HTTPS
request has to be offloaded at the node and introduces additional load
Hi
if I am reading this right, you currently have too much load on 1 nginx
server and you wish to releave this by adding another nginx server in front
of it ?
What I have is 2 nodes, but I use pacemaker instead of keepalive - i like
it as a better solution - but thats for another thread.
what yo
Hi,
I have been reading the documentation and also searching this forum for a
while, but could not find an answer to my question.
Currently, I have a 2 NGINX nodes acting as a reverse proxy (in a failover
setup using keepalived). The revproxy injects an authentication header, for
an online website
