We recently upgraded to ProGet 2025, and even just now updated to 25.0.1 to make sure this wasn't already fixed.
For full context, we also migrated from sqlserver to postgres with the built-in wizard and have performed the integrity scans along with reindexes where it was recommended. We also moved to using IIS as the https proxy to where proget is now running on the integrated web server as was required for 2025. (Side note, kudos on all the documentation and guides that made that transition much easier than expected).

Onto the bug.

We have a version metadata entry on basically all of our asset repo items. Previously, editing this worked as expected, now we get this behavior:

We click version and we get:

Instead of seeing the current content. If we try to overwrite it like

we get

if we don't check the box same thing

We are able to add a new metadata with a different name and we can workaround this by deleting the old metadata entry and creating it anew.

I would also note that it no longer auto-updates/refreshes the page, have to manually refresh to see metadata changes, not that big of a deal but worth noting.

===What version does this affect?===
ProGet 2024.28, 2024.29 (Inedo Hub)

===How can we help? (in brief)===
When trying to browse files of a package it just errors out

===Please add any details that might help us help you.===
If we go to a powershell or chocolatey package in Proget 2024.28 or 2024.29 we can no longer view the contents of the nupkg file.
We use this feature as part of some imaging/provisioning automation to get a pkgs.txt file to know what programs are to be installed.
i.e. we might run invoke-restmethod on a url like this one:

https://domain.proget.url/package-files/download?feedName=Choco&group=&packageId=some-package&version=2503.1.6&path=tools%2Ffiles%2Fpkgs.txt&download=false

But right now that returns "ERROR: File not found" breaking our system provisioning. If we browse to the page in the web ui we see

We use this method so we don't have to store a list of packages in 2 places and can maintain it within a package. I imagine there are other use cases out there for browsing or getting the package contents.

@stevedennis said in Proget Service/Site Crashes with 500 Error:

shared memory provider error 40

Thank you for the insights, I was also thinking the sql server was the most significant thing. It is on the same server but it's also a virtual server, I don't think it's a hardware failure there.

There is another sql server running on the server for chocolatey central management, there may have been a conflict with a mismatched version dependency on that app for the dotnet-aspnetmodule-v2 where I need the 16.x version for CCM but I accidentally upgraded to the 17.x version.

At the moment the issues hasn't recurred since the day I reported it and I'm hoping having fixed that dependency has fixed the issue. I found some other things that mention local sql aliases needing to exist, I do use many dns aliases in the server's config so I might try making those as sql named pipe aliases to see if that makes any difference, though it seems a long shot.

I can't attach a zip of the events so here are some screenshots

IIS AspNetCoreModuleV2 Error Code 1018

IIS AspNetCoreModuleV2 Error Code 1007

CertificateServicesClient-CertEnroll Error 86

.NET Runtime Error 1026

Service Control Manager Error 7031

===What version does this affect?===
ProGet 2023.13 (Inedo Hub)

===How can we help? (in brief)===
[Major] Service keeps crashing taking site down every few days

===Please add any details that might help us help you.===
On a fairly regular basis our proget site is crashing and giving a 500 error. It's often happening in the wee hours of the morning.
Sometimes it's fixed by a restart of just the proget service
Sometimes it's a restart of the service and the site
Sometimes it's a restart of the whole iis server service

We're also able to bring it back up but it shouldn't be randomly crashing.

When checking in the event log we see a few things and I am attaching saved versions of those logs so you can see them in more detail.
Around the same time as things crash there are winrm and certificate related errors (we're not doing anything special that we know of with certificates and winrm) and we see an error saying the proget service couldn't connect to the sql server