Proxy issue
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- azure
- Domain
- authentication, desktop, networking
Research direction
Start by launching Azure Storage Explorer on Windows, opening the proxy settings from the toolbar, and attempting account reauthentication. Compare the reported proxy failure and ECONNRESET details with the stated 1.41.1 build; done means identifying a reproducible application problem and documenting a verified resolution or the conditions under which it occurs.
Written by the indexing model from the issue text.
Description
Storage Explorer Version
1.41.1
Regression From
No response
Architecture
x64
Storage Explorer Build Number
20260214.2
Platform
Windows
OS Version
No response
Bug Description
On open Azure Storage Explorer I get this message:
Unable to establish connection using current proxy settings. Please verify current settings by accessing the proxy dialog in the toolbar.
And then when I try to Reauthenticate my account I get this message:
{
"name": null,
"message": ""{\n \"name\": \"Node Fetch Error\",\n \"message\": \"read ECONNRESET\",\n \"stack\": \"Error: read ECONNRESET\\n at TLSWrap.onStreamRead (node:internal/stream_base_commons:216:20)\",\n \"cause\": {},\n \"code\": \"ECONNRESET\",\n \"errno\": -4077\n}""
}
I have tried changing proxy settings, rebooting modem and router, etc. and nothing helps. I noticed users had similar issues in 2024 and 2023 that were fixed after a new build, do I just need to wait for an update?
Resource Types
No response
Authentication Method
Account name and key
Connection Type
Sign in (subscription)
Steps to Reproduce
Launch Storage Explorer
Attempt to change Proxy Settings
Actual Experience
Bug described above occurs every time
Expected Experience
No response
Additional Context
No response
- Dominant language
- No language data
- Stars
- 455
- Forks
- 92
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/AzureStorageExplorer
-
:beetle: regression :copilot: copilot :test_tube: testing
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
microsoft/AzureStorageExplorer#9191 · 1 comment ·
-
Difficulty 2/5 1-2 days Newbie friendliness 76/100
microsoft/AzureStorageExplorer#9186 ·
-
:globe_with_meridians: hard-coded string :globe_with_meridians: localization :test_tube: testing
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/AzureStorageExplorer#9152 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
microsoft/AzureStorageExplorer#9207 ·
-
Sign-in errorOpen
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/AzureStorageExplorer#9206 · 4 comments · 1 reaction ·
All issues in microsoft/AzureStorageExplorer
Similar issues
-
cosh prompt_scanner_hook.py crashes with AttributeError on a non-object JSON payload (every sibling hook guards this)Possibly taken @zjncs claimed this today. Opencomponent:cosh
Difficulty 1/5 Under an hour Newbie friendliness 92/100
agentic-os-org/ANOLISA#6114 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Uuriko/project-room#1523 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Gentleman-Programming/gentle-ai#5280 ·
Maintainers usually reply within 1 day
-
The shim's mount reader runs awk in the caller's locale, so its answer can differ from the sh reader'sPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
FluidNumerics/fluid-walk-blocker#162 ·
Maintainers usually reply within 1 day
-
fix(security): dependency-pinning misses list-item run steps and npm options before installPossibly taken @MohammedAlkindi claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day