microsoft / microsoft/AzureStorageExplorer

Proxy issue

Open
#9,080 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

:computer: windows :electric_plug: connection reset :gear: proxy :grey_question: need logs
Dominant language
No language data
Stars
452
Forks
92
Avg merge
15h 20m
Merged PRs (30d)
3

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

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

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.

Assessment

Tech stack
azure
Domain
authentication, desktop, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.