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!
How to change ProGet to run on specific IP address and port
-
Hi guys,
we are evaluating ProGet 5.1 free - currently running using the built-in web server.
The install is on a Windows Server 2012 with multiple IP addresses assigned. I want to run the ProGet server on a specific IP address (not the default one), and on port 80.
But I cannot see how to change the configuration. When I use the inedo hub settings the entry field it won't accept any other values that the default.
I had also previously tried installing and using IIS - but could't get that to work at all.
Do you have any suggestions?
Dwight
Product: BuildMaster
Version: 6.0.6 -
Hello, please refer to this article on how to change it;
https://inedo.com/support/kb/1014/changing-an-inedo-products-url-with-the-integrated-web-server
-
I tried following the instructions on the website but this does not make any difference. From reading the KB article and some experimentation I assume that the command to add another IP/Port binding for ProGet is:
ProGet.System.exe --reserveurls --url=http://<hostname>:<port>
After this I used the command to check the reservation worked:
ProGet.System.exe --listreservations
This shows the new reservation, as well as a bunch of other ones.
After this I restarted the services (ProGet Service and ProGet Web Server), and tried the new binding in a web browser. But the browser cannot connect to the server.
I checked the server is running by browsing to the default port 8624, and I get the ProGet home page as expected.
Is there another step required?
Should I unbind the default binding (Port 8624)?
This is different to the description in the article - looks like the product has been changed since this page was written?
-
That's really all that you should have to do; the bindings are handled with HTTP.SYS, which then passes the request to the process. If it works on one binding, it should work on all bindings. Maybe try rebooting (no idea why that would change it, but..) and maybe it could be a firewall that's blocking it...
It might be easier to upgrade to IIS however.
-
Hmm - I will try rebooting, don't think I have tried that yet.
Actually I tried IIS before trying the built-in web server, but couldn't get that to switch to a different IP or Port either.
Is not a firewall issue since I've been testing access to the new IP & Port from a browser running on the server.
Is there any diagnostic or log I can check to see if the built-in web server is having trouble opening the port?
-
It sounds like problem is most certainly a network configuration problem.
The IWS will crash / fail to start if it can't register the specified URL (i.e. "open the port" via HTTP.SYS), and IIS will similarly refuse to start a site. So, if this is not happening, then the problem is not in IIS/IWS. Keep in mind that all of this happens with a kernel-level operating system component (HTTP.SYS) , and while it's possible that your OS is broken, I've never seen it.
I think it's either a networking or proxy issue. Just because you're using a browser on the serve doesn't mean it's doing a loopback, and doesn't mean Windows firewall isn't blocking it. So, please continue to investigate your server configuration and you fill it.
Once you do, please post to this group and share an update :) -
The Windows Firewall is turned off.
There is no proxy server running in our network.
I'm just rebooting the PC to see if this makes any difference. Will update when that is done...
Is there any diagnostic or log I can check to see if the built-in web server is having trouble opening the port?
-
As an aside, if you received a "site cannot be started" error from IIS, see:
-
I gave up trying to use the built-in web server and went back to using IIS.
After some investigation I realised that our IIS instance was setup for specific IP addresses only (not the default behaviour), and the new IP added for proget was not in the list.
This situation and how to manage the bindings for IIS are described here:
Thanks for your advice
Dwight
-
After more investigation I discovered the problem was due to lack of permissions on the Storage folder assigned (DOH!).
Would be a good idea to improve the ProGet error message as you indicated so it gives a more helpful clue.
Thanks for your help.
Dwight
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