Storage Exlporer 1.6.1:
OS: Linux - Ubuntu 14.04:
Architecture x86/64bit:
This is first time installation & use *:
I installed the required Ubuntu 14.04 dependencies.
.NET runtime is as follows:
Host (useful for support):
Version: 2.1.6
Commit: 3f4f8eebd8
.NET Core SDKs installed:
No SDKs were found.
.NET Core runtimes installed:
Microsoft.NETCore.App 2.1.6 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Started the Storage Explorer.
It launched the window to "Connect to Azure Storage".
Radio Button:"Add an Azure Account"
Azure environment: "Azure" drop down.
I clicked on "Sign in.."
It popped up the Sign in window. Entered my account email and then "next". It gave the password window. Entered it.
Then it entered the "waiting for authentication" loop which ended after a while but that window exited with no message about successful login or anything. Just exited, that's it.
But then the storage explorer window does not show any account. When I go to manage accounts, my account did not show up.
any help, please! ?!
I believe this is specific to your machine. Please feel free to reach out to our support team. They can help you better diagnose the issue. Here the instruction to opening a support request: https://docs.microsoft.com/en-us/azure/azure-supportability/how-to-create-azure-support-request
I have the same problem in ubuntu 18.04.
@jinglouMSFT The issue of not being able to login from Linux has been reported several times already, e.g. in #377 or #434. This does not appear to be a specific problem of just one user - I can reproduce this as well, and judging from this and the other linked issues, it seems to be more widespread than just a couple of accounts.
Same here. 16.04 after updating Ubuntu...
Didn't work 2 months ago with ArchLinux on one machine (so with the latest version of Azure Storage Explorer), still not working today with ArchLinux on another machine. Here is what the console says:

And the screen says "Waiting for authentication..." with a spinning wheel.
Same issue on ubuntu 18.04 with a fresh install.
Is there any solution to use this tool ?
Same issue here on debian 9 with a fresh install.
We recently discovered a breaking change in the .NETCore CLI that was shipped in the latest .NETCore. This change indirectly impacts the sign-in experience in Storage Explorer. We are working with the authentication lib team to incorporate the change in the lib. At the meantime, as a workaround, if you have the latest .NETCore (likely version 2.2.3) installed, please revert back to the lowest version of .NETCore 2.0.x available for your OS. We've verified with .NETCore 2.0.3 on Ubuntu.
If you don't have libgnome-keyring-common and libgnome-keyring0 installed, please install those as well.
As an alternative to @jinglouMSFT 's workaround, you can also manually patch Storage Explorer to fix the affected file. To do so you can perform the following steps:
.nupkg to .zipstreamjsonrpc.1.5.43/lib/netstandard1.1/StreamJsonRpc.dll to the following locations inside the Storage Explorer folder:StorageExplorer/resources/app/ServiceHub/Services/Microsoft.Developer.IdentityService/StorageExplorer/resources/app/ServiceHub/Hosts/ServiceHub.Host.Core.CLR.x64/If you do that, you shouldn't need to downgrade your .NET Core version. We'll be updating out Linux docs later today with updated Linux install instructions.
Perfect thank you. I will try that later today 馃憤
Here are the updated docs: https://docs.microsoft.com/en-us/azure/storage/common/storage-explorer-troubleshooting?tabs=1804#linux-dependencies
I was having the same issue on Linux 18.04
@MRayermannMSFT It worked for me, thx for the help.
Sounds like everyone is unblocked. Glad we could help. New auth library bits have been merged into master for 1.8.0 so future versions of Storage Explorer will not need the patch. Thank you for the patience. 馃槂
Most helpful comment
@jinglouMSFT The issue of not being able to login from Linux has been reported several times already, e.g. in #377 or #434. This does not appear to be a specific problem of just one user - I can reproduce this as well, and judging from this and the other linked issues, it seems to be more widespread than just a couple of accounts.