Azure 存储资源管理器故障排除指南Azure Storage Explorer troubleshooting guide

Azure 存储资源管理器是一个独立的应用,使用它可在 Windows、macOS 和 Linux 上轻松处理 Azure 存储数据。Azure Storage Explorer is a standalone app that makes it easy to work with Azure Storage data on Windows, macOS, and Linux. 应用可连接到托管在 Azure、National Clouds 和 Azure Stack 上的存储帐户。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 权限问题Azure RBAC permissions issues

使用 Azure 基于角色的访问控制 (Azure RBAC),可以通过将权限集组合成角色,对 Azure 资源进行极精细的访问管理。Azure role-based access control Azure RBAC enables highly granular access management of Azure resources by combining sets of permissions into roles. 下面是在存储资源管理器中以最佳方式使用 Azure RBAC 的一些策略。Here are some strategies to get Azure RBAC working optimally in Storage Explorer.

如何在存储资源管理器中访问我的资源?How do I access my resources in Storage Explorer?

如果你在通过 Azure RBAC 访问存储资源时遇到问题,原因可能是你尚未被分配相应的角色。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. 如果你不确定自己是否拥有相应的角色或权限,请联系 Azure 帐户管理员。Contact your Azure account administrator if you're not sure you have the appropriate roles or permissions.

“读取:列出/获取存储帐户”权限问题"Read: List/Get Storage Account(s)" permissions issue

必须有权列出存储帐户。You must have permission to list storage accounts. 若要获取此权限,必须具有“读取者”角色。To get this permission, you must be assigned the Reader role.

列出存储帐户密钥List storage account keys

存储资源管理器还可以使用帐户密钥对请求进行身份验证。Storage Explorer can also use account keys to authenticate requests. 可以通过权限更高的角色(例如“参与者”角色)来获取帐户密钥的访问权限。You can get access to account keys through more powerful roles, such as the Contributor role.

备注

访问密钥向其任何持有者授予不受限制的权限。Access keys grant unrestricted permissions to anyone who holds them. 因此,我们不建议将这些密钥分发给帐户用户。Therefore, we don't recommend that you hand out these keys to account users. 如果需要撤销访问密钥,可以通过 Azure 门户重新生成访问密钥。If you need to revoke access keys, you can regenerate them from the Azure portal.

数据角色Data roles

必须至少拥有一个可以授予对资源中数据的读取访问权限的角色。You must be assigned at least one role that grants access to read data from resources. 例如,如果需要列出或下载 Blob,则至少需要拥有“存储 Blob 数据读取者”角色。For example, if you want to list or download blobs, you'll need at least the Storage Blob Data Reader role.

为何需要管理层角色才能在存储资源管理器中查看我的资源?Why do I need a management layer role to see my resources in Storage Explorer?

Azure 存储提供两个访问层:“管理”和“数据”。 Azure Storage has two layers of access: management and data. 订阅和存储帐户是通过管理层访问的。Subscriptions and storage accounts are accessed through the management layer. 容器、Blob 和其他数据资源是通过数据层访问的。Containers, blobs, and other data resources are accessed through the data layer. 例如,若要从 Azure 获取存储帐户的列表,应向管理终结点发送请求。For example, if you want to get a list of your storage accounts from Azure, you send a request to the management endpoint. 若要列出帐户中的 Blob 容器,应向相应的服务终结点发送请求。If you want a list of blob containers in an account, you send a request to the appropriate service endpoint.

Azure 角色可以授予你进行管理或数据层访问的权限。Azure roles can grant you permissions for management or data layer access. 例如,“读取者”角色授予对管理层资源的只读访问权限。The Reader role, for example, grants read-only access to management layer resources.

严格地讲,“读取者”角色不提供数据层的权限,并非一定要有该角色才能访问数据层。Strictly speaking, the Reader role provides no data layer permissions and isn't necessary for accessing the data layer.

在存储资源管理器中,可以通过收集连接到 Azure 资源所需的信息,来轻松访问资源。Storage Explorer makes it easy to access your resources by gathering the necessary information to connect to your Azure resources. 例如,若要显示 Blob 容器,存储资源管理器会向 Blob 服务终结点发送“列出容器”请求。For example, to display your blob containers, Storage Explorer sends a "list containers" request to the blob service endpoint. 若要获取该终结点,存储资源管理器会搜索你有权访问的订阅和存储帐户列表。To get that endpoint, Storage Explorer searches the list of subscriptions and storage accounts you have access to. 若要查找订阅和存储帐户,存储资源管理器还需要有权访问管理层。To find your subscriptions and storage accounts, Storage Explorer also needs access to the management layer.

如果你没有一个可以授予任何管理层权限的角色,则存储资源管理器无法获取连接到数据层所需的信息。If you don't have a role that grants any management layer permissions, Storage Explorer can't get the information it needs to connect to the data layer.

如果我无法从管理员获取管理层权限,该怎么办?What if I can't get the management layer permissions I need from my administrator?

若要要访问 Blob 容器、ADLS Gen2 容器或目录或队列,你可以使用 Azure 凭据连接到这些资源。If you want to access blob containers, ADLS Gen2 containers or directories, or queues, you can attach to those resources using your Azure credentials.

  1. 打开“连接”对话框。Open the Connect dialog.
  2. 选择要连接到的资源类型。Select the resource type you want to connect to.
  3. 选择“使用 Azure Active Directory (Azure AD)登录”。Select Sign in using Azure Active Directory (Azure AD). 选择“下一步”。Select Next.
  4. 选择与要连接到的资源关联的用户帐户和租户。Select the user account and tenant associated with the resource you're attaching to. 选择“下一步”。Select Next.
  5. 输入资源的 URL,并为连接输入唯一的显示名称。Enter the URL to the resource, and enter a unique display name for the connection. 选择“下一步”,然后选择“连接” 。Select Next then Connect.

对于其他资源类型,我们目前尚未制定与 Azure RBAC 相关的解决方案。For other resource types, we don't currently have an Azure RBAC-related solution. 作为一种解决方法,你可以请求 SAS URL,然后通过以下步骤连接到你的资源:As a workaround, you can request a SAS URL then attach to your resource by following these steps:

  1. 打开“连接”对话框。Open the Connect dialog.
  2. 选择要连接到的资源类型。Select the resource type you want to connect to.
  3. 选择“共享访问签名(SAS)”。Select Shared access signature (SAS). 选择“下一步”。Select Next.
  4. 输入你收到的 SAS URL,并输入连接的唯一显示名称。Enter the SAS URL you received and enter a unique display name for the connection. 选择“下一步”,然后选择“连接” 。Select Next then Connect.

有关连接到资源的详细信息,请参阅连接到单个资源For more information on attaching to resources, see Attach to an Individual Resource.

有几个 Azure 内置角色可以提供使用存储资源管理器所需的权限。There are several Azure built-in roles that can provide the permissions needed to use Storage Explorer. 其中一些角色是:Some of those roles are:

备注

“所有者”、“参与者”和“存储帐户参与者”角色授予帐户密钥访问权限。The Owner, Contributor, and Storage Account Contributor roles grant account key access.

错误:证书链中的自签名证书(和类似错误)Error: Self-signed certificate in certificate chain (and similar errors)

如果存在以下情况之一,则往往会发生证书错误:Certificate errors typically occur in one of the following situations:

  • 应用通过 透明代理 进行连接。The app is connected through a transparent proxy. 这意味着一台服务器(例如公司的服务器)正在截取 HTTPS 流量,对其进行解密,然后使用自签名证书对其进行加密。This means a server (such as your company server) is intercepting HTTPS traffic, decrypting it, and then encrypting it by using a self-signed certificate.
  • 正在运行的应用程序正在向收到的 HTTPS 消息注入自签名 TLS/SSL 证书。You're running an application that's injecting a self-signed TLS/SSL certificate into the HTTPS messages that you receive. 注入证书的应用程序示例包括防病毒软件和网络流量检查软件。Examples of applications that inject certificates include antivirus and network traffic inspection software.

当存储资源管理器看到自签名或不受信任的证书时,无法再判断收到的 HTTPS 消息是否被更改。When Storage Explorer sees a self-signed or untrusted certificate, it no longer knows whether the received HTTPS message has been altered. 如果拥有自签名证书的副本,可通过执行以下步骤,让存储资源管理器信任它:If you have a copy of the self-signed certificate, you can instruct Storage Explorer to trust it by following these steps:

  1. 获取证书的 Base-64 编码 X.509 (.cer) 副本。Obtain a Base-64 encoded X.509 (.cer) copy of the certificate.
  2. 转到“编辑” > “SSL 证书” > “导入证书”,然后使用文件选取器查找、选择和打开 .cer 文件 Go to Edit > SSL Certificates > Import Certificates, and then use the file picker to find, select, and open the .cer file.

此问题还有可能是由于存在多个证书(根证书和中间证书)造成的。This issue may also occur if there are multiple certificates (root and intermediate). 若要修复此错误,必须同时添加这两个证书。To fix this error, both certificates must be added.

如果你不确定该证书来源于何处,可以执行以下步骤来找到它:If you're unsure of where the certificate is coming from, follow these steps to find it:

  1. 安装 OpenSSL。Install OpenSSL.
    • Windows:任何精简版本均可。Windows: Any of the light versions should be sufficient.
    • Mac 和 Linux:应包含在操作系统中。Mac and Linux: Should be included with your operating system.
  2. 运行 OpenSSL。Run OpenSSL.
    • Windows:打开安装目录,选择“/bin/”,然后双击“openssl.exe” 。Windows: Open the installation directory, select /bin/, and then double-click openssl.exe.
    • Mac 和 Linux:从终端运行 opensslMac and Linux: Run openssl from a terminal.
  3. 运行 s_client -showcerts -connect microsoft.com:443Run s_client -showcerts -connect microsoft.com:443.
  4. 查找自签名证书。Look for self-signed certificates. 如果不确定哪些证书是自签名证书,请记下使用者 ("s:") 和证书颁发者 ("i:") 相同的任意位置。If you're unsure of which certificates are self-signed, make note of anywhere the subject ("s:") and issuer ("i:") are the same.
  5. 找到自签名证书后,将每个证书中从 -----BEGIN CERTIFICATE-----(含)到 -----END CERTIFICATE-----(含)的所有内容复制并粘贴到新的 .cer 文件中。When you find self-signed certificates, for each one, copy and paste everything from (and including) -----BEGIN CERTIFICATE----- through -----END CERTIFICATE----- into a new .cer file.
  6. 打开存储资源管理器,然后转到“编辑” > “SSL 证书” > “导入证书”。Open Storage Explorer and go to Edit > SSL Certificates > Import Certificates. 然后使用文件选取器查找、选择并打开创建的 .cer 文件。Then use the file picker to find, select, and open the .cer files that you created.

如果通过上述步骤无法找到任何自签名证书,请通过反馈工具联系我们以获取更多帮助。If you can't find any self-signed certificates by following these steps, contact us through the feedback tool. 也可选择通过命令行使用 --ignore-certificate-errors 标志打开存储资源管理器。You can also open Storage Explorer from the command line by using the --ignore-certificate-errors flag. 使用此标志打开后,存储资源管理器将忽略证书错误。When opened with this flag, Storage Explorer ignores certificate errors.

登录问题Sign-in issues

了解登录Understanding sign-in

请确保已阅读登录到存储资源管理器文档。Make sure you have read the Sign in to Storage Explorer documentation.

经常需要重新输入凭据Frequently having to reenter credentials

很可能是基于 AAD 管理员设置的条件访问策略才要求你重新输入凭据。Having to reenter credentials is most likely the result of conditional access policies set by your AAD administrator. 存储资源管理器要求你从帐户面板重新输入凭据时,应会看到“错误详细信息...”链接。When Storage Explorer asks you to reenter credentials from the account panel, you should see an Error details... link. 单击该链接以查看存储资源管理器要求你重新输入凭据的原因。Click on that to see why Storage Explorer is asking you to reenter credentials. 要求重新输入凭据的条件访问策略错误可能类似于以下内容:Conditional access policy errors that require reentering of credentials may look something like these:

  • 刷新令牌已过期...The refresh token has expired...
  • 必须使用多重身份验证才能访问...You must use multi-factor authentication to access...
  • 由于管理员所做的配置更改...Due to a configuration change made by your administrator...

为了减少由于上述错误而不得不重新输入凭据的频率,需要与 AAD 管理员联系。To reduce the frequency of having to reenter credentials due to errors like the ones above, you will need to talk to your AAD administrator.

条件性访问策略Conditional access policies

如果帐户需要满足条件访问策略,请确保将“默认 web 浏览器”值用于“登录方式”设置 。If you have conditional access policies that need to be satisfied for your account, make sure you are using the Default Web Browser value for the Sign in with setting. 有关此设置的信息,请参阅更改登录的位置For information on that setting, see Changing where sign in happens.

无法获取令牌,租户已被筛除Unable to acquire token, tenant is filtered out

如果你看到一条错误消息,指出由于租户被筛除而无法获取令牌,则意味着你正在尝试访问已被筛除的租户中的资源。若要取消筛选该租户,请转到“帐户面板”,并确保选中错误中指定租户的复选框。If you see an error message saying that a token cannot be acquired because a tenant is filtered out, that means you are trying to access a resource which is in a tenant you have filtered out. To unfilter the tenant, go to the Account Panel and make sure the checkbox for the tenant specified in the error is checked. 有关在存储资源管理器中筛选租户的详细信息,请参阅管理帐户Refer to the Managing accounts for more information on filtering tenants in Storage Explorer.

身份验证库未能正确启动Authentication library failed to start properly

如果在启动时看到一条错误消息,指出存储资源管理器的身份验证库未能正常启动,请确保安装环境满足所有先决条件If on startup you see an error message which says that Storage Explorer's authentication library failed to start properly then make sure your install environment meets all prerequisites. 未满足先决条件是导致该错误消息的最常见原因。Not meeting prerequisites is the most likely cause of this error message.

如果认为安装环境满足所有先决条件,请在 GitHub 上提问If you believe that your install environment meets all prerequisites, then open an issue on GitHub. 提问时,请确保提供以下信息:When you open your issue, make sure to include:

  • 你的 OS。Your OS.
  • 尝试使用的存储资源管理器版本。What version of Storage Explorer you are trying to use.
  • 是否已检查先决条件。If you checked the prerequisites.
  • 存储资源管理器启动失败时的身份验证日志Authentication logs from an unsuccessful launch of Storage Explorer. 发生此类错误后,会自动启用详细身份验证日志记录。Verbose authentication logging is automatically enabled after this type of error occurs.

使用集成登录时的空白窗口Blank window when using integrated sign-in

如果选择使用集成登录并看到一个空白的登录窗口,则可能需要切换为其他登录方法。If you have chosen to use Integrated Sign-in and are seeing a blank sign window, you will likely need to switch to a different sign-in method. 出现空白登录对话框的原因往往是 Active Directory 联合身份验证服务 (ADFS) 服务器提示存储资源管理器执行 Electron 不支持的重定向。Blank sign-in dialog boxes most often occur when an Active Directory Federation Services (ADFS) server prompts Storage Explorer to perform a redirect that is unsupported by Electron.

通过在“设置” > “应用程序” > “登录”下更改“登录方式”设置,可更改为其他登录方法 。To change to a different sign-in method by changing the Sign in with setting under Settings > Application > Sign-in. 有关不同类型的登录方法的信息,请参阅更改登录的位置For information on the different types of sign-in methods, see Changing where sign in happens.

重新验证循环或 UPN 更改Reauthentication loop or UPN change

如果你处于重新验证循环中,或者已更改其中一个帐户的 UPN,请尝试以下步骤:If you're in a reauthentication loop or have changed the UPN of one of your accounts then try these steps:

  1. 打开存储资源管理器Open Storage Explorer
  2. 转到“帮助”>“重置”Go to Help > Reset
  3. 请确保至少“身份验证”处于选中状态。Make sure at least Authentication is checked. 可以取消选中不希望重置的其他项。You can uncheck other items you do not want to reset.
  4. 单击“重置”按钮Click the Reset button
  5. 重启存储资源管理器并再次尝试登录。Restart Storage Explorer and try signing in again.

如果在执行重置后仍有问题,请尝试以下步骤:If you continue to have issues after doing a reset then try these steps:

  1. 打开存储资源管理器Open Storage Explorer
  2. 删除所有帐户,然后关闭存储资源管理器。Remove all accounts and then close Storage Explorer.
  3. 从计算机中删除 .IdentityService 文件夹。Delete the .IdentityService folder from your machine. 在 Windows 中,该文件夹位于 C:\users\<username>\AppData\LocalOn Windows, the folder is located at C:\users\<username>\AppData\Local. 对于 Mac 和 Linux,可以在用户目录的根目录中找到该文件夹。For Mac and Linux, you can find the folder at the root of your user directory.
  4. 如果运行 Mac 或 Linux,则还需要从操作系统的密钥存储中删除 Microsoft.Developer.IdentityService 条目。If you're running Mac or Linux, you'll also need to delete the Microsoft.Developer.IdentityService entry from your operating system's keystore. 在 Mac 上,密钥存储是 Gnome Keychain 应用程序。On the Mac, the keystore is the Gnome Keychain application. 对于 Linux,该应用程序通常称为 Keyring,但名称可能会有所不同,具体取决于分发版。In Linux, the application is typically called Keyring, but the name might differ depending on your distribution.
  5. 重启存储资源管理器并再次尝试登录。Restart Storage Explorer and try signing in again.

macOS:密钥链错误或无登录窗口macOS: keychain errors or no sign-in window

有时,macOS 密钥链可能会进入导致存储资源管理器的身份验证库出现问题的状态。The macOS Keychain can sometimes enter a state that causes issues for the Storage Explorer authentication library. 若要使 Keychain 进入此状态,请执行以下步骤:To get the Keychain out of this state, follow these steps:

  1. 关闭存储资源管理器。Close Storage Explorer.

  2. 打开 Keychain(按命令键+空格键,键入 keychain,然后按 Enter)。Open Keychain (press Command+Spacebar, type keychain, and press Enter).

  3. 选择“登录”Keychain。Select the "login" Keychain.

  4. 选择挂锁图标以锁定 Keychain。Select the padlock icon to lock the Keychain. (该过程完成后,挂锁将以锁定状态显示。(The padlock will appear locked when the process is complete. 这可能需要几秒钟的时间,具体要取决于打开的应用)。It might take a few seconds, depending on what apps you have open).

    挂锁图标

  5. 打开存储资源管理器。Open Storage Explorer.

  6. 此时会出现一条类似于“服务中心想要访问 Keychain”的消息。You're prompted with a message like "Service hub wants to access the Keychain." 输入 Mac 管理员帐户密码,然后选择“始终允许”(如果未显示“始终允许”,则选择“允许”)。Enter your Mac admin account password and select Always Allow (or Allow if Always Allow isn't available).

  7. 请尝试登录。Try to sign in.

默认浏览器无法打开Default browser doesn't open

如果尝试登录时默认浏览器无法打开,请尝试以下所有方法:If your default browser does not open when trying to sign in try all of the following techniques:

  • 重启存储资源管理器Restart Storage Explorer
  • 在开始登录之前手动打开浏览器Open your browser manually before starting sign-in
  • 尝试使用“集成登录”,有关操作说明,请参阅更改登录的位置Try using Integrated Sign-In, see Changing where sign in happens for instructions on how to do this.

其他登录问题Other sign-in issues

如果上述方法均不适用于你的登录问题,或者无法解决你的问题,请在 GitHub 上提问If none of the above apply to your sign-in issue or if they fail to resolve you sign-in issue open an issue on GitHub.

缺少订阅和中断的租户Missing subscriptions and broken tenants

如果成功登录后无法检索订阅,请尝试以下故障排除方法:If you can't retrieve your subscriptions after you successfully sign in, try the following troubleshooting methods:

  • 验证你的帐户是否有权访问所需的订阅。Verify that your account has access to the subscriptions you expect. 可以通过登录到尝试使用的 Azure 环境的门户,来验证是否能够访问这些订阅。You can verify your access by signing in to the portal for the Azure environment you're trying to use.
  • 确保已通过正确的 Azure 环境(Azure 中国世纪互联)登录。Make sure you've signed in through the correct Azure environment (Azure China 21Vianet).
  • 如果使用代理服务器,请确保已正确配置存储资源管理器代理。If you're behind a proxy server, make sure you've configured the Storage Explorer proxy correctly.
  • 尝试删除并重新添加帐户。Try removing and re-adding the account.
  • 如果有“更多信息”或“错误详细信息”链接,请查看针对失败的租户报告的错误消息。If there's a "More information" or "Error details" link, check which error messages are being reported for the tenants that are failing. 如果你不确定如何处理错误消息,请随意在 GitHub 上提出问题If you aren't sure how to respond to the error messages, feel free to open an issue in GitHub.

无法删除附加的存储帐户或资源Can't remove an attached storage account or resource

如果无法通过 UI 删除附加的帐户或存储资源,可以通过删除以下文件夹来手动删除所有附加的资源:If you can't remove an attached account or storage resource through the UI, you can manually delete all attached resources by deleting the following folders:

  • Windows: %AppData%/StorageExplorerWindows: %AppData%/StorageExplorer
  • macOS:/Users/<your_name>/Library/Application Support/StorageExplorermacOS: /Users/<your_name>/Library/Application Support/StorageExplorer
  • Linux:~/.config/StorageExplorerLinux: ~/.config/StorageExplorer

备注

先关闭存储资源管理器,然后删除这些文件夹。Close Storage Explorer before you delete these folders.

备注

如果曾经导入了任何 SSL 证书,请备份 certs 目录的内容。If you have ever imported any SSL certificates, back up the contents of the certs directory. 以后,可以使用备份来重新导入 SSL 证书。Later, you can use the backup to reimport your SSL certificates.

代理问题Proxy issues

存储资源管理器支持通过代理服务器连接到 Azure 存储资源。Storage Explorer supports connecting to Azure Storage resources via a proxy server. 如果通过代理连接到 Azure 时遇到任何问题,请参阅下面的建议。If you experience any issues connecting to Azure via proxy, here are some suggestions.

备注

存储资源管理器仅支持通过代理服务器进行基本身份验证。Storage Explorer only supports basic authentication with proxy servers. 不支持其他身份验证方法,例如 NTLM。Other authentication methods, such as NTLM, are not supported.

备注

存储资源管理器不支持使用代理 auto-config 文件来配置代理设置。Storage Explorer doesn't support proxy auto-config 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.

如果你选择“使用环境变量”,请确保设置 HTTPS_PROXYHTTP_PROXY 环境变量(环境变量区分大小写,因此请确保设置正确的变量)。If you select "Use environment variables", make sure to set the HTTPS_PROXY or HTTP_PROXY environment variables (environment variables are case-sensitive, so be sure to set the correct variables). 如果这些变量未定义或无效,则存储资源管理器将不使用代理。If these variables are undefined or invalid, Storage Explorer won't use a proxy. 修改任何环境变量后,请重启存储资源管理器。Restart Storage Explorer after modifying any environment variables.

如果你选择“使用应用代理设置”,请确保应用内代理设置正确无误。If you select "Use app proxy settings", make sure the in-app proxy settings are correct.

用于诊断问题的步骤Steps for diagnosing issues

如果仍遇到问题,请尝试以下故障排除方法:If you're still experiencing issues, try these troubleshooting methods:

  1. 如果在不使用代理时可以连接到 Internet,请确认未启用代理设置时存储资源管理器可以正常工作。If you can connect to the internet without using your proxy, verify that Storage Explorer works without proxy settings enabled. 如果存储资源管理器成功连接,则代理服务器可能存在问题。If Storage Explorer connects successfully, there may be an issue with your proxy server. 与管理员配合找到问题所在。Work with your administrator to identify the problems.
  2. 确认使用代理服务器的其他应用程序按预期运行。Verify that other applications that use the proxy server work as expected.
  3. 验证是否能够连接到尝试使用的 Azure 环境的门户。Verify that you can connect to the portal for the Azure environment you're trying to use.
  4. 确认可以收到来自服务终结点的响应。Verify that you can receive responses from your service endpoints. 在浏览器中输入其中一个终结点 URL。Enter one of your endpoint URLs into your browser. 如果你可以连接,应会收到 InvalidQueryParameterValue 或类似的 XML 响应。If you 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, you may have to contact your proxy server admin.

诊断问题的工具Tools for diagnosing issues

一个可以帮助你诊断问题的网络工具,例如 Fiddler。A networking tool, such as Fiddler, can help you diagnose problems.

  1. 将你的网络工具配置为在本地主机上运行的代理服务器。Configure your networking tool as a proxy server running on the local host. 如果必须继续在实际代理后面工作,则必须将网络工具配置为通过代理进行连接。If you have to continue working behind an actual proxy, you may have to configure your networking tool to connect through the proxy.
  2. 检查网络服务工具使用的端口号。Check the port number used by your networking tool.
  3. 配置存储资源管理器代理设置,以便使用本地主机和网络工具的端口号(例如“localhost:8888”)。Configure Storage Explorer proxy settings to use the local host and the networking tool's port number (such as "localhost:8888").

当设置正确时,你的网络工具会记录存储资源管理器向管理和服务终结点发出的网络请求。When set correctly, your networking tool will log network requests made by Storage Explorer to management and service endpoints.

如果你的网络工具看起来没有记录存储资源管理器流量,请尝试使用不同的应用程序来测试你的工具。If your networking tool doesn't appear to be logging Storage Explorer traffic, try testing your tool with a different application. 例如,在 Web 浏览器中输入存储资源之一的终结点 URL(例如 https://contoso.blob.core.chinacloudapi.cn/),然后就会收到类似于以下内容的响应:For example, enter the endpoint URL for one of your storage resources (such as https://contoso.blob.core.chinacloudapi.cn/) in a web browser, and you'll receive a response similar to:

代码示例

此响应表示资源存在,虽然你无法访问它。The response suggests the resource exists, even though you can't access it.

如果网络工具仅显示了来自其他应用程序的流量,则你可能需要在存储资源管理器中调整代理设置。If your networking tool only shows traffic from other applications, you may need to adjust the proxy settings in Storage Explorer. 否则,你可能需要调整工具的设置。Otherwise, you made need to adjust your tool's settings.

与代理服务器管理员联系Contact proxy server admin

如果代理设置正确,则可能需要与代理服务器管理员联系,以便:If your proxy settings are correct, you may have to contact your proxy server administrator to:

  • 确保代理不会阻止到 Azure 管理或资源终结点的流量。Make sure your proxy doesn't block traffic to Azure management or resource endpoints.
  • 验证代理服务器使用的身份验证协议。Verify the authentication protocol used by your proxy server. 存储资源管理器仅支持基本身份验证协议。Storage Explorer only supports basic authentication protocols. 存储资源管理器不支持 NTLM 代理。Storage Explorer doesn't support NTLM proxies.

“无法检索子级”错误消息"Unable to Retrieve Children" error message

如果通过代理连接到 Azure,请确认代理设置正确无误。If you're connected to Azure through a proxy, verify that your proxy settings are correct.

如果订阅或帐户的所有者已向你授予对某个资源的访问权限,请验证你是否对该资源拥有读取或列出权限。If the owner of a subscription or account has granted you access to a resource, verify that you have read or list permissions for that resource.

连接字符串没有完整的配置设置Connection string doesn't have complete configuration settings

如果收到此错误消息,则表示你可能没有所需的权限来获取你的存储帐户的密钥。If you receive this error message, it's possible that you 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 account. 可以通过右键单击存储帐户的节点并选择“在门户中打开”来执行此操作。You can do this by right-clicking the node for your storage account and selecting Open in Portal. 然后转到“访问密钥”边栏选项卡。Then, go to the Access Keys blade. 如果你无权查看密钥,则会看到“你没有访问权限”消息。If you don't have permissions to view keys, you'll see a "You don't have access" message. 若要解决此问题,可以从其他某人获取帐户密钥并结合名称和密钥附加存储帐户,或者,向某人索要存储帐户的 SAS 并使用它来附加存储帐户。To work around this issue, you can either obtain the account key from someone else and attach through the name and key, or you can ask someone for a SAS to the storage account and use it to attach the storage account.

如果看到了帐户密钥,请在 GitHub 上提出问题,使我们能够帮助你解决问题。If you do see the account keys, file an issue in GitHub so that we can help you resolve the issue.

添加新连接时出错:TypeError:无法读取未定义的属性 'version'Error occurred while adding new connection: TypeError: Cannot read property 'version' of undefined

如果你在尝试添加自定义连接时收到此错误消息,则可能是本地凭据管理器中存储的连接数据已损坏。If you receive this error 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 issue, try deleting your corrupted local connections, and then re-add them:

  1. 启动存储资源管理器。Start Storage Explorer. 在顶部菜单中,转到“帮助” > “切换开发人员工具”。From the menu, go to Help > Toggle Developer Tools.
  2. 在打开的窗口中的“应用程序”选项卡上,转到“本地存储”(左侧)>“file://”。 In the opened window, on the Application tab, go to Local Storage (left side) > file://.
  3. 根据遇到问题的连接类型,查找其密钥并将其值复制到文本编辑器。Depending on the type of connection you're having an issue with, look for its key and then copy its value into a text editor. 该值是自定义连接名称的数组,如下所示:The value is an array of your custom connection names, like the following:
    • 存储帐户Storage accounts
      • StorageExplorer_CustomConnections_Accounts_v1
    • Blob 容器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. 保存当前连接名称后,将开发人员工具中的值设置为 []After you save your current connection names, set the value in Developer Tools to [].

若要保留未损坏的连接,可以使用以下步骤来查找损坏的连接。If you want to preserve the connections that aren't corrupted, you can use the following steps to locate the corrupted connections. 如果你不介意丢失所有现有连接,则可以跳过以下步骤,并按照平台特定说明清除连接数据。If you don't mind losing all existing connections, you can skip these steps and follow the platform-specific instructions to clear your connection data.

  1. 在文本编辑器中,将每个连接名称重新添加到开发人员工具,并检查连接是否仍在运行。From a text editor, re-add each connection name to Developer Tools, and then check whether the connection is still working.
  2. 如果连接正常工作,则表示它未损坏,你可以安全地将其保留。If a connection is working correctly, it's not corrupted and you can safely leave it there. 如果连接不起作用,请从开发人员工具中删除其值并将其记录,以便以后可以重新添加它。If a connection isn't working, remove its value from Developer Tools, and record it so that you can add it back later.
  3. 重复此步骤,直到检查完所有连接。Repeat until you have examined all your connections.

完成所有连接后,针对所有未添加回的连接名称,必须清除其损坏的数据(如果有),并使用存储资源管理器中的标准步骤将其重新添加。After going through all your connections, for all connections names that aren't added back, you must clear their corrupted data (if there is any) and add them back by using the standard steps in Storage Explorer:

  1. 在“开始”菜单中,搜索“凭据管理器”并将其打开。 On the Start menu, search for Credential Manager and open it.
  2. 转到“Windows 凭据”。Go to Windows Credentials.
  3. 在“一般凭据”下,找到具有 <connection_type_key>/<corrupted_connection_name> 键的条目(例如 StorageExplorer_CustomConnections_Accounts_v1/account1)。Under Generic Credentials, look for entries that have the <connection_type_key>/<corrupted_connection_name> key (for example, StorageExplorer_CustomConnections_Accounts_v1/account1).
  4. 删除这些条目并重新添加连接。Delete these entries and re-add the connections.

如果运行这些步骤后仍遇到此错误,或者你想要分享连接损坏原因的看法,请在 GitHub 页上提出问题If you still encounter this error after running these steps, or if you want to share what you suspect has corrupted the connections, open an issue on our GitHub page.

SAS URL 的问题Issues with SAS URL

如果通过 SAS URL 连接到服务时遇到错误:If you're connecting to a service through a SAS URL and experiencing an error:

  • 请确认 URL 提供了读取或列出资源所需的权限。Verify that the URL provides the necessary permissions to read or list resources.
  • 请确认 URL 未过期。Verify that the URL has not expired.
  • 如果 SAS URL 基于访问策略,请确认访问策略尚未吊销。If the SAS URL is based on an access policy, verify that the access policy has not been revoked.

如果意外附加了无效的 SAS URL,并且现在无法分离,请执行以下步骤:If you accidentally attached by using an invalid SAS URL and now cannot detach, follow these steps:

  1. 运行存储资源管理器时,按 F12 打开“开发人员工具”窗口。When you're running Storage Explorer, press F12 to open the Developer Tools window.
  2. 在“应用程序”选项卡上,选择左侧树中的“本地存储” > “file://”。 On the Application tab, select Local Storage > file:// in the tree on the left.
  3. 查找与有问题的 SAS URI 服务类型关联的键。Find the key associated with the service type of the problematic SAS URI. 例如,如果用于 blob 容器的 SAS URI 错误,请查找名为 StorageExplorer_AddStorageServiceSAS_v1_blob 的键。For example, if the bad SAS URI is for a blob container, look for the key named StorageExplorer_AddStorageServiceSAS_v1_blob.
  4. 键的值应为 JSON 数组。The value of the key should be a JSON array. 找到与错误 URI 关联的对象,并将其删除。Find the object associated with the bad URI, and then delete it.
  5. 按 Ctrl+R 重新加载存储资源管理器。Press Ctrl+R to reload Storage Explorer.

Linux 依赖项Linux dependencies

对齐Snap

Snap Store 中以内嵌项的形式提供了存储资源管理器 1.10.0 和更高版本。Storage Explorer 1.10.0 and later is available as a snap from the Snap Store. 存储资源管理器内嵌项会自动安装其所有依赖项,并在新版内嵌项推出时更新。The Storage Explorer snap installs all its dependencies automatically, and 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 manager, which you might need to connect manually before Storage Explorer will work correctly. 可以运行以下命令,将存储资源管理器连接到系统的密码管理器:You can connect Storage Explorer to your system's password manager by running the following command:

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

.tar.gz 文件.tar.gz File

还可以下载 .tar.gz 文件格式的应用程序,但必须手动安装依赖项。You can also download the application as a .tar.gz file, but you'll have to install dependencies manually.

仅以下 Ubuntu 版本支持 .tar.gz 下载中提供的存储资源管理器。Storage Explorer as provided in the .tar.gz download is supported for the following versions of Ubuntu only. 存储资源管理器可以在其他 Linux 发行版上运行,但未得到正式支持。Storage Explorer might work on other Linux distributions, but they are not officially supported.

  • Ubuntu 20.04 x64Ubuntu 20.04 x64
  • Ubuntu 18.04 x64Ubuntu 18.04 x64
  • Ubuntu 16.04 x64Ubuntu 16.04 x64

存储资源管理器要求在系统上安装 .NET Core。Storage Explorer requires .NET Core to be installed on your system. 建议安装 .NET Core 2.1,但存储资源管理器也可使用 .NET Core 2.2。We recommend .NET Core 2.1, but Storage Explorer will work with 2.2 as well.

备注

存储资源管理器 1.7.0 及更低版本需要 .NET Core 2.0。Storage Explorer version 1.7.0 and earlier require .NET Core 2.0. 如果安装了更高版本的 .NET Core,则必须修补存储资源管理器If you have a newer version of .NET Core installed, you'll have to patch Storage Explorer. 如果运行存储资源管理器 1.8.0 或更高版本,则至少需要 .NET Core 2.1。If you're running Storage Explorer 1.8.0 or later, you need at least .NET Core 2.1.

  1. 下载存储资源管理器 .tar.gz 文件。Download the Storage Explorer .tar.gz file.
  2. 安装 .NET Core 运行时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-transport-https && \
      sudo apt-get update && \
      sudo apt-get install -y dotnet-runtime-2.1
    

存储资源管理器所需的许多库都已随 Canonical 的 Ubuntu 标准安装进行预安装。Many libraries needed by Storage Explorer come preinstalled with Canonical's standard installations of Ubuntu. 自定义环境可能缺少其中某些库。Custom environments may be missing some of these libraries. 如果在启动存储资源管理器时遇到问题,建议确保以下包已安装在系统上:If you have issues launching Storage Explorer, we recommend making sure the following packages are installed on your system:

  • iproute2iproute2
  • libasound2libasound2
  • libatm1libatm1
  • libgconf2-4libgconf2-4
  • libnspr4libnspr4
  • libnss3libnss3
  • libpulse0libpulse0
  • libsecret-1-0libsecret-1-0
  • libx11-xcb1libx11-xcb1
  • libxss1libxss1
  • libxtables11libxtables11
  • libxtst6libxtst6
  • xdg-utilsxdg-utils

修补适用于 .NET Core 更高版本的存储资源管理器Patching Storage Explorer for newer versions of .NET Core

对于存储资源管理器 1.7.0 或更低版本,可能需要修补存储资源管理器使用的 .NET Core 版本:For Storage Explorer 1.7.0 or earlier, you might have to patch the version of .NET Core used by Storage Explorer:

  1. 从 NuGet 下载 StreamJsonRpc 版本 1.5.43。Download version 1.5.43 of StreamJsonRpc from NuGet. 在页面的右侧找到“下载包”链接。Look for the "Download package" link on the right side of the page.
  2. 下载该包后,将其文件扩展名从 .nupkg 更改为 .zipAfter you download the package, change its file extension from .nupkg to .zip.
  3. 将包解压缩。Unzip the package.
  4. 打开 streamjsonrpc.1.5.43/lib/netstandard1.1/ 文件夹。Open the streamjsonrpc.1.5.43/lib/netstandard1.1/ folder.
  5. StreamJsonRpc.dll 复制到存储资源管理器文件夹中的以下位置:Copy StreamJsonRpc.dll to the following locations in the Storage Explorer folder:
    • StorageExplorer/resources/app/ServiceHub/Services/Microsoft.Developer.IdentityService/
    • StorageExplorer/resources/app/ServiceHub/Hosts/ServiceHub.Host.Core.CLR.x64/

Azure 门户中的“在资源管理器中打开”不起作用"Open In Explorer" from the Azure portal doesn't work

如果在 Azure 门户上单击“在资源管理器中打开”按钮不起作用,请确保使用兼容的浏览器。If the Open In Explorer button on the Azure portal doesn't work, make sure you're using a compatible browser. 以下浏览器已通过兼容性测试:The following browsers have been tested for compatibility:

  • Microsoft EdgeMicrosoft Edge
  • Mozilla FirefoxMozilla Firefox
  • Google ChromeGoogle Chrome
  • Microsoft Internet ExplorerMicrosoft Internet Explorer

收集日志Gathering logs

向 GitHub 报告问题时,可能会要求你收集特定日志来帮助诊断问题。When you report an issue to GitHub, you may be asked to gather certain logs to help diagnose your issue.

存储资源管理器日志Storage Explorer logs

从版本 1.16.0 开始,存储资源管理器会将各种内容记录到其自己的应用程序日志中。Starting with version 1.16.0, Storage Explorer logs various things to its own application logs. 可以通过单击“帮助”>“打开日志目录”来轻松访问这些日志。You can easily get to these logs by clicking on Help > Open Logs Directory. 默认情况下,存储资源管理器按较低详细级别进行日志记录。By default, Storage Explorer logs at a low level of verbosity. 若要更改详细级别,请添加名称为 STG_EX_LOG_LEVEL 的环境变量以及以下任何值:To change the verbosity level, add an environment variable with the name of STG_EX_LOG_LEVEL, and any of the following values:

  • silent
  • critical
  • error
  • warning
  • info(默认级别)info (default level)
  • verbose
  • debug

日志会拆分到所运行的每个存储资源管理器会话的相应文件夹中。Logs are split into folders for each session of Storage Explorer that you run. 对于需要共享的任何日志文件,建议将它们置于 zip 存档中,并将来自不同会话的文件放在不同的文件夹中。For whatever log files you need to share, it is recommended to place them in a zip archive, with files from different sessions in different folders.

身份验证日志Authentication logs

对于与登录或存储资源管理器身份验证库相关的问题,很可能需要收集身份验证日志。For issues related to sign-in or Storage Explorer's authentication library, you will most likely need to gather authentication logs. 身份验证日志存储在以下位置:Authentication logs are stored at:

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

通常可以按照以下步骤收集日志:Generally, you can follow these steps to gather the logs:

  1. 转到“设置”>“登录”> 选中“详细身份验证日志记录”。Go to Settings > Sign-in > check Verbose Authentication Logging. 如果存储资源管理器由于其身份验证库出现问题而未能启动,则系统会为你完成此操作。If Storage Explorer is failing to launch due to an issue with its authentication library, this will be done for you.
  2. 关闭存储资源管理器。Close Storage Explorer.
  3. 可选/建议:清除 logs 文件夹中的现有日志。Optional/recommended: clear out existing logs from the logs folder. 这样做会减少必须向我们发送的信息量。Doing this will reduce the amount of information you have to send us.
  4. 打开存储资源管理器并重现问题Open Storage Explorer and reproduce your issue
  5. 关闭存储资源管理器Close Storage Explorer
  6. 压缩 log 文件夹的内容。Zip the contents of the log folder.

AzCopy 日志AzCopy logs

如果在传输数据时遇到问题,则可能需要获取 AzCopy 日志。If you are having trouble transferring data, you may need to get the AzCopy logs. 可以通过两种不同的方法轻松找到 AzCopy 日志:AzCopy logs can be found easily via two different methods:

  • 对于仍在活动日志中的失败传输,请单击“转到 AzCopy 日志文件”For failed transfers still in the Activity Log, click on "Go to AzCopy Log File"
  • 对于过去失败的传输,请转到 AzCopy 日志文件夹。For transfers that failed in the past, go to the AzCopy logs folder. 可在以下位置找到此文件夹:This folder can be found at:
    • Windows: C:\Users\<your username>\.azcopyWindows: C:\Users\<your username>\.azcopy
    • macOS 和 Linux `~/.azcopymacOS and Linux `~/.azcopy

网络日志Network logs

对于某些问题,需要提供存储资源管理器进行的网络调用的日志。For some issues you will need to provide logs of the network calls made by Storage Explorer. 在 Windows 上,可以使用 Fiddler 执行此操作。On Windows, you can do this by using Fiddler.

备注

Fiddler 跟踪可能包含在收集跟踪期间在浏览器中输入/发送的密码。Fiddler traces may contain passwords you entered/sent in your browser during the gathering of the trace. 请确保阅读有关如何清理 Fiddler 跟踪的说明。Make sure to read the instructions on how to sanitize a Fiddler trace. 请勿将 Fiddler 跟踪上传到 GitHub。Do not upload Fiddler traces to GitHub. 系统会告诉你可以安全发送 Fiddler 跟踪的位置。You will be told where you can securely send your Fiddler trace.

第 1 部分:安装和配置 FiddlerPart 1: Install and Configure Fiddler

  1. 安装 FiddlerInstall Fiddler
  2. 启动 FiddlerStart Fiddler
  3. 转到“工具”>“选项”Go to Tools > Options
  4. 单击“HTTPS”选项卡Click on the HTTPS tab
  5. 请确保已选中“捕获连接”和“解密 HTTPS 流量”Make sure Capture CONNECTs and Decrypt HTTPS traffic are checked
  6. 单击“操作”按钮Click on the Actions button
  7. 选择“信任根证书”,然后在下一个对话框中选择“是”Choose "Trust Root Certificate" and then "Yes" in the next dialog
  8. 再次单击“操作”按钮Click on the Actions button again
  9. 选择“将根证书导出到桌面”Choose “Export Root Certificate to Desktop”
  10. 转到桌面Go to your desktop
  11. 找到 FiddlerRoot.cer 文件Find the FiddlerRoot.cer file
  12. 双击以打开Double-click to open
  13. 转到“详细信息”选项卡Go to the "Details" tab
  14. 单击“复制到文件...”Click "Copy to File…"
  15. 在导出向导中,选择以下选项In the export wizard choose the following options
    • Base-64 编码的 X.509Base-64 encoded X.509
    • 对于文件名,浏览…For file name, Browse… 到 C:\Users<your user dir>\AppData\Roaming\StorageExplorer\certs,然后可以将它保存为任何文件名to C:\Users<your user dir>\AppData\Roaming\StorageExplorer\certs, and then you can save it as any file name
  16. 关闭证书窗口Close the certificate window
  17. 启动存储资源管理器Start Storage Explorer
  18. 转到“编辑”>“配置代理”Go to Edit > Configure Proxy
  19. 在对话框中,选择“使用应用代理设置”,并将 URL 设置为 http://localhost ,将端口设置为 8888In the dialog, choose "Use app proxy settings", and set the URL to http://localhost and the port to 8888
  20. 单击“确定”Click Ok
  21. 重启存储资源管理器Restart Storage Explorer
  22. 你应开始看到来自 storageexplorer: 进程的网络调用显示在 Fiddler 中You should start seeing network calls from a storageexplorer: process show up in Fiddler

第 2 部分:重现问题Part 2: Reproduce the issue

  1. 关闭除 Fiddler 以外的所有应用Close all apps other than Fiddler
  2. 清除 Fiddler 日志(左上角的 X 图标,“视图”菜单附件)Clear the Fiddler log (X icon in the top left, near the View menu)
  3. 可选/建议:让 Fiddler 设置几分钟,如果看到网络调用出现,请右键单击它们,然后选择“立即筛选”>“隐藏 ”Optional/recommended: let Fiddler set for few minutes, if you see network calls appear, right-click on them and choose 'Filter Now' > 'Hide '
  4. 启动存储资源管理器Start Storage Explorer
  5. 再现问题Reproduce the issue
  6. 单击“文件”>“保存”>“所有会话…”,保存在不会忘记的某个位置Click File > Save > All Sessions…, save somewhere you won't forget
  7. 关闭 Fiddler 和存储资源管理器Close Fiddler and Storage Explorer

第 3 部分:清理 Fiddler 跟踪Part 3: Sanitize the Fiddler trace

  1. 双击 fiddler 跟踪(.saz 文件)Double-click on the fiddler trace (.saz file)
  2. ctrl+fPress ctrl+f
  3. 在出现的对话框中,确保设置了以下选项:“搜索”=“请求和响应”,“检查”=“标头和正文”In the dialog that appears, make sure the following options are set: Search = Requests and responses, Examine = Headers and bodies
  4. 搜索在收集 fiddler 跟踪时使用的任何密码,突出显示所有条目,右键单击,然后选择“删除”>“所选会话”Search for any passwords you used while collecting the fiddler trace, any entries that are highlighted, right-click and choose Remove > Selected sessions
  5. 如果在收集跟踪时确实在浏览器中输入了密码,但在使用 ctrl + f 时找不到任何条目,并且不希望更改密码/所用的密码还用于其他帐户,则可以跳过向我们发送 .saz 文件。If you definitely entered passwords into your browser while collecting the trace but you don't find any entries when using ctrl+f and you don't want to change your passwords/the passwords you used are used for other accounts, then feel free to just skip sending us the .saz file. 安全第一。Better to be safe than sorry. :):)
  6. 使用新名称再次保存跟踪Save the trace again with a new name
  7. 可选:删除原始跟踪Optional: delete the original trace

后续步骤Next steps

如果这些解决方案都无效,你可以:If none of these solutions work for you, you can:

  • 创建支持票证Create a support ticket
  • 在 GitHub 上提问Open an issue on GitHub. 也可以选择左下角的“向 GitHub 报告问题”按钮。You can also do this by selecting the Report issue to GitHub button in the lower-left corner.

反馈