Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login
    1. Home
    2. kigiwow570_6179
    3. Topics

    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!

    K Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 2
    • Groups 0

    Topics

    • K

      nuget.org connector throving NuGet v2 Bad Request

      Watching Ignoring Scheduled Pinned Locked Moved Support
      2
      2
      0 Votes
      2 Posts
      9 Views
      dean-houstonD
      Hi @kigiwow570_6179 , These errors are being "forwarded" from NuGet.org, and if you're seeing them it means that "something" on your network is making requests to a ProGet feed that has a connector to nuget.org. This is typically an old, outdated tool or script. You'll need to track this down and update/disable it. It could also be a self-connector that is connecting to a feed that also has a connector to ProGet using the V2 APi - so double check your self-connectors. Best, Dean
    • K

      Connector showing error in logs if package doesn't exist in feed

      Watching Ignoring Scheduled Pinned Locked Moved Support
      2
      0 Votes
      2 Posts
      5 Views
      dean-houstonD
      Hi @kigiwow570_6179, I don't have enough information/specifics to answer the questions; it really depends on the API queries being made, etc. Some API calls result in errors, others do not. In general, doing a NuGet restore will not result in errors being logged. Best, Dean
    • 1 / 1