What causes 'The specified account does not exist.' error message in Azure Blob Storage?

Question

We have an Apache server running as a proxy for Azure blob storage.

However, there are some occasions where we get the following error:

HTTP/1.1 404 The specified account does not exist.

This happens occasionally/randomly and only when we fetch the blobs through the Apache proxy. If we fetch the blobs directly from the azure blob url, it works just fine.

We're trying to figure out why this happens - in order to do that, we're trying to figure out what triggers the above error.

This is the command we're using to reproduce it:

curl -IXGET https://<account-storage>.blob.core.windows.net/<container>/<blob-path>

What's the criteria for getting the error The specified account does not exist? What do we need to do to the above command?

A few things we've tried: **

-** We tried modifying the <account-storage> to anything and we get:

curl: (6) Could not resolve host: <modified-account-storage>.blob.core.windows.net

• We tried modifying the <container> and we get:

HTTP/1.1 404 The specified resource does not exist.

• We tried modifying the <blob-path> and we get:

HTTP/1.1 404 The specified blob does not exist.

None of these match the error we're trying to reproduce.

Answer 1

Germán José Aguilera

I understand that you are encountering a "404 The specified blob does not exist" error intermittently while retrieving blobs via the Apache proxy.

This issue may be due to Authentication or incorrect URL problems.

Here are the few things you need to check:

• In the case of an Azure Data Lake storage account configured with an Azure network private endpoint, I suggest configuring the private endpoint for both blob and DFS endpoints.
• https://learn.microsoft.com/en-us/azure/storage/common/storage-private-endpoints#creating-a-private-endpoint
• Ensure that Azure storage blob data contributor permissions are granted for the authentication account or service principal.
• https://learn.microsoft.com/en-us/azure/storage/blobs/assign-azure-role-data-access?tabs=portal#assign-an-azure-role
• If the issue persists, I recommend enabling Azure Storage diagnostics logs. Reproduce the problem, and carefully analyze the logs for additional insights.

If you need further assistance or clarification on any of the outlined steps, please don't hesitate to reach out and we would be happy to assist you.