Oh, that's a shame. We definitely try to cut down on the complexity of what we ask of folk when they deploy this, so that's more friction than is ideal.

Thanks for the reply!

If any of the reported users see this and have tips and tricks from their experience, I'd love to hear them!

I'm looking to host multiple services on the same port (in this case, lazily, 443).

With other services, e.g. Jenkins (and previously Nexus) I have used nginx or the Azure Application Gateway to route traffic to ports based on the path accessed, and then used context path / application context path to modify the apps URLs etc.

This works very nicely for my use. I want to replace Nexus with ProGet, but I can't figure out a way to do so!

It seems that URLs (the node in /InedoAppConfig/WebServer within the ProGet.config file) ignores anything after the port number, and Web.BaseUrl in advanced settings also seems to ignore it. Though I can get a semblance of a page loading, scripts such as nonmodal.css and jquery.min.js immediately fail to load (as they're pointing to the original URL rather than my attempted path).

Is there anything I can do to add a context path to ProGet?