I have deployed APIM self hosted GW to AKS and it is up and running this gateway got exposed using ingress I create my API with self hosted GW and I would expect to call my it and get routed to beta svc in demo namespace but I get 404 instead (even whil trying inside APIM portal) What do I do wrong? Do I need to configure the GW exposed IP somewhere? When I click on "Trace" I just get this empty screen: Please help, i am lost

@David Macháček Thanks for getting back, this will not work from portal test console as i see from the screenshot that you're making a call to http://sgc-apim-prem.azure-api.net/request the host name gc-apim-prem.azure-api.net will resolve to Ip address of your APIM instance. Can you please try with postman as below with AKS ip address. By this way you can verify that the self-hosted gateway is configured correctly, and that the API is accessible through the SHG. do let me know incase of further queries, I would be happy to assist you.

Api managament self hosted gateway returns 404

David Macháček 25

I have deployed APIM self hosted GW to AKS and it is up and running User's image

this gateway got exposed using ingress User's image

I create my API with self hosted GW and I would expect to call my it and get routed to beta svc in demo namespace
User's image

but I get 404 instead (even whil trying inside APIM portal) User's image

What do I do wrong? Do I need to configure the GW exposed IP somewhere? When I click on "Trace" I just get this empty screen: User's image

Please help, i am lost

JananiRamesh-MSFT 28,716 Reputation points

2024-03-01T07:15:49.21+00:00

@David Macháček Thanks for reaching out. Could you please verify if you had linked the API to the Self-hosted Gateway from Azure Portal -> APIM -> API -> Settings as shown below,

do let me know incase of further queries, I would be happy to assist you.
David Macháček 25 Reputation points

2024-03-01T07:38:49.5+00:00

Yes, I did that. If I keep the managed gateway I get 200 and everything is ok, but when I set the self hosted gw (called private-gw) as shown in picture below I get the behavior described in this post (404 ERROR) and nothing works
JananiRamesh-MSFT 28,716 Reputation points

2024-03-01T07:52:49.5933333+00:00

@David Macháček can you also Ensure that the URL schema supports the current API call from Azure Portal > APIM > API > Settings.
David Macháček 25 Reputation points

2024-03-01T08:14:44.48+00:00

I did try all the 3 schema types (HTTP, HTTPS, and HTTP(s)). Also I think if there was an error in schema, the calls would not work with managed gateway either. But the problem is, that everything works with managed gateway, but when i swiitch to self hosted one i get 404
David Macháček 25 Reputation points

2024-03-01T08:15:42.9966667+00:00

also all the logs from self hosted gw look okay, they seem retrieving all the configuration updates, i.e.
JananiRamesh-MSFT 28,716 Reputation points

2024-03-04T17:28:58.9433333+00:00

@David Macháček Please Accept the answer if the information helped you. Accepting answers will help increase the visibility of this question and the solution for anyone else who may run into the same issue. Thank you for helping to improve Microsoft Q&A!
SKT 146 Reputation points

2024-05-14T04:51:18.64+00:00

Hi there,

I have exactly the same issue with a self hosted gateway. The backend API is via a firewall, so I'm doing a packet sniff there, and see zero traffic when test an operation (the api gateway is not even trying the operation so the 404 error is confusing/wrong). What did you do to solve this? I can't understand the MSFT answer.

Accepted answer

JananiRamesh-MSFT 28,716 Reputation points

2024-03-01T10:37:15.2233333+00:00

@David Macháček Thanks for getting back, this will not work from portal test console as i see from the screenshot that you're making a call to http://sgc-apim-prem.azure-api.net/request the host name gc-apim-prem.azure-api.net will resolve to Ip address of your APIM instance. Can you please try with postman as below with AKS ip address.

By this way you can verify that the self-hosted gateway is configured correctly, and that the API is accessible through the SHG.

do let me know incase of further queries, I would be happy to assist you.
Please sign in to rate this answer.
David Macháček 25 Reputation points

2024-03-01T11:10:40.7+00:00

you are right! thanks very much for help. You cannot use APIM hostname for calls when the self-hosted GW is used!

JananiRamesh-MSFT 28,716 Reputation points

2024-03-02T16:46:55.53+00:00

David Macháček Thanks for your response. I have converted my comment to answer. Feel free to Accept as Answer and Upvote so it can help other community members facing the similar issue.

SKT 146 Reputation points

2024-05-14T04:52:09.3566667+00:00

Hi there,

I have exactly the same issue with a self hosted gateway. The backend API is via a firewall, so I'm doing a packet sniff there, and see zero traffic when I test an operation (the api gateway is not even trying the operation so the 404 error is confusing/wrong). What did you do to solve this?
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Api managament self hosted gateway returns 404

0 additional answers

Your answer