Easily manage the contents of your storage account with Azure Storage Explorer. Upload, download, and manage blobs, files, queues, tables, and Cosmos DB entities. Gain easy access to manage your virtual machine disks. Work with either Azure Resource Manager or classic storage accounts, plus manage and configure cross-origin resource sharing (CORS) rules.
Can you provide any more information about the error, such as screenshots, at what exact point the error was encountered, etc.?
Are you able to get a list of blob containers? Does the error occur when you try to view the blob container?
Have you made sure required components are installed and up-to-date (for example .NET 8)? Does uninstalling and reinstalling resolve the issue?
Are you trying to connect via a work machine and network connection or a private machine? If work, does your workplace expect connections through a proxy?
I am getting the same error. We have a few storage accounts, I can list the blob containers for all but one. When expanding "Blob Containers" for the one that wont open, there is a spinner, then "Error Details" dialog is displayed with the following detail:
This started happening after I copied a blob container from a different storage account. The output window indicated that the copy had completed normally.
I was able to access the blob containers via the portal, and deleted the one I had copied in, but storage explorer still wont list the blob containers.
And a couple more notes:
The blob containers list correctly in the portal, but when I try to expand the blob container it presents this:
{"shellProps":{"sessionId":"","extName":"Microsoft_Azure_Storage","contentName":"BlobsBlade","resourceId":"","code":0},"error":{"message":"Network request failed - cannot access storage endpoint","code":0,"details":{"htmlTemplate":"
","viewModel":{"causes":[{"details":"Your firewall settings may be preventing network access from this client to the storage data endpoint.","link":null},{"details":"CORS settings on your storage account may be preventing network access from this client.","link":null}]}}}}
The CORS configuration is identical to other storage accounts/blob containers that list correctly.
The application that depends on the blob container is still processing blobs normally
@KevinL3 Your application may have explicit authorization to access your resources. Has anyone modified network or security configurations for the resources you are trying to access? For example, do you know if public network access has been turned off or limited?
craxal
commented
1 month ago 
KevinL3
Preflight Checklist
Storage Explorer Version
1.34.0 (99)
Regression From
No response
Architecture
x64
Storage Explorer Build Number
No response
Platform
Windows
OS Version
WIndows 10
Bug Description
Unable to retrieve child resources
ProducerError:{ "name": "Node Fetch Error", "message": "{\"name\":\"Node Fetch Error\",\"cause\":{\"cause\":{\"code\":\"EACCES\"}},\"code\":\"EACCES\"}" }
Steps to Reproduce
Launch Storage Explorer Login with email address Expand a blob container node
Actual Experience
Unable to retrieve child resources
ProducerError:{ "name": "Node Fetch Error", "message": "{\"name\":\"Node Fetch Error\",\"cause\":{\"cause\":{\"code\":\"EACCES\"}},\"code\":\"EACCES\"}" }
Expected Experience
No response
Additional Context
No response