search

winget-run / wingetdotrun

📦 Finding winget packages made easy 🔍
https://winget.run
465 stars 10 forks source link

[BUG] https://winget.run/ not working at all [BUG] #33

Closed officialmmt closed 1 year ago

officialmmt commented 1 year ago

It was working for a while but now not working.

image image

gregwen commented 1 year ago

I came here for just this purpose. Thanks for posting

adnanaylan commented 1 year ago

I get the same error.

chewgun commented 1 year ago

same for me.. since 2 weeks nothing..

Frxhb commented 1 year ago

Same error. Even API Requests are not working.

ToasterUwU commented 1 year ago

Same here

ahdncordeiro commented 1 year ago

I found the https://winstall.app/apps that has the same functionality and is working.

OmriYaHoo commented 1 year ago

I found the https://winstall.app/apps that has the same functionality and is working.

Thanks for the recommendation, gonna switch to this for now. A bit weird the team behind the website hasn't noticed/ignore this issue.

It's also mentioned here - #32

Frxhb commented 1 year ago

I found the https://winstall.app/apps that has the same functionality and is working.

Almost... API requests as in winget.run aren't working 😐

griesi007 commented 1 year ago

@Dragon1320 @MattheousDT Are you aware that winget.run is down and not usable currently?

chewgun commented 1 year ago

Does the certificate issue from WinGet impact as well the winget.run site? https://www.bleepingcomputer.com/news/security/microsoft-winget-package-manager-failing-from-expired-ssl-certificate/

MattheousDT commented 1 year ago

Thanks for the ping. Didn't see this in my notifications. Currently looking into it. Will keep you posted.

MattheousDT commented 1 year ago

The API and website are back up. We redeployed our kubernetes cluster and freshly regenerated our database. Statistics are therefore reset.

Sorry to everyone who couldn't use the site over the last week or so. We're going to set up some tracking for this stuff (and also fixing our github notifications) so that we can be alerted if anything like this happens in the future. Soon™ we'll dig into a rewrite since our setup is overly complex and a bit fragile.