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!

    Cannot access default ProGet installation via public IP - only localhost

    Scheduled Pinned Locked Moved Support
    integrated-web-serverproget-installationproget
    5 Posts 3 Posters 57 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

      Hi,
      I ran through and did a default installation of ProGet (all default options) on Windows Server 2016.
      I am able to browse to the ProGet web application via localhost on http://localhost:8624 but when I try to browse to it using the public IP address of the server I cannot get to it. Chrome responds with ERR_CONNECTION_TIMED_OUT.
      I am trying to get to the public IP via the browser on the server using remote desktop. So it shouldn't be a network access issue. Even so, I have tested that I have access to the server over port 8624 from my remote machine, and it appears to be open.
      Ideas?

      Product: ProGet
      Version: 5.0.13

      1 Reply Last reply Reply Quote 0
      • T Offline
        thoven
        last edited by

        Does the public IP actually resolve to to that server internally?

        Only other thought is that it's an HTTP URL reservation issue (maybe localhost was explicitly registered instead of * somehow). You can check by running the following from PowerShell:

        netsh http show urlacl | ?{ $_ -like "*:8624*" }
        
        1 Reply Last reply Reply Quote 0
        • ? This user is from outside of this forum
          Guest
          last edited by

          Any up for this case ?
          I have the same issue...

          http://localhost:8624/ : OK work

          http://fqdn:8624/ : KO, error 503

          1 Reply Last reply Reply Quote 0
          • atrippA Offline
            atripp inedo-engineer
            last edited by

            Hello; please check out this KB article for help on how to update the urls.

            https://inedo.com/support/kb/1014/changing-an-inedo-products-url-with-the-integrated-web-server

            Alternatively, you can use IIS, which will be easier for your web admins to maintain.

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

              Ok, I use this KB 2 days ago and i added netbios name, fqdn but same problem.
              I try to change the user context but same pb.

              Error 503 - service unvailabable

              I will change my stack of web and i will go to install IIS...but is strange for an editor to indicate don't use "web integrade proget server"

              Thanks.

              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