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!
SSL / https self-hosted ProGet
-
Hi,
I tried using the self-hosted service instead of IIS to setup https for ProGet but so far it's not working. I used the “ReserveUrls” command to reserve https://:443/ (NT AUTHORITY\SYSTEM) and I changed the Service to use the parameters /s /urls=https://:443/. The service wouldn't start anymore. If I try to run it using the “run” action from the command line, with the url “https://*:443/”, the program crashes (see screenshot). Would you be able to direct me to a tutorial on how to setup https using the built-in server (not IIS) ? I’m trying to follow this one: http://inedo.com/support/kb/1014/changing-an-inedo-products-url-with-the-integrated-web-server , but obviously it’s not directly targeted at configuring the whole thing like I want it to so if you had any other articles that could fill that gap that would help me a lot.
Update:
After trying to make this work this afternoon, by re-installing the app with and without the GUI (silent install with specific parameters) and messing with the url registration, I came to the conclusion that there is a bug in the application. More specifically in the InedoLib. There is a regex in the WebServerPrefix that has http hardcoded there, so if the URL doesn’t contain http:// then an exception is thrown and it crashes. I don't know if it's "working as intended" and you don't allow the use of https or if it's actually a bug ?Let me know if it helps you to find the cause of my issue and if you can fix it.
Thanks.
Product: ProGet
Version: 4.0.10 -
Thanks for looking into this; it's quite possible there is a bug for https in the IWS.
Do note that the IWS is very rudimentary, and basically is just a basic wrapper around the ASPNET hosting libraries. IIS also wraps these same libraries, but it can do a lot more before the code gets to ASPNET runtime, such as logging, requirest filtering, etc.
We really do not recommend using the IWS for anything other than the basic, out-of-box set-up... and since HTTPs requires setting up a certificate and the like, using IIS is much better (plus, others will be able to figure it out once a certificate expires or something).
-
Alright, well I did manage to make it work using IIS so at least there is a workaround, however since that was the only thing on that server that needed IIS it's too bad that I had to install and configure it only for that purpose.
Thanks.
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