When we test plugin with our service api locally everything works fine. but when we deploy our bits into azure (aks with ingress and azure application gateway) and try to add the plugin into store, we got the got 404 with Plugin not found error message via this request (https://chat.openai.com/backend-api/aip/p/domain?domain=ourservicedomain).
Here are the logs in our side, it seems calling the open api document via HEAD method and GET method.
As you can see from the attached image above, the HEAD request got 404 and GET request got 200. Can anyone help us understand or debug what the reason(s ) can cause the issue above? Is that because the HEAD request return as 404?
A few general things to check:
If you’re using a reverse proxy or a web application firewall, ensure it’s correctly forwarding HEAD requests.
Check your AKS Ingress configurations, in some cases, ingress controllers can behave differently based on the type of request. Make sure your ingress configurations covers HEAD.
Also worth checking that your Azure Application Gateway is not potentially be the cause. Check its configuration to ensure it’s not blocking or improperly routing HEAD requests.
Thanks for the help. I did check the ingress and azure application gateway, both accept HEAD. I think the issue is that we use ASP.NET Core web API documentation with Swagger / OpenAPI | Microsoft Learn to generate the Open AI document rather than a physical file, so it doesn’t support HEAD. Also fun fact, if I choose deploy as develop own plugin, then it worked.
I am using Swashbuckle command line to generate an open api physical file, deploying now and will let you know the result. But I would like to know the detail flow on how chatgpt discovery plugin via this request (https://chat.openai.com/backend-api/aip/p/domain?domain=ourservicedomain).
Update on this thread
It worked when use as physical file for unverified plugin option.
