Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
NuGet push API key no longer working after upgrade
-
Yesterday we upgraded from ProGet 5.0.12 to 5.1.3. We have had ProGet (free version) installed for ages, since an early version (v2 or 3 I can't remember), that has been upgraded regularly.
We have a local feed that our build server pushes to every night using an API key from the nuget command line.
After upgrade, all pushes failed last night with InternalServerError and errors logged on the server: "An error occurred processing a PUT request to http://ourinternalurl.net/nuget/internal/: This operation requires IIS integrated pipeline mode."
I read elsewhere this was fixed in the new version so we have now upgraded to 5.1.4.
However, we are now getting Unauthorized errors from the nuget command line on the build server ("Please provide credentials for http://ourinternalurl.net UserName: Password: Object reference not set to an instance of an object.") and nothing logged on the server.
It looks like our NuGet API key has disappeared from ProGet, and I can't figure out where or how to put it back (It was first configured several years back.)
I also cannot currently access your documentation site as https://inedo.com/support/documentation/proget is giving me the error "Index was outside the bounds of the array."
Please help.
Product: ProGet
Version: 5.1.4 -
Documentation site came back up, so according to https://inedo.com/support/documentation/proget/feeds/nuget#nuget-api-key we created a new dedicated user for the build server and are now using username:password as the API Key.
No more problem. Thanks.
-
I had the same issue as you, so I upgraded to 5.1.4 (thanks for that info!) and the error did indeed disappear. On the other hand, another error took its place:
"Cannot prompt for input in non-interactive mode."I've been using an ApiKey in the username:password format for quite a while now and it has been working flawlessly. Any idea what could help?
Thanks
-
Turns out I needed to migrate the feed to the "new format" that supports semver. Everything worked like a charm afterwards.
Thanks
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login