Share via

Failed to connect to management Endpoint...

Rob Wilson 47 Reputation points
2022-10-12T08:09:15.197+00:00

Hello. I've recently integrated API management inside a Vnet. I've built my Application gateway successfully, and heath probes for the portal, gateway and manager are showing healthy. I've configured DNS records for the Portal, Manager and API on GoDaddy to point to the public IP, and now following the link to the developer portal brings up this page as expected:

249596-image.png

This naturally leads me onto wishing to publish the developer portal. However on the Portal Overview plane, the option to publish the portal is greyed out and I'm seeing this:

249604-image.png

I've also having this error message popping up, which is obviously related:

249578-image.png

Any ideas? I'm fairly new to Azure so go easy with your technical answers haha. But any help would be massively welcome! :)

Azure API Management
Azure API Management
An Azure service that provides a hybrid, multi-cloud management platform for APIs.
2,239 questions
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,098 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. JananiRamesh-MSFT 29,191 Reputation points
    2022-10-12T15:28:48.4+00:00

    Hi @Anonymous Thanks for reaching out. I believe the issue could be due to self signed cert, verify if the management endpoint can be accessed via a browser without any certificate related warnings. From your machine, you can open a browser and navigate to https://servicename.management.azure-api.net/servicestatus (be sure to replace servicename.management.azure-api.net with your custom domain, if they have configured one). If you see any certificate related warnings while accessing this Url, then you will not be able to open Developer Portal on your machine as the browser will block calls to the management endpoint. To address this problem, you can either remove custom domain from the management endpoint (if possible) or alternately, address the problem with the certificate (it may be untrusted certificate) as it is self signed certificate. click on advanced in the warnings and allow. after that you will see 200 status.

    let me know if this resolves the issue else will connect offline to troubleshoot the same.

    Please 'Accept as answer' and ‘Upvote’ if it helped so that it can help others in the community looking for help on similar topics.

    1 person found this answer helpful.
  2. Ranjeet Singh 20 Reputation points
    2024-12-20T06:05:55.6366667+00:00

    Hi Rob, could you confirm that you have done the internal DNS update for below endpoint point them to the private IP of APIM gateway?

    Please refer this. When you access the APIM within subnet or internal network connected to your subnet via express route/(other option), your internal DNS should resolve your APIM domains to the private IP of gateway.

    https://zcusa.951200.xyz/en-us/azure/api-management/api-management-using-with-internal-vnet?tabs=stv2

    Endpoint Endpoint configuration
    API Gateway contosointernalvnet.azure-api.net
    API Gateway contosointernalvnet.azure-api.net
    Developer portal contosointernalvnet.portal.azure-api.net
    The new developer portal contosointernalvnet.developer.azure-api.net
    Direct management endpoint contosointernalvnet.management.azure-api.net
    Git contosointernalvnet.scm.azure-api.net

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.