Unable to access the UAT File Shares with Timeout error

[ppabayat]

Storage Explorer Version

1.38.0

Regression From

No response

Architecture

x64

Storage Explorer Build Number

20250408.1

Platform

Windows

OS Version

Windows 11 Enterprise

Bug Description

The file shares are not loading for the below storage account: Name: f0b1e5a5593b64d2cb12a8a Key: REDACTED

Note: Other file shares are loading without an issue.

Steps to Reproduce

1. Launch the storage explorer
2. Click the above mentioned Storage account and click the File Shares drop down

Actual Experience

The drop down keeps loading and then time out error comes.

Expected Experience

File shares should be loaded and able to be accessed

Additional Context

Error Message:

Unable to retrieve child resources

ProducerError:{ "name": "Electron Net Error", "message": "net::ERR_CONNECTION_TIMED_OUT", "stack": "Error: net::ERR_CONNECTION_TIMED_OUT\n at SimpleURLLoaderWrapper. (node:electron/js2c/browser_init:2:118774)\n at SimpleURLLoaderWrapper.emit (node:events:518:28)", "cause": {} }

[ppabayat]

[ppabayat]

Hello, This is currently a blocker for our testing. Any support please? Thank you.

[craxal]

@ppabayat Please do not share sensitive information such as account keys here. They are viewable by the public and can be used by anyone to access your data. I would strongly recommend rotating your account keys now to prevent unauthorized access.

The error appears to be associated with an account called "LCP UAT" and not "f0b1e5a5593b64d2cb12a8a" as you mentioned above. Can you clarify?

Based on your screenshot, it appears that you are attaching via account key. Does the storage account allow authenticating using storage keys? Are there any security or network configurations on the storage account that might restrict connections? Are you attempting to connect through a proxy?

[ppabayat]

Hello @craxal, 'LCP UAT' is just the display name of the storage to identify easily but the actual name is "f0b1e5a5593b64d2cb12a8a". We are only allowed to authenticate via keys.

Please note that this is an issue facing by all my team mates and not an individual. It worked fine until 3rd of June and started getting the timeout error only from the 4th. Also, it only happens to this storage account and the other storages that we authenticate similarly via keys are working fine.

[craxal]

@ppabayat Are you able to access the storage account using other tools such as Azure PowerShell or the Azure CLI? And again, are there any security or network configurations on the storage account that might restrict connections? Are you attempting to connect through a proxy?

[craxal]

Closing due to inactivity. If this still an issue, please reply with answers to the above questions, and we can revisit.