Styjun

Why has Speaker Pelosi been so hesitant to impeach President Trump?

Giving a good fancy look to a simple table

What is the meaning of first flight and introduction in aircraft production?

How is this situation not a checkmate?

IEEE 754 square root with Newton-Raphson

How do we decide/plan an SLA for an NP-hard optimization process running in production?

Realistically, how much do you need to start investing?

How dangerous are my worn rims?

How deep is the liquid in a half-full hemisphere?

Can a passenger predict that an airline or a tour operator is about to go bankrupt?

Shell Sort, Insertion Sort, Bubble Sort, Selection Sort Algorithms (Python)

Do actions granted by the Haste spell count as "your action"?

Can an untrusted VPN client monitor my network activity?

How to find places to store/land a private airplane?

PhD Length: are shorter PhD degrees (from different countries) valued differently in other counter countries where PhD Is a longer process?

How do we know neutrons have no charge?

Phonetic distortion when words are borrowed among languages

Confusion regarding control system of Mars Rover?

Lighthouse Alternatives

C++ Standard-Thread Threadpool

Convert a string of digits from words to an integer

Short story about a potato hotel that makes its guests into potatoes throughout the night

What is The Difference Between Increasing Volume and Increasing Gain

What does a textbook look like while you are writing it?

How to communicate SSL handshake failure information between two different server configurations on nginx

node.js and nginx SSL handshake failureNGINX caching proxy fails with SSL23_GET_SERVER_HELLO:sslv3 alert handshake failureSSL Handshake failures with client and servernginx - log SSL handshake failuresSSL on Load Balanced Nginx ServerSSL handshake failure (40) between nginx and iOS 11 onlynginx and tomcat ssl issue - SSL23_GET_SERVER_HELLO:sslv3 alert handshake failureNginx - SSL handshake error when connecting to upstream with self signed certificateHow to configure NginX: one domain with SSL, another withoutSetup Nginx server with SSL configured

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;

0

I have two nginx servers running locally, each serving a 1X1 pixel image, and its own certificate. This may be an unconventional requirement, but what I want is that if server 1 has an SSL handshake failure, then this information should travel to server 2, which upon hearing this information, sends a redirect. Is something like this possible? The only information I have about the first server which fails is through the error logs which register a SSL handshake failure, but I am not sure how to communicate this to server 2. And since I want to do a redirect for the same client, I am not sure if using error logs is the best idea. Is there some way to for example, set a particular variable in server 1, and then read that in server 2. Upon reading this, server 2 sends a redirect to a chosen domain name.

ssl nginx tls1.2

share|improve this question

asked Mar 28 at 20:15

QPTRQPTR

69155 gold badges1414 silver badges3434 bronze badges

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  You may start by explaining more your server1/server2 setup because it looks strange and hence you are maybe creating a problem yourself that has a simpler solution. Also since this is not programming related, you will be more on topic at Server Fault. But to summarize if there is an handshake error, this came back to the client, which will not continue the exchange, whatever you do on the server. So I fail to see how you want to have server2 start to intervene there...
  
  – Patrick Mevzek
  Mar 28 at 20:45
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @PatrickMevzek its something of an unconventional use-case that I am testing locally. I do realize that the connection with the first server would be broken down once there is a handshake error, but the connection with server 2 would still be alive, right? So I was wondering if its possible to do a redirect by server 2, once I know that server 1 has had some sort of an error (on server-side). The fact that server 1 has had a failure can be traced via error logs right?
  
  – QPTR
  Mar 28 at 21:51
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  "but the connection with server 2 would still be alive" the connection from where? From the client? The client only connected to server 1 if I understood correctly. Please switch over to Server Fault and give a proper schema about who connects to who, in order to make things clearer/
  
  – Patrick Mevzek
  Mar 28 at 22:28
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @PatrickMevzek Will do, thanks for pointing out!
  
  – QPTR
  Mar 29 at 0:07
  

  
  
  
  

add a comment
 | 

0

I have two nginx servers running locally, each serving a 1X1 pixel image, and its own certificate. This may be an unconventional requirement, but what I want is that if server 1 has an SSL handshake failure, then this information should travel to server 2, which upon hearing this information, sends a redirect. Is something like this possible? The only information I have about the first server which fails is through the error logs which register a SSL handshake failure, but I am not sure how to communicate this to server 2. And since I want to do a redirect for the same client, I am not sure if using error logs is the best idea. Is there some way to for example, set a particular variable in server 1, and then read that in server 2. Upon reading this, server 2 sends a redirect to a chosen domain name.

ssl nginx tls1.2

share|improve this question

asked Mar 28 at 20:15

QPTRQPTR

69155 gold badges1414 silver badges3434 bronze badges

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  You may start by explaining more your server1/server2 setup because it looks strange and hence you are maybe creating a problem yourself that has a simpler solution. Also since this is not programming related, you will be more on topic at Server Fault. But to summarize if there is an handshake error, this came back to the client, which will not continue the exchange, whatever you do on the server. So I fail to see how you want to have server2 start to intervene there...
  
  – Patrick Mevzek
  Mar 28 at 20:45
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @PatrickMevzek its something of an unconventional use-case that I am testing locally. I do realize that the connection with the first server would be broken down once there is a handshake error, but the connection with server 2 would still be alive, right? So I was wondering if its possible to do a redirect by server 2, once I know that server 1 has had some sort of an error (on server-side). The fact that server 1 has had a failure can be traced via error logs right?
  
  – QPTR
  Mar 28 at 21:51
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  "but the connection with server 2 would still be alive" the connection from where? From the client? The client only connected to server 1 if I understood correctly. Please switch over to Server Fault and give a proper schema about who connects to who, in order to make things clearer/
  
  – Patrick Mevzek
  Mar 28 at 22:28
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @PatrickMevzek Will do, thanks for pointing out!
  
  – QPTR
  Mar 29 at 0:07
  

  
  
  
  

add a comment
 | 

I have two nginx servers running locally, each serving a 1X1 pixel image, and its own certificate. This may be an unconventional requirement, but what I want is that if server 1 has an SSL handshake failure, then this information should travel to server 2, which upon hearing this information, sends a redirect. Is something like this possible? The only information I have about the first server which fails is through the error logs which register a SSL handshake failure, but I am not sure how to communicate this to server 2. And since I want to do a redirect for the same client, I am not sure if using error logs is the best idea. Is there some way to for example, set a particular variable in server 1, and then read that in server 2. Upon reading this, server 2 sends a redirect to a chosen domain name.

ssl nginx tls1.2

share|improve this question

asked Mar 28 at 20:15

QPTRQPTR

69155 gold badges1414 silver badges3434 bronze badges

share|improve this question

asked Mar 28 at 20:15

QPTRQPTR

69155 gold badges1414 silver badges3434 bronze badges

share|improve this question

asked Mar 28 at 20:15

QPTRQPTR

69155 gold badges1414 silver badges3434 bronze badges

asked Mar 28 at 20:15

QPTRQPTR

69155 gold badges1414 silver badges3434 bronze badges

asked Mar 28 at 20:15

QPTRQPTR

69155 gold badges1414 silver badges3434 bronze badges