We have configure rabbitmq clusters with haproxy using cf-multitentant-rabbitmq-broker release without TLS. Now when we configure
self signed certs on rabbitmq nodes which has the following details,
cn = rabbitmq node-1 ip
sn = rabbitmq node-1 ip, rabbitmq node-2 ip
We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.
The labels on this github issue will be updated when the story is started.
We have configure rabbitmq clusters with haproxy using cf-multitentant-rabbitmq-broker release without TLS. Now when we configure self signed certs on rabbitmq nodes which has the following details, cn = rabbitmq node-1 ip sn = rabbitmq node-1 ip, rabbitmq node-2 ip
We are using rabbit-example-app to test it with TLS https://github.com/pivotal-cf/rabbit-example-app.git
When we put the client and server certs same as the certs configured on the nodes it gives us following error,
"Connection to amqps://***@10.x.x.x failed to start hostname haproxy-ip does not match server certificate"
We are using the following release versions, cf-multitentant-rabbitmq-broker - v49 cf-rabbitmq-release - v265