search

microsoft / AzureStorageExplorer

Easily manage the contents of your storage account with Azure Storage Explorer. Upload, download, and manage blobs, files, queues, tables, and Cosmos DB entities. Gain easy access to manage your virtual machine disks. Work with either Azure Resource Manager or classic storage accounts, plus manage and configure cross-origin resource sharing (CORS) rules.
Creative Commons Attribution 4.0 International
370 stars 85 forks source link

Azure Storage Explorer in AVD not connecting to Storage Account with Private Link Enabled #6472

Closed ShubjeetPal closed 1 year ago

ShubjeetPal commented 1 year ago

Preflight Checklist

Storage Explorer Version

1.27.2

Regression From

No response

Architecture

i86

Storage Explorer Build Number

20230123.2

Platform

Windows

OS Version

No response

Bug Description

Azure Storage Explorer for windows installed in Azure virtual Desktop not connecting to Storage Account with Private Link Enabled

Steps to Reproduce

1) I have 3 vnets for hub, spoke-dev and AVD. 2) Hub has VPN gateway and is peered with spoke-dev and AVD vnets with gateway transit enabled 3) Added storage account in spoke-dev vnet with private link. The private link has vnet link with hub, spoke-dev and AVD vnets 4) When accessing storage account from AVD remote desktop app for windows (from my laptop) getting below error a) request to https://devstgacct.blob.core.windows.net/?comp=list&include=metadata failed, reason: connect ETIMEDOUT 5) Created a vm in hub vnet. Logged in and same error from AVD remote desktop app for windows 6) Enabled private links for AVD and disabled public access from host pool and workspace a) Logged in again to vm in hub vnet. Same result from AVD remote desktop app for windows

Actual Experience

Details: { "name": "FetchError", "message": "request to https://devstgacct.blob.core.windows.net/?comp=list&include=metadata failed, reason: connect ETIMEDOUT 10.1.1.4:443", "stack": "FetchError: request to https://devstgacct.blob.core.windows.net/?comp=list&include=metadata failed, reason: connect ETIMEDOUT 10.1.1.4:443\n at ClientRequest. (C:\Users\ShubjeetPal\AppData\Local\Programs\Microsoft Azure Storage Explorer\resources\app\node_modules\se-blob-extension\dist\src\index.js:2:2440800)\n at ClientRequest.emit (node:events:527:28)\n at TLSSocket.socketErrorListener (node:_http_client:454:9)\n at TLSSocket.emit (node:events:527:28)\n at emitErrorNT (node:internal/streams/destroy:157:8)\n at emitErrorCloseNT (node:internal/streams/destroy:122:3)\n at process.processTicksAndRejections (node:internal/process/task_queues:83:21)", "type": "system", "errno": "ETIMEDOUT", "code": "ETIMEDOUT" }

Expected Experience

Connection Should work

Additional Context

No response

MRayermannMSFT commented 1 year ago

@ShubjeetPal

  1. Can you try using System Proxy? You can read more about it here: https://learn.microsoft.com/en-us/azure/storage/common/storage-explorer-network#use-system-proxy-preview
  2. If you make a SAS url to a blob in your container, and then try to use that SAS url in the browser in the AVD instance, is the browser able to reach the blob?
MRayermannMSFT commented 1 year ago

Closing due to lack of response. If you are still encountering this issue we recommend opening an Azure support ticket from the portal. Alternatively you can open a new issue here.