Quantcast
Channel: HAProxy community - Latest topics
Viewing all articles
Browse latest Browse all 4718

Wildcard Cert FE, Self-signed BE

$
0
0

Hello everyone,

I have a FE I am trying to create. The FE is using a wildcard.domain.com certificate. The backend servers connect on 443, and use a self-signed certificate. In packet captures, I get a fatal error from the health checks (error 21, which is due to unknown CA). I have modified the health checks to use ‘check-ssl verify none’ and my backend is up. The servers are also up when I hit them individually.

It’s returning a 502 error when I try to access the server via load balancer. It looks like HAProxy won’t connect to the backend. Do I somehow need to ‘force’ it to trust the self signed certificate? This works in f5, but not here.

Ideas?

EDIT: 502, not 503

3 posts - 3 participants

Read full topic


Viewing all articles
Browse latest Browse all 4718

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>