Derek Zeanah
March 21, 2012, 02:05 PM
Here's the problem I'm trying to solve:
When people try and connect to THR when it's down, they eventually get redirected to the secure version of THR, which doesn't exist, and times out until the browser is cleared.
What I've done: purchased and installed valid certificates for the https:// version of THR. Configured the firewall to allow the traffic. Configured the web servers to use this certificate. Configured the load balancer to successfully verify which servers are up and direct traffic to them (this took the longest.)
So, if you've been having problems connecting you should now see the HTTPS:// version of THR correctly. Once connected, you should be automagically redirected to the non-secure version either immediately, or when you click on a link.
Is this happening?
If so, are you getting any weird error messages?
Thanks. More complexity than I want to take on, but hopefully a whole range of problems will disappear now.
When people try and connect to THR when it's down, they eventually get redirected to the secure version of THR, which doesn't exist, and times out until the browser is cleared.
What I've done: purchased and installed valid certificates for the https:// version of THR. Configured the firewall to allow the traffic. Configured the web servers to use this certificate. Configured the load balancer to successfully verify which servers are up and direct traffic to them (this took the longest.)
So, if you've been having problems connecting you should now see the HTTPS:// version of THR correctly. Once connected, you should be automagically redirected to the non-secure version either immediately, or when you click on a link.
Is this happening?
If so, are you getting any weird error messages?
Thanks. More complexity than I want to take on, but hopefully a whole range of problems will disappear now.