AzureStorageExplorer icon indicating copy to clipboard operation
AzureStorageExplorer copied to clipboard

Electron Net Error

Open nasia7 opened this issue 6 months ago • 2 comments

Storage Explorer Version

1.37.0

Regression From

No response

Architecture

x64

Storage Explorer Build Number

No response

Platform

All

OS Version

Windows 10

Bug Description

无法检索子资源

ProducerError:{ "name": "Electron Net Error", "message": "{"name":"Electron Net Error","cause":{}}" }

Steps to Reproduce

  1. Open Storage Explorer.
  2. Click a blob container node.

Remark: try to reset function and logged in again, still have the same issue.

Actual Experience

Show the follow content:

无法检索子资源

ProducerError:{ "name": "Electron Net Error", "message": "{"name":"Electron Net Error","cause":{}}" }

Expected Experience

No response

Additional Context

No response

nasia7 avatar May 25 '25 00:05 nasia7

I'm experiencing the same:

Windows 11, Storage Explorer 1.38.0 (105)

I have the azurite container running:

docker run -d --name azurite --restart unless-stopped -p 10000:10000 -p 10001:10001 -p 10002:10002 mcr.microsoft.com/azure-storage/azurite azurite --skipApiVersionCheck

When I expand "Blob Containers" under "devstoreaccount1 (azurite)" I get:

Unable to retrieve child resources

ProducerError:{
  "name": "Electron Net Error",
  "message": "{\"name\":\"Electron Net Error\",\"cause\":{}}"
}

I tried an uninstall and reinstall of storage explorer, and removing the azurite container + image, then rebuilding the container. Same error in the storage explorer.

Logs: 2025-05-27_094337.zip

mbursill avatar May 27 '25 16:05 mbursill

@nasia7

  • Please try updating to the latest version of Storage Explorer, then try again. Make sure you have at least .NET 8 installed.
  • Have you tried any of the troubleshooting steps?
  • How are you trying to connecting to the blob container (signed in or attaching)?
  • How are you authenticating (signing in, account name and key, SAS)?
  • If you are signing in, have you tried signing out and signing back in?
  • Have you tried uninstalling and reinstalling Storage Explorer?
  • Can you share your app logs?

@mbursill

  • I'm assuming your "devstoreaccount1" node shows as a Docker node, yes? If the emulator is running, do you see any console output from the emulator when you try to interact with the child nodes?
  • Does a manually created connection work?
  • Can you run Azurite directly (after stopping any other Azurite containers)? Can Storage Explorer connect to the directly run instance (default emulator node)?
  • Do you have anything else listening to the same ports (like other containers or instances)?

Interacting with Azurite is a completely separate issue from the original author's issue. If none of the above suggestions work, please open a new issue.

craxal avatar Jun 04 '25 16:06 craxal

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

craxal avatar Aug 12 '25 21:08 craxal