Fresh Proget 5.1.22 in fresh IIS 6.2 gives 500 errors at best

Guest

Hi ProGet,

I've tried to get HTTP and HTTPS working together with the built-in webserver to no avail. We can only get HTTP or HTTPS working, not both.

Therefore I have switched to the IIS approach, which gave me further headaches. Even though I've switched on all checkboxes I could find in IIS, the best I get is an empty page or a 500 page.
We're working with IIS 6.2 (out-of-the-box) on Windows 2012 and ProGet 5.1.22. As I'm trying to move our old ProGet server to this new machine and environment, I cannot use the latest ProGet instance at this moment. I dare not touch our production version of ProGet - if that fails too, we're in for trouble.

When I go to http://localhost/proget2 I get a full-fledged 500 error with details. When I go to http://localhost/ I just get a blank page, with <BODY></BODY>. Using any other binded url's just gives an empty page or a brief 500 error.

The detailed error page is copied in below. I hope you can shed some light on this 'cause after 10 hours of wriggling with all the settings, I'm at my wits' end.

Thanks,
Eelko

Image link: https://photos.app.goo.gl/qrKnmwjGFNKZPyjm6

Product: ProGet
Version: 5.1.22

Guest

Based on the screenshot you're sharing, it looks like you are trying to configure an application (virtual directory) called "/proget2" under different website. ProGet does not support this. You will need to create a site dedicated to ProGet. See ProGet Manual Installation

You can find errors from blank pages typically in the Windows Error log. It's usually a severe IIS error from an Application Pool crash, or something.

Guest

Hi Alana,

Thanks for the information. I've reinstalled ProGet and IIS several times and at attempt four it suddenly worked fine.

So I'm not touching the setup anymore and will keep it as-is now!

Thanks,
Eelko