Hey @stevedennis ,
That's my bad I blurred too much. The "/feeds/" part was there too. I poked our IT team to see if there could be any weird settings on our IIS server or the network itself.
Sometimes our Proget page gets super slow too and we even get 502 errors so there might be something wrong in our setup.
I'll keep you updated if I find anything.
Thanks again
Hello @atripp
I did a test an tried to go on the page being on the server where proget is hosted and it worked :
If I try from my workstation I get the error message :
It's really weird since it happens only with this package. Others from the public Nuget feeds works just fine.
I guess we'll have to dig a bit deeper on our end if we can find and explanation. If you have any ideas let us know :)
Thanks again for your support,
Nicolas
Hey @rhessinger,
I'm using Version 6.0.7 (Build 5). I updated Proget when I faced this problem so it should be the latest right?
When I click on the Puma.Security.Rules package in the list :
That's when I'm sent to the 404 - File or directory not found. page.
I checked the Diagnostic Center while doing that and nothing showed up. Well there's something but it's about one of our connectors that needs to be fixed so no link with that.
Hey Alana,
Thanks for your answer.
Unfortunately, for this kind of issue I've been able to fix it by myself but now is a different case. Now my problem is that I can't even access the Puma.Security.Rules package page where I can see the versions and try to use the "delete cached package". As soon as I click on the Puma.Security.Rules in the NuGet lists from the UI I get that 404 error page.
Seems to be a level higher than that.
Hey there,
We have a weird issue with 1 NuGet package on our feed : Puma.Security.Rules
It comes from https://www.nuget.org/packages/Puma.Security.Rules/ and we have a connector to this public feed that usually works flawlessly.
We see the package listed on the feed :
But if we try to go on this package page we hit a 404 not found page:
I tried to add a version manually to the feed so it's in the local cache and even that didn't work.
I never had this issue before and I don't want to break it even more
Thanks,
Nicolas