PowerShell
Web page search returns no results
Prerequisites
- [x] Write a descriptive title.
- [x] Make sure you are able to repro it on the latest version
- [x] Search the existing issues.
Steps to reproduce
Seems this happens quite frequently. 🤔
- 2025-01-31: https://github.com/PowerShell/PowerShellGallery/issues/305
- 2024-08-17: https://github.com/PowerShell/PowerShellGallery/issues/289
- 2024-07-17: https://github.com/PowerShell/PowerShellGallery/issues/282
- 2022-10-24: https://github.com/PowerShell/PowerShellGallery/issues/239
- 2018-09-19: https://github.com/PowerShell/PowerShellGallery/issues/25
Expected behavior
Results
Actual behavior
No results
Error details
Environment data
Not relevant
Version
Not relevant
Visuals
No response
It seems the issue has been resolved. Currently, the search is working stably. Update: No sooner had I written this than subsequent search checks stopped returning results.
This is currently happening for me right now, which led me here, only to find it's a frequent on-going issue..... The lack of responses from MS since this was opened months ago is a bit worrying, does anyone check this repo?
I've confirmed from testing on different devices (even different ISP's) that this is not a client side issue.
There are multiple things that can affect stability the last days.
Azure Front Door (the CDN in front of PowerShell Gallery) has had problems recently:
There seems to be a halt / freeze, in that customers can't push new configuration to Front Door for another two days ( 😅 ).
And the PowerShell team is modernizing PowerShell Gallery to run on Azure Kubernetes Services (AKS), ref. community call notes from 2025-05-15:
Here are some workarounds for when PowerShell Gallery is down:
@alerickson care to comment? 😊 Can we expect PSG to become more stable in the foreseeable future, or do those that rely on it have to implement fallback strategies?
Thanks for the detailed reply. I think what may go a long way would also be some way to gracefully handle when this happens, for example, an error message to indicate there's a temporary issue to visitors, rather than just no results being returned like everything is ok. It might also appease others who are likely to look for ways to contact MS about the issue.
Same issue as of right now (2026/01/04 12:25 ET), a month later after the last person reported it. I find it hard to believe that the default PSResource repository is constantly and persistently down since years. I have experienced it personally many times over the past several years. It would be like if GitHub just didn't work half the time so no one could find anything to clone anything or build anything or get their dependencies. Does no one notice that at Microsoft?
I was an early adopter of PowerShell in the 2000's and am one of its biggest fans. Love the eco-system so this kind of bad publicity distresses me! Looking forward to the fruits of the labors of those working to modernize the gallery. In the meantime, I hope they can make things stable so that new people thinking to adopt PowerShell are not turned away.
== UPDATE== It's back up. If someone listened and acted, thank you.
