Hello, working on exposing am internal load balancer through an app gw v2. My listener continues to default to the wrong certificate, so when I open the host name on the browser it depicts the wrong certificate.

EDWARD REYESARROYO 25 Reputation points
2024-07-18T01:15:08.62+00:00

-Double check settings as in hostname, correct wildcard attached to our listener.

-Error: The Common Name of the leaf certificate presented by the backend server does not match the Probe or Backend Setting hostname of the application gateway.

-When attempting to open the site shows insecure and the certificate information points to out gitlab solution versus the desired load balancer....

Please advice if I should add more details.

Azure Application Gateway
Azure Application Gateway
An Azure service that provides a platform-managed, scalable, and highly available application delivery controller as a service.
1,079 questions
Azure Load Balancer
Azure Load Balancer
An Azure service that delivers high availability and network performance to applications.
451 questions
{count} votes

1 answer

Sort by: Most helpful
  1. KapilAnanth-MSFT 46,776 Reputation points Microsoft Employee
    2024-07-18T08:39:33.1833333+00:00

    @EDWARD REYESARROYO ,

    Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

    From your verbatim, you are trying to add an ILB as the backend of an App gateway and this appears to be a new setup altogether.

    • If you bypass the Application Gateway, and directly access the ILB from a VM, does this work?
    • Do you use any domain on the ILB or just access it like https://<PrivateIpOfILB>:443 ?
    • What is the hostname you are configuring in the Application Gateway BackendHTTPSettings ?
      • If you are using a custom Probe, what are the values used ?

    Cheers,

    Kapil


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.