Cannot get access to Blob Container

[OlgaNikolaevaKofax]

Preflight Checklist

• I have installed the latest version of Storage Explorer.
• I have checked existing resources, including the troubleshooting guide and the release notes.
• I have searched for similar issues.

Storage Explorer Version

1.32.1

Regression From

No response

Architecture

x64

Storage Explorer Build Number

20231114.10

Platform

Windows

OS Version

Windows 10

Bug Description

While trying to get access to Blob Container I always get same error:
Unable to retrieve child resources

ProducerError:{
"name": "Node Fetch Error",
"message": "getaddrinfo ENOTFOUND qatcstorage24char.blob.core.windows.net",
"stack": "Error: getaddrinfo ENOTFOUND qatcstorage24char.blob.core.windows.net\n at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:108:26)",
"cause": {
"cause": {
"errno": -3008,
"code": "ENOTFOUND",
"syscall": "getaddrinfo",
"hostname": "qatcstorage24char.blob.core.windows.net"
}
},
"code": "ENOTFOUND",
"errno": -3008
}

Steps to Reproduce

1. Launch Storage Explorer
2. Expand Blob container node

Actual Experience

Unable to retrieve child resources

ProducerError:{
"name": "Node Fetch Error",
"message": "getaddrinfo ENOTFOUND qatcstorage24char.blob.core.windows.net",
"stack": "Error: getaddrinfo ENOTFOUND qatcstorage24char.blob.core.windows.net\n at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:108:26)",
"cause": {
"cause": {
"errno": -3008,
"code": "ENOTFOUND",
"syscall": "getaddrinfo",
"hostname": "qatcstorage24char.blob.core.windows.net"
}
},
"code": "ENOTFOUND",
"errno": -3008
}

Expected Experience

I get access to blob container successfully

Additional Context

No response

[MRayermannMSFT]

@OlgaNikolaevaKofax is your storage account on a private virtual network? If so, is your current machine on that network? As a quick test, can you try accessing the same container from the Azure Portal, using the same machine as you are running Storage Explorer?

[MRayermannMSFT]

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.