Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...DotNetNuke SSL ProblemDotNetNuke SSL Problem
Previous
 
Next
New Post
12/15/2008 6:11 AM
 

Hi all,

I have DotNetNuke installed on a shared hosting account and I'm running several portals from one installation. Each portal has its own domain name, the PortalId for each domain is as follows:-

0 = sinconta.com/dnn
1 = friendsofthechurchyard.org.uk/dnn
3 = beastlings.com/dnn

I purchased an SSL certificate for beastlings.com and it is all set up properly. I can successfully access files in my web space from either http://www.beastlings.com/... or https://www.beastlings.com/...

The problem arises when I try to access DotNetNuke via SSL. If I try to connect to https://www.beastlings.com/dnn then I get redirected to https:/www.sinconta.com/dnn - I can't understand why this is happening? Can anybody explain why I may be getting redirected to portal 0?

Thanks,
Adam

 
New Post
2/5/2009 4:27 AM
 

I did some packet traces to find out what is going on with this problem.

1) Initially there is an HTTP POST (this is the ASP.NET PostBack that occurs when clicking the Login LinkButton)

2) Sometime later the web browser issues an HTTP GET for the path /dnn/Login/tabid/269/Default.aspx?returnurl=%2fdnn%2fDefault.aspx

3) In response to the GET, the server sends back an HTTP 302 Found response stating that the resource has temporarily moved to https://www.beastlings.com/dnn/Login/tabid/269/Default.aspx?returnurl=%2fdnn%2fDefault.aspx.

4) So it all seems to be working as expected up until this point - DotNetNuke has redirected us to https://www.beastlings.com/. The SSL connection is then established, but due to the fact it is encrypted I can't see what happens inside the SSL connection... but at some during the SSL connection we are then redirected to https://www.sinconta.com/.

Do you know of any way to debug what is happening inside an SSL connection?

 

I have actually given up on this problem. The technical folks at my shared hosting company haven't been able to help me. There has been no response on this forum to anything that I've posted.... I don't think I'll be recommending DotNetNuke to any clients anymore, if you get stuck with something then you really do hit a dead end.

I've decided not to use SSL with my DotNetNuke site anymore and have requested a refund for the SSL certificate - a very bitter taste remains in my mouth.

I have recently started using WordPress and I am totally amazed at the vibrance of the community and how easy it is to find help.

 
New Post
2/5/2009 8:41 AM
 

Hi,

Maybe not helpful anymore, but every domain needs an own ip number otherwise ssl will not work. You can also install a multiple domain certficate on one ip number. Maybe your hosting company does not know that.

J.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...DotNetNuke SSL ProblemDotNetNuke SSL Problem


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out