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 ...Solution: GoDaddy DNN on root, no subdir in URL, multiple domains hostedSolution: GoDaddy DNN on root, no subdir in URL, multiple domains hosted
Previous
 
Next
New Post
12/3/2008 11:38 AM
 

I'm still having issues with this.

I had another ASP.net application running in a sub folder that was set up in IIS.  IT was working fine until I moved my DNN install to the root directory.  Now the other applicaiton is referencing the web.config file for DNN that is in the root directory.  I get the error: [No relevant source lines]

 Go Daddy IIS setting won't let me remove the IIS from the root directory.  Any other suggestions or work arounds? 

 
New Post
4/20/2009 6:25 PM
 

Tricky P wrote

After reading a million posts, I found a post somewhere (I think on this site, but not sure) which gave very clear instructions on how to move the DNN install to the root of your deluxe hosted site. I copied the steps and it worked perfect! Yes, you can eliminate the subdirectory, look like a real web site, and set up any other domains that you host as portals, also without any subdirectory in the URL. It's not hard, folks, and I'm staying up late to share because i'm happy to give a little something back if it can help others. Once you move the site, you can point all your domains to your root, and just indicate your domains in the portal's HTTP alias. No need to re-install & no more redirects. A million thanks to whoever posted the basic steps. I'm adding some detail that I hope is helpful for the benefit of ALL THE POSTS complaining about this, because this fix really works. GoDaddy doesn't support install at the root by default, but moving it after the fact is not hard. Here are the steps. 

1) Check that the Root and DNN directories have the same permissions. You might need to adjust through IIS Settings or File Manager(I didn't). Check the bottom of this page for good advice on security: http://www.northernstarsolutions.com//tabid/61/Default.aspx.

2) Backup both your DNN web installation and your database (in database section, click the pencil to edit, then the Backup icon at the top)

3)  Create an html file called app_offline.htm into the DNN directory, taking the site offline.

4) Update your site's existing portal alias record in the database (the HTTPAlias column of the dnn_PortalAlias table) from (example) mysite.com/dnn to simply mysite.com. This is the only slightly advanced step. From the GD control panel, go to databases/SQL Server/Open Manager. Enter your DB username & pass (user is like tri + 12 #s). Once you connect, go to Query Analyzer, and execute this(omitting quotes) "select * from dnn_PortalAlias" This shows you all your aliases for any portals you have. So, if your main site has portal ID of 0, and your current alias is mydomain.com/dnn, you would update it to mydomain.com by executing this:

UPDATE dnn_PortalAlias
  SET HTTPAlias = mydomain.com
  WHERE PortalAliasID = '0'

5) Now move the contents of the current DNN folder into the root. Easiest way is to FTP it back home, then up into the root. It takes a little while, but just sit back and think how happy you are gonna be soon. Google's gonna see you as a real site!!  :-)

6) Update any references you might have in your web.config file to your old site path.

7) Remove the app_offline.htm file and point a browser at the default.aspx file.

8) Have fun with a real DNN install on GoDaddy!!

 

Excellent Steps, no more information is needed. These steps are still current.

 
New Post
7/7/2009 12:43 AM
 

Mike Ott wrote

I'm still having issues with this.

I had another ASP.net application running in a sub folder that was set up in IIS.  IT was working fine until I moved my DNN install to the root directory.  Now the other applicaiton is referencing the web.config file for DNN that is in the root directory.  I get the error: [No relevant source lines]

 Go Daddy IIS setting won't let me remove the IIS from the root directory.  Any other suggestions or work arounds? 

I know this is an older post but just in case you haven't found the solution.  You should set the sub directory as an application root in the IIS Managment settings.  The root directory will always be an application root.  Specifying the sub folder as an application root should tell IIS that it will have it's own web.config and all folders under that will be part of that application (unless also set as application root in IIS Management).

 
New Post
7/7/2009 10:32 AM
 

AdmSteck is right on the money.  Unfortunately GoDaddy doesn't always make things easy, even on the IIS basic settings front.
 
Here's info on how to configure GoDaddy settings to git rid of the subfolder name without any need to move your installation to root:
 
   http://www.eguanasolutions.com/DNN_Blog/EntryId/31.aspx
 
If you happen to use Network Solutions as your provider, things are a bit easier:
 
   http://www.eguanasolutions.com/DNN_Blog/EntryID/30.aspx

 
-mamlin


esmamlin atxgeek.me
 
New Post
7/7/2009 4:27 PM
 

This walkthrough has been helpful, but I have encountered a brick wall and need some advice. The line in Query Analizer:

select * from dnn_PortalAlias

Did not work for me and gave me an error that "dnn_PortalAlias" didnt exist. I played with the code and got it to work when I altered it to "PortalAlias" and dropped the "dnn_". I moved on to the next step and when I try to execute:

UPDATE PortalAlias (dropped the dnn_ because it wouldnt accept it)
  SET HTTPAlias = mydomain.com (I changed it to my domain, or course)
  WHERE PortalAliasID = '0'

I get the error "The multi-part identifier "mydomain.com" could not be bound" What am I missing here? I copied the domain name exactly from the HTTPAlias and checked it for accuracy. I recently installed DNN, and am just now setting it up. I just added the aliases to the DNN admin settings. I followed the instructions of each step prior. Any help is appreciated. Thanks!

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Solution: GoDaddy DNN on root, no subdir in URL, multiple domains hostedSolution: GoDaddy DNN on root, no subdir in URL, multiple domains hosted


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