Hello,
I created new LB and i need to test it now with one backend point.
All healthcheck and monitoring is green.
But when i try to open the LB new URL it gives me error as below
526s appear when you have a broken certificate and I assume one of your servers won’t be properly configured for SSL. Check if all your servers have the right certificate in this case.
Thanks,
At this stage im testing with only one server, and this server is working fine with SSL.
But i can not find what is the reason why on multiple refresh the SSL generate issue!
And that happened when i remove the DNS proxy, if i enable DNS proxy then i get server is down !
In that case double check that your load balancer setup actually really just makes use of that one server. Right now it really seems as if every second request went to a server with an invalid certificate, which is why you get the 526.
Looks all right to me, but let’s call the cavalary → @MVP
Right now it really appears as if there were at least two instances and the load balancer would proxy requests alternatingly, but from that screenshot it does seem as if you only had one configured. Maybe the fallback pool? Guessing here
If you have ruled out SSL issues on your server and double checked that you only have that one server configured in your load balancer setup, then I’d be out of ideas I am afraid but support might be able to tell more from their logs, so I’d suggest to open a support ticket.
Can you disable Always Online mode so that you start seeing the actual error from the Origin?
The certificate on the Origin is for the prod hostname, not for the lb1 hostname. What is your current SSL Mode, and over the course of your testing have you changed the SSL Mode a few times?
My guess is that your Origin is actually not always responding, but you are getting a copy of an old error from earlier in your testing when that happens. Disabling Always Online should make diagnosing that easier.