Repository navigation
Powershell Gallery is returning 503 #135
Description
Activity
Same here with Pester and other modules
Having similar problem installing PSScriptTools, our build pipelines failing as a result.
Same behavior on my side
I am getting a 503 error when trying to pull any modules down at the moment
Modules cannot be pulled from the PowerShell Gallery at the moment. The PowerShell Gallery seems to be unavailable for at least a few hours already.
Reacted by buckthebug, Martin Brown, Peter Palotas, Ashley How, Bahman Nikkhahan, Igor Shenderchuk and Dennis BasarginIs there any official websites for PowerShell Gallery status?
It is hard to know that it is down or just an internet error.Reacted by buckthebug, Nasir Amin and SeaBinTApphttps://github.com/PowerShell/PowerShellGallery/blob/master/psgallery_status.md
Although nothing on there as yet for this
Reacted by Petr Ježek and andy1Q7Hi all, we currently have an outage and are working on resolving it. Our CDN is down preventing packages from being downloaded and availability for the gallery itself has been extremely low. I'll update here as mitigation steps progress.
Reacted by staedter, Dennis van Doorn, Martin Brown, amo, Ryan, Arie, Ron Hernaus, Markus Lindström, buckthebug, Jan Hajek and 23 moreSame problem here
PowerShellGallery has become a essential resource for many. It's been unstable and have had other problems for months.
alerickson : Is Microsoft comitting to making PowerShellGallery a reliable resource for PowerShell modules in near future, or do we have to look for other solutions (like GitHub maybe) for reliably hosting PowerShell modules?
Reacted by Markus Lindström, Martin Brown, Chris Blank, Dembeck, Jan Hajek, staedter, buckthebug, Peter Palotas, Ashley How, Mitchell Skaggs and 11 morePowerShellGallery has become a essential resource for many. It's been unstable and have had other problems for months.
alerickson : Is Microsoft comitting to making PowerShellGallery a reliable resource for PowerShell modules in near future, or do we have to look for other solutions (like GitHub maybe) for reliably hosting PowerShell modules?
I want to second the sentiment. Our CI/CD Pipelines quite heavily rely on the availability of multiple third-party modules that are primarily hosted on PS Gallery... I guess we should try to get rid of that single point of failure but Microsoft also should be doing more to guaranty the availability of something so vital to a lot of people.
Although I personally appreciate that alerickson gave us the first official information about the problem from the responsible team from Microsoft, I think they should be doing a better job at communicating outages and mitigation progress than replying on Github issues.
Reacted by Markus Lindström, Jan Hajek, Martin Brown, Peter Palotas, buckthebug, salascz, possibly0784, Nasir Amin, SeaBinTApp, Amy Jeanes and 7 moreI concur I have a change which is reliant on me pulling a module down to a new server so this is eating away at my change window.
Reacted by buckthebug and Peter Palotasfacing same issue. Our ADO pipelines relies on powershell gallery for ps module. when we can aspect fix. Same kind of issue was observed few days back, but it was fixed by India Noon time on that day.
Same here..
Same here. Need to install Docker on a new server and therefore need psgallery to install my modules. Can't work on this server now..
46 remaining items
Soooo.... Funny how I planned to get around and set up a local repo today for situations like these :')
Well then. Time for the weekend!
Good luck PSGallery admins 😅
Reacted by Francis Grignon and Paul RobichaudThis doesn't work for me
I've been trying to install the Get-WindowsAutopilotInfo script for 1 hour then realised the powershell gallery wasn't loading. Had 19 laptops setup to start building! Can't believe it!
Will try again tomorrow and go get some pizza for now .
Reacted by providynClosing to reopen, to rerun CI.
Reopening to rerun CI.
(argh. wrong window. :P)
Reacted by SGC and Andy BlateckyReacted by Arie, Peter Palotas, Simon D'Morias and Petr Ježek- Reacted by Valters Jansons
Works in Europe! Tested it with SQLServer module
Reacted by Sydney SmithThanks, we are currently validating the changes before updating the incident as mitigated
It looks like it might be the index that is out of date. I can’t republish the newer version
Thanks folks we have mitigated the outage-- please refer to https://github.com/PowerShell/PowerShellGallery/blob/master/psgallery_status.md for more details, we will follow up with a post-mortem
Reacted by Bergot and Peter PalotasReacted by Ted ChambersGoing to close out this issue, please let us know if you are still experiencing any issues
Hi Team,
I am getting that problem from yesterday evening. Do you have any updates?
PS C:\Program Files\PowerShell\7-preview> [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.SecurityProtocolType]::Tls12
PS C:\Program Files\PowerShell\7-preview> Install-Module -Name DataGateway
WARNING: Unable to resolve package source 'https://www.powershellgallery.com/api/v2'.
Install-Package: C:\program files\powershell\7-preview\Modules\PowerShellGet\PSModule.psm1:9711
Line |
9711 | … talledPackages = PackageManagement\Install-Package @PSBoundParameters
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| No match was found for the specified search criteria and module name 'DataGateway'. Try
| Get-PSRepository to see all available registered module repositories.
Powershell Gallery is returning 503. I can't currently run https://github.com/powershell/powershell tests because they try to pull Pester from it.