New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Traffic is sent to a terminated server #1169
Comments
One and two servers in your servers are two different servers, how do you achieve that both servers can automatically deploy SSL certificates? |
I now use the manual certificate creation method
|
The proxy only runs on server "one". |
@ninjaPixel could you please explain how you tested this? I had tried to test this scenario, but there must have been a flaw in how I did it. |
1 - I deployed my application to two servers ('one' and 'two' in my config) on my cloud hosting provider (Vultr). |
When using the loadBalancing option (with two servers, named 'one' and 'two'), I expected nginx to route all traffic to server 'one' when server 'two' is terminated.
Zero downtime deploys do work for me with this setup, however, if server 'two' is terminated (i.e. I just shut it down from my cloud hosting provider) then clients that were connected to 'two' are not connected to 'one' instead (after doing a browser refresh).
I've tried this by using clients with lots of different IP addresses (by using Tor browser) and my guess is that nginx is routing traffic based on the client's IP address, and it isn't checking the health of the server first.
Based on this snippet from your 1.5 blog post, I would expect traffic to only be sent to healthy servers:
Mup version (
mup --version
): 1.5.1Mup config
The text was updated successfully, but these errors were encountered: