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!

    NuGet Feed API Endpoint URL Returns 404

    Scheduled Pinned Locked Moved Support
    networknugetapi
    3 Posts 2 Posters 9 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.
    • C Offline
      cole.bagshaw_3056
      last edited by

      I have created a Proget instance with a NuGet feed and am trying to access the packages hosted there. However, when I try to access the API endpoint URL provided in the feed, the server returns a 404 error. I'm having difficulty troubleshooting the issue as I'm not sure why the web interface would be accessible, but the API end point would not be. Any help would be much appreciated.

      Thanks

      Response when attempting to send a GET request to the API endpoint URL:

      <html>
      <head><title>404 Not Found</title></head>
      <body>
      <center><h1>404 Not Found</h1></center>
      <hr><center>nginx/1.18.0 (Ubuntu)</center>
      </body>
      </html>
      
      stevedennisS 1 Reply Last reply Reply Quote 0
      • stevedennisS Offline
        stevedennis inedo-engineer @cole.bagshaw_3056
        last edited by

        Hi @cole-bagshaw_3056 ,

        The web interface and API are powered by the same program (the ProGet web server application), so if the UI is accessible so would the API, as you noticed.

        In this case, this error message is coming from your reverse proxy (NGINX); I would check with your configuration there, as something is misconfigured.

        The first and most obvious thing I would check is the hostname/port of your URLs. It's possible that you're accessing different hosts/domains. This is controlled by the X-Forwarded headers.

        Hope that points you in the right direction

        Cheers,
        Steve

        1 Reply Last reply Reply Quote 0
        • C Offline
          cole.bagshaw_3056
          last edited by

          Hi @stevedennis,

          Thanks for the reply. It turns out my default nginx server was intercepting all http traffic and not allowing requests to get to the Proget server.

          I solved the issue by disabling the default server (removing it from sites-enabled) and making some config changes to the Proget nginx config file to stop the server from redirecting http traffic to https.

          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