1

I have a .NET Core Web API hosted in Azure App Service, with API Management in front of it.

I have added the IP of API Management to be allowed in inbound traffic to my App Service: enter image description here

If i send a request without a subscription key to the API Management endpoint i get

{
    "statusCode": 401,
    "message": "Access denied due to missing subscription key. Make sure to include subscription key when making requests to an API."
}

When i add subscription key and send request through postman, it will just be infinitely loading unless i set a timeout.

I can send requests directly to the App Service endpoint url (by temporarily adding my IP to allowed IP addresses in network settings) and it works perfectly fine, and when i check logstream i can see logs that my request was successfully handled in my middleware. enter image description here

But when i send requests to the API Management endpoint, there are no logs in the App Service logstream from my middleware. enter image description here

When i check the logs in API Management i find this error, which doesn't help me much: enter image description here

Any idea what could cause this? Maybe i've done something wrong with how i've set up App Service / API Management.

Albin Cederblad
  • 175
  • 1
  • 11
  • Have you checked these similar issues? [API management service ClientConnectionFailure at forward-request](https://stackoverflow.com/questions/56862256/api-management-service-clientconnectionfailure-at-forward-request), [ClientConnectionFailure at forward-request](https://stackoverflow.com/questions/64705819/clientconnectionfailure-at-forward-request) and [APIM: Intermittent ClientConnectionFailure at forward-request](https://learn.microsoft.com/en-us/answers/questions/747999/apim-intermittent-clientconnectionfailure-at-forwa.html) – Ecstasy Apr 08 '22 at 04:13
  • [forward request - how to increase the default timeout](https://github.com/MicrosoftDocs/azure-docs/issues/52667) – Ecstasy Apr 08 '22 at 04:13
  • Yes, i have checked out those twice, nothing helpful there. It isn't a problem with increasing timeout, i could wait 2 weeks for a response it wouldn't come. – Albin Cederblad Apr 10 '22 at 17:26

1 Answers1

1

Ugh, found the mistake. I had accidentally set the "Web service URL" in API Management settings to the API Management URL instead of the App service URL, so it was essentially trying to send requests to itself, perhaps resulting in an endless loop.

Albin Cederblad
  • 175
  • 1
  • 11