-
Notifications
You must be signed in to change notification settings - Fork 21.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DALL-E API 404 Resrouce Not Found #111250
Comments
@alvinvinalon |
Hi there. I have fixed the issue. It's with the GET for the image generated that's stored in the storage blob. A mistakenly thought the 'operation-location' is the region and replaced it with 'eastus'. I reverted it back to 'operation-location' and it's working fine now. Thanks. |
We are going to close this thread.if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation. |
It appears that we are encountering an issue with the current version of the OpenAI library, which is not functioning as expected in our environment. A potential workaround for this problem is to make a direct REST API request to OpenAI’s service. This approach would allow us to have more granular control over the communication with the service and bypass the limitations we are experiencing with the library.
|
[Enter feedback here]
I followed the steps written here (REST) and have confirmed both api-base and api-key are correct multiple times.
But when I run my python app, I get a 404 resource not found error.
I also tried the Python (Openai module) steps, and got a Resource Not Found issue too.
Our DALL-E instance is currently deployed in EAST US and I can successfully generate an image using the Azure OpenAI Studio.
I tested the REST API call in Postman and I get a 202 response with the following response:
{"id":"cf5e4e51-xxxx-xxxx-xxxx-193e338cdf4a","status":"notRunning"}
Is there anything I may have missed when using the DALL-E API in python? Cheers.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: