New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Accessing a File Share on a Storage Account with an app specific proxy results in a timeout issue #4930
Comments
I was able to get our teams to install 1.20.1 and the issue is not present in that version. I am able to browse to the File Share as expected and I can see the traffic on the proxy. |
I'm not able to reproduce when using Fiddler as a proxy on my machine. Can you please share your log files with us for both "main" and "se-file-extension"? You can find the log files by selecting Help > Open Logs Directory from the menu. Is it possible to use system proxy settings or environment variables? Does this problem reproduce if you try those options? Another thing you can do:
|
Thanks craxal, Is it possible that your fiddler is working because it is listening locally on 3128 and the error indicates that it is trying to connect to 127.0.0.1:3128 - thus would work with a local fiddler that is listening on 127.0.0.1? Have you tried with an external proxy - squid should be about 20mins of work to get running on another machine or maybe fiddler listening on another machine?
|
@soloji Can you also provide the logs for the "se-file-extension" process? Since the problem you're having is with file shares, that may be more informative. Have you also confirmed that you are using the correct protocol, username, and password? If your OS is already configured to go through the same proxy, it may be easier for you to change Storage Explorer's settings to "Use system proxy". I will try setting up a real proxy on my end and see if I can reproduce the issue. To confirm, what kind of authentication does your proxy server use? |
@craxal this will not work, file share features are not onboarded to system proxy at this time. |
@soloji FYI, I've been wrestling with Squid and other proxy options for a while but have not been successful in getting anything to work except Fiddler locally, let alone get Storage Explorer to work with it. I mentioned it before, but I want to make sure. The log files seem to indicate that you have a username and password, but "Use credentials" is turned off. Assuming your proxy uses Basic authentication, does your proxy expect a username and password? Are there any other resource types or areas where proxy isn't working (such as Queues or Tables)? |
@craxal Good morning, thanks for trying to reproduce! I will get the logs of the file that you requested shortly |
Two findings this morning
|
@soloji Thanks for the info. I was able to reproduce the same behavior using a simple Node script to act as a proxy on a different machine. Blobs and Queues work, but Files and Tables do not. The key difference is we use different SDK versions, and so setting up the proxy is different for each version. Since you say it doesn't reproduce in 1.20.1, can you follow the same steps above involving the dev tools with that version? I'm curious to see if the proxy value is different between versions. |
I think I found the problem. In 1.21.0, we changed just a little bit how we pass app proxy settings to the File and Table clients. However, the SDK documentation was misleading, so we ended up passing the settings in the wrong format. Not entirely sure why this error is only apparent when working with a non-local proxy, but I tested the fix, and it seems to be working. @soloji Would you like to try out a private build to see if the change fixes your issue? |
@craxal great news! I always think that once an expert can reproduce, the fix is not far away would be happy to test, might take a business day or two as I need to get things whitelisted but I should be able to test by early next week. |
@craxal I have installed the build you provided and the file and table function is working with our proxy. |
Preflight Checklist
Storage Explorer Version
1.21.0
Regression From
1.10.1
Architecture
i86
Storage Explorer Build Number
20210908.7
Platform
Windows
OS Version
Windows 10 Enterprise 1909
Bug Description
File Share doesn't seem to uses the application specified proxy.
We have specified an app specific proxy for Azure Storage Explorer but when attempting to browse to the "File Share" of an account the access times out with the image below.
In the old version we would see traffic on the proxy server when opening File Shares such as
.file.core.windows.net:443.
However in this version we see no traffic attempting to reach the specified proxy.
Steps to Reproduce
Actual Experience
When attempting to open File Shares I get the following error that seems to indicate that traffic is not being direct to the specified proxy
Expected Experience
Able to open the File Share when using a application specific proxy
Additional Context
This is a major jump in version for our organisation 1.10.1 to 1.21.0 and I appreciated this might of broken in much earlier versions.
The text was updated successfully, but these errors were encountered: