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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Problem adding parent portals after clean install in wh4lProblem adding parent portals after clean install in wh4l
Previous
 
Next
New Post
4/30/2007 5:31 PM
 

I've installed DNN using the Installation Wizard (that was great, thanks), I'd like to set up different alias's.  Lets say my domain is http://www.mysite.com and my DNN portal in there.

I'd like to set up a subdomain through Webhost4life called http://subdomain.mysite.com. After setting it up in Webhost4life, I would then go into DNN as the 'Host' and create a new Parent Portal using the alias http://subdomain.mysite.com.

1- Am I doing this correctly?
2- When I set up the subdomain in Webhost4life, I would assume that I need to tell it to 'add subdomain' and set the target path to the directory where my DNN app is, which is the same http://www.mysite.com  Is this correct? Because is not working

Do i need to set up some permissions? or what do i need to add new parent portals?

 

because now if i try to access the new portal im getting this :S

 

Server Error in '/' Application.

Runtime Error

 

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>

 

 

 
New Post
4/30/2007 5:39 PM
 

That sounds right, but you might try making CustomErrors = Off in the web.config so you can get a more descriptive error of what is occurring when you try to access the subdomain.


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
4/30/2007 6:46 PM
 

thanks for the reply

i already did it. that's the strange part. Im using DNN 4.5.1

you can see the parent portal on this subdomain http://newarcadia.inovasoftware.com/

thanks.

 
New Post
5/1/2007 12:24 PM
 

I get this problem constantly with WH4L and can't figure it out - one subdomain will work, the next one not. I find that if you open a support ticket they will fix it for you, it spossibly DNS related.


Regards
Nick
 
New Post
5/1/2007 12:48 PM
 

thanks nick i'll do that.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Problem adding parent portals after clean install in wh4lProblem adding parent portals after clean install in wh4l


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