Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    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!

    503 Error when accessing feeds from nuget.exe or Visual Studio

    Scheduled Pinned Locked Moved Support
    errorsiisnugetproget
    6 Posts 1 Posters 116 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ? This user is from outside of this forum
      Guest
      last edited by

      When I attempt to access my ProGet feeds through Visual Studio or nuget.exe it errors out with a 503 error.
      I am using:

      • LDAP authentication
      • Integrated Authentication
      • IIS Hosted
      • With custom AppPool identity which has access to my database and filesystem

      Product: ProGet
      Version: 3.5.5

      1 Reply Last reply Reply Quote 0
      • ? This user is from outside of this forum
        Guest
        last edited by

        What version of NuGet are you using?

        Also- did this used to work, or is this the first time you are trying it?

        1 Reply Last reply Reply Quote 0
        • ? This user is from outside of this forum
          Guest
          last edited by

          I'm using nuget 2.8. Come to think of it hasn't worked. I had to manually upload packages previously and I never tried adding ProGet as a package source.

          The interesting thing is I tried installing to a different machine and I get the same problem.

          1 Reply Last reply Reply Quote 0
          • ? This user is from outside of this forum
            Guest
            last edited by

            Strange. Well, an HTTP 503 pretty much has to be coming from IIS rather than ProGet itself, as we don't explicitly return that error code at all. It might be useful to record a Fiddler trace to see what URLs NuGet is trying to connect to, and to see if the server returns any more information that isn't being displayed.

            1 Reply Last reply Reply Quote 0
            • ? This user is from outside of this forum
              Guest
              last edited by

              I also tried going the non-IIS route and I was getting the same behavior.

              1 Reply Last reply Reply Quote 0
              • ? This user is from outside of this forum
                Guest
                last edited by

                So upon doing a fiddler trace and seeing nothing coming through when I used nuget.exe against our internal repo, I tried it against nuget.org and lo and behold that failed too.
                It turns out for prior things I had HTTP_PROXY and HTTPS_PROXY environment variables set and nuget.exe didn't like it. This carried over to Visual Studio as well. After removing those variables everything started working again.

                So, sorry this wasn't ProGet at all (thankfully).

                1 Reply Last reply Reply Quote 0

                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
                • 1 / 1
                • First post
                  Last post
                Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation