Below is a conversation I just had with their tech support.
While having a free SSL cert that doesn't break ASP.Net is a good thing. The problem with this new system is that you have to go to a completely new URL from the one user users come in on. And I think, confusing the users seeing the URL change that completely. The other problem is just getting DNN to navigate to the new URL.
While a tempting solution, I would suggest staying away from it and getting your own SSL cert (as low as $19/year from freessl) will prevent many problems.
--------------------------------------------------------------------------------------
Shared SSL Certificate
In the past, I've seen a warning that enabling this would break asp.net and did not see the warning this time.
From your instructions, it appears that now to use your certificate on a users site requires the user use the URL that is specified in the control panel. One of my useraccounts (rbresort) this reads as " https://site205.mysite4now.com/rbresort". For DNN users, then they would have to put the above URL in their alias table.
Is this an accurate interpretation?
User/Staff Follow-ups
KC (staff)
10/8/2004 2:16:05 PM
Yes, you are correct. The new shared SSL will indeed work with asp.net without a problem, and yes, you do need to add that as an portal alias.
If you have further questions, please feel free to contact us again. Thank you.
-------------
Thank you for using our Hosting Service.