Azure WAF Backend Health - Cert issue

Dave K 91 Reputation points
2020-05-25T20:06:47.71+00:00

When I'm trying to configure the WAF to reach my RDS Gateway, I'm getting the following error "The Common Name (CN) of the backend certificate does not match the host header entered in the health probe configuration. Either change the probe configuration or add a valid certificate on the backend".

The cert I installed on the gateway is a wildcard cert for my external domain, and have updated the external DNS to the Azure public IP. The external domain name differs from the internal name but surely this is a common situation. Also to confirm the wildcard cert installed is definitely the cert I wish to use. Its an externally signed cert for my external domain.

Also to mention I haven't configured any health probe so I presume the health probe mentioned is created by default with the gateway/waf. I have not changed any config on this.

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
7,872 questions
Azure Web Application Firewall
0 comments No comments
{count} votes

Accepted answer
  1. Andreas Baumgarten 108.8K Reputation points MVP
    2020-05-25T23:41:35.813+00:00

    The issue and how to get this fixed is described here:

    Troubleshoot backend health issues in Application Gateway

    Maybe this is helpful.

    Regards

    Andreas Baumgarten

    --please don't forget to Accept as answer if the reply is helpful--

    1 person found this answer helpful.
    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.