Tried to fix - cant - your AI said to contact you - please see attached.
Works great - until it doesn’t.
Thank you
My workflow fails at the “Download Image” node when trying to fetch an image from OpenAI’s Azure Blob Storage. The URL is valid and accessible in my browser, but n8n Cloud returns a DNS error.
{
"name": "NodeApiError",
"message": "The connection cannot be established, this usually occurs due to an incorrect host (domain) value",
"stack": "NodeApiError: The connection cannot be established, this usually occurs due to an incorrect host (domain) value\n at ExecuteContext.execute ...",
"cause": {
"errno": -3008,
"code": "ENOTFOUND",
"syscall": "getaddrinfo",
"hostname": "oaidalleapiprodscus.blob.core.windows.net"
}
}
The image URL works in my browser.
I have retried multiple times.
This workflow usually works.
It sounds like it is an issue beyond your control so better raise a ticket. But a quick fix would be to avoid the image URL if possible. Request the image API to return a Base64 instead of a blob URL. This means in the request body you will have to set up response format to be base64. It will get the image encoded as text within a JSON so will always be a best practice to overcome potential DNS issues like what you are experiencing. Inside n8n for the conversion you will have to use a Move binary data node to handle the input.
Would you like to share the URL of the image, so that we could try. This could allow to differentiate between issues with the source vs issues with destination. Maybe a simple workflow example you would like to attach to showcase the issue?
This was quite some time ago it took a while to get my account unblocked I guess.
Since I have learned this is standard behavior for the node and you have to trim through hoops to get it off the URL in the next node.
It just seems like terrible functionality and that such a extremely common use case that it would be handled easily but the solution was not at hand. Thanks for your response
Thanks for your response. Apparently it’s expected behavior but for such a common extremely common use case seems it would be more apparent how to handle the blob.
N8n took some time getting my account set up so this was a few days ago I have since changed the following node.
Surprised a solution wasn’t available in this community It seems like such an extremely common use case. But oh well now it was days and days ago lol