We're using Zendesk's Secure Settings feature, but it fails in error, "Proxy error: DNS resolution error". The domain is subdomain of openai.azure.com, like oursubdomain.openai.azure.com.
- secure:true in ZAFClient request options
- set "domainWhitelist" in manifest.json
- without secure:true option, it works. This means the subdomain and parameters are correct.
- installed the app as private app
What can we do next to solve this error?
Hi Megumi! Do you have CORS set to false in your request options? If you do, could you share the full request snippet, along with the options?
Hi Greg, thank you for the comment.
I tried with `cors: false`, but it also failed in the same DNS error. This is the request I am using.
var params = {...};
var headers = {
'Content-Type': 'application/json',
'api-key': '...',
};
var settings = {
url: 'https://....openai.azure.com/openai/...,
contentType: 'application/json',
secure: true,
cors: false,
type: 'POST',
headers: headers,
data: JSON.stringify(params),
};
return client.request(settings)...The "api-key" param is `{{setting.api_key}}` (api_key param is in the parameters of manifest.json), but I tried both with the raw value and `{{setting.api_key}}`.
If I remove the line "cors: false" (means use only secure:true), this failed in DNS error.
If I remove the line "secure: true" and use api-key with raw value (means use only cors:false), this request works.
Can you find something?
Hi Greg, thank you for the update :)
Hi Greg, Thank you for information.
This investigation is for our customer and the customer has asked to support in ticket 11779265. The business impact of this issue is as described in the ticket.
And thank you for about workaround. I hope this issue fixed, but if we need to implement before that, I consider the workaround.
thank you!
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
dig +trace e...openai.azure.comor on Windowsnslookup -debug e...openai.azure.com, you'll see the full resolution path.Since this is working when you're not passing it through our proxy (by removing
secure: true), I'm assuming that there is something deeper that occurs on this particular path, so I'm going to bring my findings to that team to hear what they have to say. I'll drop you a line when I hear back from them, hopefully later this week.