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 ...Advice on DNN Portal, Https and securityAdvice on DNN Portal, Https and security
Previous
 
Next
New Post
1/5/2015 5:45 AM
 

HI, when we first installed and setup our DNN Pro site we were advised to create our portals as new sites in IE7, each portal running in their own App pool.
This we have done and have currently 2 portals using a different domain name, we will eventually have up to 20 portals using a number of domain names.
When we inquired about securing the various sites logins using https certificates it came to light that this approach is wrong and we Recieved this advice
DNN should run DNN under a single IIS web site entry.
If we run multiple web site entries for each portal in DNN, DNN will determine this as multiple web servers in Host > Manage Web Servers. This is then determined to be a web farm configuration, which will turn on the Shared Caching Providers. Since we are not using a web farm configuration, multiple errors will occur due to the web request caching provider and Host > Schedule will not run. Meaning that the Search Crawler has not spidered our websites.
It is recommended to run DNN under a single application pool and IIS web site entry. After this is done, deleting all entries in the WebServers table will allow the scheduler to run normally again.
This recommended configuration of DNN will only allow for a single SSL certificate to be installed in the IIS web site entry. This is a limitation in IIS 7.

Obviously we cannot afford to buy 20 licences for each domain.
Apparently IIS 8 allows multiple SSL certificates to be bound to host headers, does anyone have any knowledge of II8 and can confirm this?.

Other than build a new hardened web server with II8 (if true) and all the problems of moving licences and sites domains etc, are there any real issues with our current setup and is there any workarounds we can use to get around applying https to secure each site.

 
New Post
1/5/2015 10:32 AM
 
By IE7, I assume you mean IIS7.

Question, who advised you to run multiple IIS App Pools?

Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
1/5/2015 11:28 AM
 

Hi Chris, yes IIS7 .

I really hate to say so as most advice has been brilliant but it was DNN Pro support.
We set up our portals and webserver according to that initial advice and now find ourselves with a problem.
One of the reasons we choose DNN was the multi portal option and the ability to share data accross portals easily.

We never thought much about multiple domain names being a problem and it was never raised during our sales webinars, but are now wondering what the best approach is.

 
New Post
1/5/2015 11:33 AM
 
Using DNN with multiple portals is fine, and a very common thing to do. I do not know how the licensing for Evoq works these days, but I seem to recall they were changing the way licensing worked, in a way that would make it very costly to have multiple domains running out of an installation.

Perhaps my memory fails me on that front, maybe they didn't make that change, or they've made further changes since then.


Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
1/5/2015 11:58 AM
 
Chris Hammond wrote:
Using DNN with multiple portals is fine, and a very common thing to do. I do not know how the licensing for Evoq works these days, but I seem to recall they were changing the way licensing worked, in a way that would make it very costly to have multiple domains running out of an installation.

Perhaps my memory fails me on that front, maybe they didn't make that change, or they've made further changes since then.

 Chris, are you saying our current set up is ok with multiple sites and app pools and the domain names as host headers.
Or should we make each portal a virtual directories running under one app pool? and if yes could  we still use different domain names in host headers.
DNN Corp were suggesting multiple instances for each domain but that is unrealistic and unaffordable to have multiple licences

Any advice as to a workaround would be welcome.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Advice on DNN Portal, Https and securityAdvice on DNN Portal, Https and security


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.

Content Layout

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  


Copyright 2017 by DNN Corp Terms of Use Privacy
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out