AzureStorageExplorer
AzureStorageExplorer copied to clipboard
microsoft
unable to expand azure storage in explorer
Preflight Checklist
- [X] I have installed the latest version of Storage Explorer.
- [X] I have checked existing resources, including the troubleshooting guide and the release notes.
- [X] I have searched for similar issues.
Storage Explorer Version
10.20.1
Regression From
No response
Architecture
i86
Storage Explorer Build Number
No response
Platform
All
OS Version
Windows server 2019
Bug Description
Unable to retrieve child resources
ProducerError:{ "name": "Node Fetch Error", "message": "getaddrinfo ENOTFOUND stcazurefiles01.file.core.windows.net", "stack": "Error: getaddrinfo ENOTFOUND stcazurefiles01.file.core.windows.net\n at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:108:26)", "cause": { "cause": { "errno": -3008, "code": "ENOTFOUND", "syscall": "getaddrinfo", "hostname": "stcazurefiles01.file.core.windows.net" } }, "code": "ENOTFOUND", "errno": -3008 }
Steps to Reproduce
Actual Experience
Expected Experience
No response
Additional Context
No response
@handasunny I'm going to assume you are accessing this storage account after signing in, and listing all the accounts under a subscription. Please let me know if that isn't the case.
With that assumption in mind, I will also assume that Azure is not returning a bogus storage account/is not giving us the wrong files endpoint for the account. So in that case, what is likely the issue here is that the vnet/firewall settings on the account are configured in such a way that the machine you are on does not have access to the storage account (at least not over the storage data plane).
Can you start a conversation with the owner of this account, and work with them to look at the vnet/firewall settings of the account, and see if y'all can determine why your machine can't access it?
Finally, as an immediate troubleshooting step, I would recommend enabling system proxy in Storage Explorer. To do that, go to Settings (gear on the left) > Application > Proxy > change the dropdown to be "system proxy".
Closing due to lack of response. This issue will no longer be monitored. If you need further help, we recommend opening a support ticket via the Azure portal. Alternatively you can open a new issue here.