Azure Storage Explorer troubleshooting guide

  • Commodity
  • 25 minutes to read

Microsoft Azure Storage Explorer is a standalone app that makes it easy to work with Azure Storage data on Windows, macOS, and Linux. The app can connect to storage accounts hosted on Azure, national clouds, and Azure Stack.

This guide summarizes solutions for issues that are commonly seen in Storage Explorer.

Azure RBAC permissions bug

Azure office-based access control (Azure RBAC) enables highly granular access management of Azure resources by combining sets of permissions into roles. Here are some strategies to get Azure RBAC working optimally in Storage Explorer.

How do I access my resources in Storage Explorer?

If you're having problems accessing storage resources through Azure RBAC, you might not have been assigned the appropriate roles. The following sections describe the permissions Storage Explorer currently requires for access to your storage resources. Contact your Azure account admin if yous're non sure y'all have the advisable roles or permissions.

"Read: Listing/Become Storage Account(s)" permissions issue

You must accept permission to list storage accounts. To get this permission, you must exist assigned the Reader office.

List storage account keys

Storage Explorer can also use account keys to authenticate requests. You lot tin can get access to business relationship keys through more powerful roles, such as the Contributor role.

Note

Access keys grant unrestricted permissions to anyone who holds them. Equally a result, nosotros don't recommend that yous manus out these keys to account users. If you need to revoke access keys, y'all can regenerate them from the Azure portal.

Data roles

You must exist assigned at to the lowest degree i office that grants admission to read data from resources. For example, if you want to list or download blobs, y'all'll need at least the Storage Blob Information Reader role.

Why do I need a management layer office to see my resource in Storage Explorer?

Azure Storage has 2 layers of access: management and information. Subscriptions and storage accounts are accessed through the management layer. Containers, blobs, and other data resources are accessed through the data layer. For example, if you desire to get a list of your storage accounts from Azure, y'all ship a request to the direction endpoint. If y'all want a list of blob containers in an account, you send a request to the appropriate service endpoint.

Azure roles can grant you permissions for management or data layer access. The Reader office, for example, grants read-only access to management layer resource.

Strictly speaking, the Reader function provides no data layer permissions and isn't necessary for accessing the data layer.

Storage Explorer makes it easy to access your resource by gathering the necessary data to connect to your Azure resources. For instance, to display your blob containers, Storage Explorer sends a "listing containers" request to the blob service endpoint. To get that endpoint, Storage Explorer searches the listing of subscriptions and storage accounts you lot have admission to. To find your subscriptions and storage accounts, Storage Explorer likewise needs access to the management layer.

If yous don't have a role that grants whatsoever management layer permissions, Storage Explorer tin't become the data information technology needs to connect to the information layer.

What if I can't get the management layer permissions I need from my admin?

If you want to access blob containers, Azure Data Lake Storage Gen2 containers or directories, or queues, you tin can adhere to those resources past using your Azure credentials.

  1. Open the Connect dialog.
  2. Select the resource blazon you want to connect to.
  3. Select Sign in using Azure Agile Directory (Azure Advertizing) and select Next.
  4. Select the user account and tenant associated with the resource you're attaching to. Select Next.
  5. Enter the URL to the resource, and enter a unique brandish proper noun for the connection. Select Next and and so select Connect.

For other resource types, we don't currently take an Azure RBAC-related solution. As a workaround, you can request a shared admission signature URL and then attach to your resources:

  1. Open the Connect dialog.
  2. Select the resource type you want to connect to.
  3. Select Shared access signature (SAS) and select Adjacent.
  4. Enter the shared access signature URL you received and enter a unique display name for the connection. Select Adjacent and so select Connect.

For more information on how to attach to resource, see Attach to an private resource.

There are several Azure built-in roles that can provide the permissions needed to utilize Storage Explorer. Some of those roles are:

  • Owner: Manage everything, including access to resources.
  • Contributor: Manage everything, excluding access to resources.
  • Reader: Read and list resources.
  • Storage Business relationship Contributor: Full management of storage accounts.
  • Storage Blob Information Owner: Full access to Azure Storage blob containers and data.
  • Storage Blob Data Contributor: Read, write, and delete Azure Storage containers and blobs.
  • Storage Blob Data Reader: Read and list Azure Storage containers and blobs.

Annotation

The Possessor, Contributor, and Storage Account Contributor roles grant business relationship cardinal access.

SSL certificate problems

This section discusses SSL certificate bug.

Understand SSL certificate problems

Make sure you've read the SSL certificates section in the Storage Explorer networking documentation earlier yous go along.

Use system proxy

If you're only using features that support the apply organisation proxy setting, try using that setting. To read more well-nigh the system proxy setting, see Network connections in Storage Explorer.

Import SSL certificates

If you have a copy of the self-signed certificates, you can instruct Storage Explorer to trust them:

  1. Obtain a Base-64 encoded Ten.509 (.cer) copy of the document.
  2. Get to Edit > SSL Certificates > Import Certificates. And so use the file picker to detect, select, and open the .cer file.

This upshot might also occur if in that location are multiple certificates (root and intermediate). To fix this error, all certificates must exist imported.

Detect SSL certificates

If you don't have a copy of the self-signed certificates, talk to your It admin for help.

Follow these steps to find them:

  1. Install OpenSSL:

    • Windows: Any of the light versions should be sufficient.
    • Mac and Linux: Should be included with your operating organisation.

  2. Run OpenSSL:

    • Windows: Open the installation directory, select /bin/, and then double-click openssl.exe.
    • Mac and Linux: Run openssl from a terminal.

  3. Run the command openssl s_client -showcerts -connect <hostname>:443 for any of the Microsoft or Azure host names that your storage resources are behind. For more data, see this listing of host names that are frequently accessed past Storage Explorer.

  4. Look for self-signed certificates. If the subject ("southward:") and issuer ("i:") are the same, the certificate is most likely cocky-signed.

  5. When you notice the self-signed certificates, for each one, re-create and paste everything from, and including, -----Brainstorm Document----- to -----END Certificate----- into a new .cer file.

  6. Open Storage Explorer and go to Edit > SSL Certificates > Import Certificates. Then use the file picker to observe, select, and open the .cer files you created.

Disable SSL certificate validation

If y'all tin't discover any cocky-signed certificates by following these steps, contact united states through the feedback tool. You lot can likewise open up Storage Explorer from the command line with the --ignore-certificate-errors flag. When opened with this flag, Storage Explorer ignores certificate errors. This flag is non recommended.

Sign-in issues

This section discusses sign-in issues you might encounter.

Sympathise sign-in

Make sure you've read the Sign in to Storage Explorer documentation before you continue.

Often having to reenter credentials

Having to reenter credentials is virtually probable the result of Conditional Admission policies gear up by your Azure Active Directory (Azure Advertisement) admin. When Storage Explorer asks you to reenter credentials from the account panel, you should see an Error details link. Select it to see why Storage Explorer is asking you to reenter credentials. Conditional Access policy errors that require reentering of credentials might look something like these:

  • The refresh token has expired.
  • You must use multifactor authentication to access.
  • Your admin made a configuration change.

To reduce the frequency of having to reenter credentials because of errors like the preceding ones, you lot'll need to talk to your Azure AD admin.

Provisional access policies

If yous accept provisional admission policies that need to be satisfied for your business relationship, make sure you're using the Default Web Browser value for the Sign in with setting. For information on that setting, see Changing where sign-in happens.

Browser complains about HTTP redirect or insecure connection during sign-in

When Storage Explorer performs sign-in in your web browser, a redirect to localhost is done at the end of the sign-in process. Browsers sometimes raise a warning or mistake that the redirect is being performed with HTTP instead of HTTPS. Some browsers might too endeavor to force the redirect to be performed with HTTPS. If either of these issues happen, depending on your browser, you have options:

  • Ignore the warning.
  • Add an exception for localhost.
  • Disable force HTTPS, either globally or just for localhost.

If you can't do any of those options, you lot can also alter where sign-in happens to integrated sign-in to avert using your browser altogether.

Unable to learn token, tenant is filtered out

If yous see an mistake message that says a token tin't be acquired because a tenant is filtered out, you're trying to admission a resource that's in a tenant you filtered out. To unfilter the tenant, go to the Business relationship Console. Brand certain the checkbox for the tenant specified in the fault is selected. For more information on filtering tenants in Storage Explorer, run across Managing accounts.

Authentication library failed to start properly

If on startup you lot run across an error message that says Storage Explorer's authentication library failed to starting time properly, brand certain your installation environs meets all prerequisites. Not meeting prerequisites is the most likely cause of this error message.

If you believe that your installation surround meets all prerequisites, open an issue on GitHub. When y'all open your effect, make sure to include:

  • Your Os.
  • What version of Storage Explorer you're trying to utilize.
  • If you checked the prerequisites.
  • Hallmark logs from an unsuccessful launch of Storage Explorer. Verbose authentication logging is automatically enabled after this type of error occurs.

Blank window when y'all apply integrated sign-in

If yous chose to use Integrated Sign-in and y'all're seeing a bare sign-in window, yous'll likely need to switch to a different sign-in method. Blank sign-in dialog boxes about often occur when an Active Directory Federation Services server prompts Storage Explorer to perform a redirect that'south unsupported by Electron.

To modify to a different sign-in method, change the Sign in with setting under Settings > Application > Sign-in. For information on the dissimilar types of sign-in methods, see Changing where sign in happens.

Reauthentication loop or UPN change

If you're in a reauthentication loop or take changed the UPN of 1 of your accounts, endeavour these steps:

  1. Open Storage Explorer.
  2. Go to Help > Reset.
  3. Make sure at least Hallmark is selected. Articulate other items you don't want to reset.
  4. Select Reset.
  5. Restart Storage Explorer and try to sign in once again.

If you proceed to have issues after you lot do a reset, effort these steps:

  1. Open Storage Explorer.
  2. Remove all accounts and and so close Storage Explorer.
  3. Delete the .IdentityService folder from your automobile. On Windows, the binder is located at C:\users\<username>\AppData\Local. For Mac and Linux, you can find the binder at the root of your user directory.
  4. If you're running Mac or Linux, you as well demand to delete the Microsoft.Developer.IdentityService entry from your operating organisation's keystore. On the Mac, the keystore is the Gnome Keychain awarding. In Linux, the application is typically chosen Keyring, merely the proper noun might differ depending on your distribution.
  5. Restart Storage Explorer and try to sign in again.

macOS: Keychain errors or no sign-in window

macOS Keychain tin can sometimes enter a state that causes issues for the Storage Explorer authentication library. To get Keychain out of this state:

  1. Shut Storage Explorer.

  2. Open up Keychain past selecting Command+Spacebar, enter keychain, and select Enter.

  3. Select the login keychain.

  4. Select the padlock to lock the keychain. Later on the process is finished, the padlock appears locked. Information technology might accept a few seconds, depending on what apps you lot take open.

    Screenshot that shows the padlock.

  5. Open Storage Explorer.

  6. You're prompted with a message like "Service hub wants to access the Keychain." Enter your Mac admin business relationship password and select Always Allow. Or select Allow if Always Allow isn't available.

  7. Try to sign in.

Default browser doesn't open

If your default browser doesn't open when you try to sign in, try all of the following techniques:

  • Restart Storage Explorer.
  • Open your browser manually before you first to sign in.
  • Try using Integrated Sign-In. For instructions, meet Changing where sign-in happens.

Other sign-in bug

If none of the preceding instructions apply to your sign-in issue or if they fail to resolve your sign-in upshot, open an event on GitHub.

Missing subscriptions and broken tenants

If you tin't retrieve your subscriptions subsequently you successfully sign in, try the following troubleshooting methods:

  • Verify that your business relationship has access to the subscriptions y'all await. You can verify your admission by signing in to the portal for the Azure surroundings you're trying to use.
  • Make sure you've signed in through the correct Azure environment like Azure, Azure China 21Vianet, Azure Deutschland, Azure United states Regime, or Custom Environs.
  • If you're backside a proxy server, brand sure you lot configured the Storage Explorer proxy correctly.
  • Endeavour removing and re-adding the business relationship.
  • If in that location's a "More information" or "Error details" link, bank check which error messages are being reported for the tenants that are declining. If you aren't certain how to respond to the mistake messages, open an consequence in GitHub.

Trouble interacting with your OS credential shop during an AzCopy transfer

If yous see this message on Windows, most likely the Windows Credential Manager is full. To make room in the Windows Credential Manager

  1. Close Storage Explorer
  2. On the Get-go menu, search for Credential Managing director and open it.
  3. Get to Windows Credentials.
  4. Nether Generic Credentials, look for entries associated with programs y'all no longer use and delete them. Yous can besides look for entries like azcopy/aadtoken/<some number> and delete those.

If the message continues to appear later on completing the above steps, or if you lot encounter this bulletin on platforms other than Windows, then please open an event on GitHub.

Can't remove an fastened storage account or resource

If you tin can't remove an attached business relationship or storage resource through the UI, yous can manually delete all attached resources past deleting the following folders:

  • Windows: %AppData%/StorageExplorer
  • macOS: /Users/<your_name>/Library/Awarding Support/StorageExplorer
  • Linux: ~/.config/StorageExplorer

Close Storage Explorer before yous delete these folders.

Annotation

If yous've e'er imported whatever SSL certificates, back up the contents of the certs directory. Later, yous can use the fill-in to reimport your SSL certificates.

Proxy issues

Storage Explorer supports connecting to Azure Storage resources via a proxy server. If you feel any issues when y'all connect to Azure via proxy, hither are some suggestions.

Storage Explorer just supports basic authentication with proxy servers. Other authentication methods, such as NTLM, aren't supported.

Note

Storage Explorer doesn't support proxy autoconfig files for configuring proxy settings.

Verify Storage Explorer proxy settings

The Application > Proxy > Proxy configuration setting determines which source Storage Explorer gets the proxy configuration from.

If you select Utilise environment variables, make sure to set the HTTPS_PROXY or HTTP_PROXY environment variables. Surroundings variables are example sensitive, so be sure to fix the correct variables. If these variables are undefined or invalid, Storage Explorer won't utilize a proxy. Restart Storage Explorer after you change any surround variables.

If you lot select Apply app proxy settings, make sure the in-app proxy settings are correct.

Steps for diagnosing issues

If you're all the same experiencing issues, attempt these troubleshooting methods:

  1. If you lot can connect to the internet without using your proxy, verify that Storage Explorer works without proxy settings enabled. If Storage Explorer connects successfully, in that location might exist an consequence with your proxy server. Piece of work with your admin to identify the problems.
  2. Verify that other applications that use the proxy server work as expected.
  3. Verify that y'all tin can connect to the portal for the Azure surroundings you're trying to employ.
  4. Verify that you can receive responses from your service endpoints. Enter one of your endpoint URLs into your browser. If y'all can connect, you should receive an InvalidQueryParameterValue or similar XML response.
  5. Check whether someone else using Storage Explorer with the same proxy server can connect. If they can, y'all might have to contact your proxy server admin.

Tools for diagnosing problems

A networking tool, such as Fiddler, can assistance you diagnose issues.

  1. Configure your networking tool equally a proxy server running on the local host. If you have to proceed working behind an actual proxy, you might have to configure your networking tool to connect through the proxy.
  2. Check the port number used by your networking tool.
  3. Configure Storage Explorer proxy settings to utilize the local host and the networking tool's port number, such as "localhost:8888".

When prepare correctly, your networking tool will log network requests made by Storage Explorer to management and service endpoints.

If your networking tool doesn't announced to exist logging Storage Explorer traffic, try testing your tool with a unlike awarding. For example, enter the endpoint URL for one of your storage resources, such as https://contoso.blob.core.windows.net/) in a web browser. You'll receive a response similar to this code sample.

Code sample.

The response suggests the resource exists, fifty-fifty though you can't access it.

If your networking tool just shows traffic from other applications, you lot might demand to adjust the proxy settings in Storage Explorer. Otherwise, you lot might need to accommodate your tool'south settings.

Contact proxy server admin

If your proxy settings are right, you might have to contact your proxy server admin to:

  • Make sure your proxy doesn't block traffic to Azure direction or resources endpoints.
  • Verify the authentication protocol used by your proxy server. Storage Explorer only supports basic hallmark protocols. Storage Explorer doesn't support NTLM proxies.

"Unable to Retrieve Children" fault message

If you're connected to Azure through a proxy, verify that your proxy settings are correct.

If the possessor of a subscription or account has granted you admission to a resources, verify that you have read or list permissions for that resource.

Connection string doesn't have complete configuration settings

If y'all receive this error bulletin, it's possible that y'all don't have the necessary permissions to obtain the keys for your storage account. To confirm that this is the case, go to the portal and locate your storage business relationship. Right-click the node for your storage account and select Open in Portal. Then, become to the Access Keys pane. If you don't have permissions to view keys, you'll meet a "You don't have access" message. To piece of work effectually this result, you lot tin can either obtain the account key from someone else and attach through the name and primal or yous tin ask someone for a shared access signature to the storage account and utilize it to attach the storage account.

If you practice see the business relationship keys, file an issue in GitHub so that nosotros tin can help you resolve the consequence.

"Mistake occurred while adding new connection: TypeError: Cannot read belongings 'version' of undefined"

If you receive this fault message when you try to add a custom connection, the connection data that's stored in the local credential manager might be corrupted. To work around this outcome, effort deleting your corrupted local connections, and and then re-add them:

  1. Offset Storage Explorer. From the menu, go to Help > Toggle Developer Tools.

  2. In the opened window, on the Awarding tab, go to Local Storage > file:// on the left side.

  3. Depending on the blazon of connection you're having an issue with, look for its key. Then copy its value into a text editor. The value is an assortment of your custom connectedness names, such as:

    • Storage accounts
      • StorageExplorer_CustomConnections_Accounts_v1
    • Blob containers
      • StorageExplorer_CustomConnections_Blobs_v1
      • StorageExplorer_CustomConnections_Blobs_v2
    • File shares
      • StorageExplorer_CustomConnections_Files_v1
    • Queues
      • StorageExplorer_CustomConnections_Queues_v1
    • Tables
      • StorageExplorer_CustomConnections_Tables_v1

  4. Later you save your current connection names, fix the value in Programmer Tools to [].

To preserve the connections that aren't corrupted, use the following steps to locate the corrupted connections. If you don't mind losing all existing connections, skip these steps and follow the platform-specific instructions to clear your connection data.

  1. From a text editor, re-add together each connection proper name to Developer Tools. And then cheque whether the connection is yet working.
  2. If a connection is working correctly, it's not corrupted and yous can safely leave information technology there. If a connection isn't working, remove its value from Developer Tools, and record it so that y'all can add it back subsequently.
  3. Echo until you've examined all your connections.

Later yous get through all your connections, for all connexion names that aren't added dorsum, you lot must articulate their corrupted data, if there is whatsoever. So add them back past using the standard steps in Storage Explorer.

  • Windows
  • macOS
  • Linux
  1. On the Starting time menu, search for Credential Director and open it.
  2. Go to Windows Credentials.
  3. Under Generic Credentials, await for entries that have the <connection_type_key>/<corrupted_connection_name> key. An example is StorageExplorer_CustomConnections_Accounts_v1/account1.
  4. Delete these entries and re-add the connections.

If you still encounter this error later on you lot run these steps, or if you want to share what you doubtable has corrupted the connections, open an event on our GitHub page.

If you connect to a service through a shared admission signature URL and experience an error:

  • Verify that the URL provides the necessary permissions to read or list resources.
  • Verify that the URL hasn't expired.
  • If the shared admission signature URL is based on an access policy, verify that the admission policy hasn't been revoked.

If you accidentally fastened by using an invalid shared access signature URL and now tin can't detach, follow these steps:

  1. When you're running Storage Explorer, select F12 to open the Developer Tools window.
  2. On the Application tab, select Local Storage > file:// on the left side.
  3. Observe the key associated with the service blazon of the problematic shared admission signature URI. For instance, if the bad shared access signature URI is for a blob container, look for the key named StorageExplorer_AddStorageServiceSAS_v1_blob.
  4. The value of the key should exist a JSON array. Find the object associated with the bad URI, and delete information technology.
  5. Select Ctrl+R to reload Storage Explorer.

Linux dependencies

Snap

Storage Explorer one.x.0 and after is bachelor equally a snap from the Snap Store. The Storage Explorer snap installs all its dependencies automatically. It's updated when a new version of the snap is available. Installing the Storage Explorer snap is the recommended method of installation.

Storage Explorer requires the use of a password director, which you might need to connect manually before Storage Explorer will work correctly. You tin can connect Storage Explorer to your organization's password managing director by running the following control:

              snap connect storage-explorer:countersign-manager-service :password-manager-service

.tar.gz file

You tin too download the application as a .tar.gz file, simply you'll accept to install dependencies manually.

Storage Explorer as provided in the .tar.gz download is supported for the post-obit versions of Ubuntu merely. Storage Explorer might work on other Linux distributions, but they aren't officially supported.

  • Ubuntu twenty.04 x64
  • Ubuntu eighteen.04 x64
  • Ubuntu 16.04 x64

Storage Explorer requires .Net Cadre 3.one to be installed on your organization.

Note

Storage Explorer versions one.8.0 through 1.xx.1 require .Cyberspace Core 2.1. Storage Explorer version ane.vii.0 and before require .NET Cadre 2.0.

  • Ubuntu xx.04
  • Ubuntu xviii.04
  • Ubuntu 16.04

  1. Download the Storage Explorer .tar.gz file.

  2. Install the .Net Core Runtime:

                          wget https://packages.microsoft.com/config/ubuntu/20.04/packages-microsoft-prod.deb -O packages-microsoft-prod.deb; \   sudo dpkg -i packages-microsoft-prod.deb; \   sudo apt-get update; \   sudo apt-get install -y apt-send-https && \   sudo apt-get update && \   sudo apt-get install -y dotnet-runtime-3.1

Many libraries needed past Storage Explorer come preinstalled with Canonical's standard installations of Ubuntu. Custom environments might be missing some of these libraries. If y'all take issues launching Storage Explorer, make sure the following packages are installed on your system:

  • iproute2
  • libasound2
  • libatm1
  • libgconf2-4
  • libnspr4
  • libnss3
  • libpulse0
  • libsecret-ane-0
  • libx11-xcb1
  • libxss1
  • libxtables11
  • libxtst6
  • xdg-utils

Patch Storage Explorer for newer versions of .NET Cadre

For Storage Explorer i.7.0 or before, you might have to patch the version of .NET Cadre used past Storage Explorer:

  1. Download version one.5.43 of StreamJsonRpc from NuGet.1. Look for the Download package link on the correct side of the folio.

  2. Later you download the bundle, change its file extension from .nupkg to .zilch.

  3. Unzip the package.

  4. Open up the streamjsonrpc.1.5.43/lib/netstandard1.i/ folder.

  5. Re-create StreamJsonRpc.dll to the following locations in the Storage Explorer binder:

    • StorageExplorer/resources/app/ServiceHub/Services/Microsoft.Programmer.IdentityService/
    • StorageExplorer/resources/app/ServiceHub/Hosts/ServiceHub.Host.Core.CLR.x64/

Open In Explorer button in the Azure portal doesn't work

If the Open In Explorer button in the Azure portal doesn't work, brand sure you're using a uniform browser. The following browsers were tested for compatibility:

  • Microsoft Border
  • Mozilla Firefox
  • Google Chrome
  • Microsoft Cyberspace Explorer

Gather logs

When you report an effect to GitHub, you lot might be asked to assemble certain logs to help diagnose your outcome.

Storage Explorer logs

Starting with version ane.16.0, Storage Explorer logs various things to its own application logs. You can easily get to these logs past selecting Help > Open Logs Directory. By default, Storage Explorer logs at a low level of verbosity. To modify the verbosity level, add together an surround variable with the name of STG_EX_LOG_LEVEL, and any of the post-obit values:

  • silent
  • disquisitional
  • error
  • warning
  • info (default level)
  • verbose
  • debug

Logs are carve up into folders for each session of Storage Explorer that you run. For whatever log files you need to share, place them in a zip archive, with files from different sessions in different folders.

Hallmark logs

For issues related to sign-in or Storage Explorer'south hallmark library, you'll most likely need to gather authentication logs. Authentication logs are stored at:

  • Windows: C:\Users\<your username>\AppData\Local\Temp\servicehub\logs
  • macOS and Linux: ~/.ServiceHub/logs

Generally, y'all can follow these steps to gather the logs:

  1. Go to Settings (the gear symbol on the left) > Application > Sign-in. Select Verbose Authentication Logging. If Storage Explorer fails to kickoff because of an issue with its hallmark library, this will exist washed for you.
  2. Close Storage Explorer.
  3. Optional/recommended: Clear out existing logs from the logs folder. This stride reduces the amount of information you take to send the states.
  4. Open Storage Explorer and reproduce your issue.
  5. Close Storage Explorer.
  6. Zero the contents of the logs folder.

AzCopy logs

If you're having trouble transferring data, you might need to get the AzCopy logs. AzCopy logs can be found easily via two different methods:

  • For failed transfers still in the Activeness Log, select Go to AzCopy Log File.

  • For transfers that failed in the by, go to the AzCopy logs binder. This folder tin be institute at:

    • Windows: C:\Users\<your username>\.azcopy
    • macOS and Linux: ~/.azcopy

Network logs

For some bug, you'll demand to provide logs of the network calls made by Storage Explorer. On Windows, yous can practice this step past using Fiddler.

Note

Fiddler traces might comprise passwords y'all entered or sent in your browser during the gathering of the trace. Brand sure to read the instructions on how to sanitize a Fiddler trace. Don't upload Fiddler traces to GitHub. You'll be told where y'all can securely send your Fiddler trace.

Part 1: Install and configure Fiddler

  1. Install Fiddler.

  2. Get-go Fiddler.

  3. Go to Tools > Options.

  4. Select the HTTPS tab.

  5. Make certain Capture CONNECTs and Decrypt HTTPS traffic are selected.

  6. Select Actions.

  7. Select Trust Root Certificate and then select Yes in the adjacent dialog.

  8. Select Actions again.

  9. Select Export Root Document to Desktop.

  10. Become to your desktop, find the FiddlerRoot.cer file, and double-click it.

  11. Go to the Details tab.

  12. Select Copy to File.

  13. In the consign wizard, choose the following options:

    • Base-64 encoded Ten.509.
    • For file name, browse to C:\Users\<your user dir>\AppData\Roaming\StorageExplorer\certs. So you can save it as any file name.

  14. Close the certificate window.

  15. Start Storage Explorer.

  16. Become to Edit > Configure Proxy.

  17. In the dialog, select Use app proxy settings. Ready the URL to http://localhost and the port to 8888.

  18. Select OK.

  19. Restart Storage Explorer.

  20. You should start seeing network calls from a storageexplorer: process evidence upward in Fiddler.

Part 2: Reproduce the issue

  1. Close all apps other than Fiddler.
  2. Articulate the Fiddler log past using the X in the top left, most the View menu.
  3. Optional/recommended: Permit Fiddler set for a few minutes. If you see network calls appear that aren't related to Storage Explorer, right-click them and select Filter At present > Hibernate (process name).
  4. Start Storage Explorer.
  5. Reproduce the upshot.
  6. Select File > Save > All Sessions. Save information technology somewhere yous won't forget.
  7. Close Fiddler and Storage Explorer.

Part 3: Sanitize the Fiddler trace

  1. Double-click the Fiddler trace (.saz file).
  2. Select Ctrl+F.
  3. In the dialog that appears, make sure the following options are gear up: Search = Requests and responses and Examine = Headers and bodies.
  4. Search for any passwords you used while you collected the Fiddler trace and whatsoever entries that are highlighted. Right-click and select Remove > Selected sessions.
  5. If you lot definitely entered passwords into your browser while you collected the trace but y'all don't find whatsoever entries when you use Ctrl+F, you don't want to change your passwords, or if the passwords y'all used are used for other accounts, skip sending the states the .saz file.
  6. Save the trace again with a new name.
  7. Optional: Delete the original trace.

Adjacent steps

If none of these solutions work for you, you tin:

  • Create a support ticket.
  • Open up an issue on GitHub by selecting the Written report result to GitHub push in the lower-left corner.

Feedback