PowerShell/PowerShellGallery

Web page search returns no results

Opened this issue Β· 13 comments

Prerequisites

  • Write a descriptive title.
  • Make sure you are able to repro it on the latest version
  • Search the existing issues.

Steps to reproduce

Image

Seems this happens quite frequently. πŸ€”

Expected behavior

Results

Actual behavior

No results

Error details

Environment data

Not relevant

Version

Not relevant

Visuals

No response

Now it works again. Maybe this should be looked into?

Doesn't work for me:

Image

with all filters:

Image

Not working for me either. Sign in also doesn't work. 500 error.

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.

Kvoo commented

Not working for me either.

Not working still/again

Not working again

Search bar still showing zero results.

Still not working :(

Oops!…It Did It Again 😁 (Not working)

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.