Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions powershell-gallery/docs-conceptual/getting-started.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
description: This article explains how to get started using the PowerShell Gallery and the PowerShellGet cmdlets
ms.date: 06/19/2025
ms.date: 09/09/2025
ms.topic: get-started
title: Get Started with the PowerShell Gallery
---
Expand Down Expand Up @@ -128,6 +128,8 @@ installed directly from the PowerShell Gallery.

## Network access to the PowerShell Gallery

[!INCLUDE [TLS 1.2 Requirement](../includes/tls-gallery.md)]

These hostnames should be added to the allow lists that control access from your network.

Hosts required for package discovery and download:
Expand All @@ -140,7 +142,9 @@ Hosts required when using the PowerShell Gallery website:
- `*.powershellgallery.com` - website
- `go.microsoft.com` and `aka.ms` - redirection services

[!INCLUDE [TLS 1.2 Requirement](../includes/tls-gallery.md)]
> [!NOTE]
> These endpoints have changed. The old endpoints that ended with `azureedge.net` are no longer
> supported.

## Related links

Expand Down
Original file line number Diff line number Diff line change
@@ -1,46 +1,50 @@
---
description: This article provide information and steps for troubleshooting errors using the PowerShell Gallery
ms.date: 06/12/2025
ms.date: 09/09/2025
title: Troubleshooting cmdlets
---
# Troubleshooting cmdlets

## How to resolve "WARNING: Package 'your package name' failed to download" issue

It is reported that `Install-Module` or `Update-Module` sometimes fails on some machines. Based on
our investigation, it is something to do with the networking connection. Recently we updated NuGet
provider so that it can reliably download packages. You can follow the instructions below to install
the latest build of NuGet provider and then install or update your module. Let's use 'Azure' module
as an example below.
The `Install-Module` or `Update-Module` commands sometimes fail. Based on investigations, it's
usually a networking problem. Ensure that you are using TLS 1.2 or higher and that your firewall
rules allow access to the required network endpoints.

[!INCLUDE [TLS 1.2 Requirement](../../../includes/tls-gallery.md)]

The NuGet provider was updated to improve reliably. Use the following instructions to install the
latest build of NuGet provider and then install or update your module.

```powershell
Install-PackageProvider NuGet -MinimumVersion 2.8.5.206 -Force
Launch new PowerShell Console
Update-Module Azure -Verbose
```

## Required network endpoints

The Install and Update cmdlets require internet access to connect to the network endpoints used by
the PowerShell Gallery. Ensure that your network access policies allow you to connect to TCP port
443 of the following endpoints.
The `Install-*` and `Update-*` cmdlets require internet access to connect to the network endpoints
used by the PowerShell Gallery.

Ensure that your network access policies allow you to connect to TCP port 443 of the following
endpoints.

Hosts required for package discovery and download:

- `cdn.oneget.org` - CDN hostname
- `cdn.powershellgallery.com` - CDN hostname
- `cdn.oneget.org`
- `cdn.powershellgallery.com`

Hosts required when using the PowerShell Gallery website:

- `devopsgallerystorage.blob.core.windows.net` - storage account hostname
- `*.powershellgallery.com` - website
- `go.microsoft.com` - redirection service
- `go.microsoft.com` and `aka.ms` - redirection services

> [!NOTE]
> Cmdlets that interact with the PowerShell Gallery can fail with unexpected errors when there is an
> outage of the PowerShell Gallery services. To see the current status of the PowerShell Gallery,
> see the [PowerShell Gallery Status][01]
> page on GitHub.
> These endpoints have changed. The old endpoints that ended with `azureedge.net` are no longer
> supported.

Cmdlets that interact with the PowerShell Gallery can fail with unexpected errors when there is an
outage of the PowerShell Gallery services. To see the current status of the PowerShell Gallery, see
the [PowerShell Gallery Status][01] page on GitHub.

<!-- link references -->
[01]: https://github.com/PowerShell/PowerShellGallery/blob/master/psgallery_status.md
16 changes: 6 additions & 10 deletions powershell-gallery/includes/tls-gallery.md
Original file line number Diff line number Diff line change
@@ -1,20 +1,16 @@
---
author: sdwheeler
ms.author: sewhee
ms.date: 11/18/2020
ms.date: 09/09/2025
ms.topic: include
---
<!-- markdownlint-disable first-line-h1 -->
> [!IMPORTANT]
> As of April 2020, the PowerShell Gallery no longer supports Transport Layer Security (TLS)
> versions 1.0 and 1.1. If you are not using TLS 1.2 or higher, you will receive an error when
> trying to access the PowerShell Gallery. Use the following command to ensure you are using TLS
> 1.2:
> The PowerShell Gallery requires Transport Layer Security (TLS) 1.2 or higher. If you are not using
> TLS 1.2 or higher, you will receive an error when trying to access the PowerShell Gallery. Use the
> following command to ensure you are using TLS 1.2:
>
> ```powershell
> [Net.ServicePointManager]::SecurityProtocol = [Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Tls12
> [Net.ServicePointManager]::SecurityProtocol =
> [Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Tls12
> ```
>
> For more information, see the
> [announcement](https://devblogs.microsoft.com/powershell/powershell-gallery-tls-support/) in the
> PowerShell blog.
Loading