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 ...Migrate from localhost to IIS web server using multiple sitesMigrate from localhost to IIS web server using multiple sites
Previous
 
Next
New Post
8/10/2008 2:47 PM
 

I've developed a DNN site on a local IIS system whereby the address of my DNN site is http://localhost/mec. I'm now trying to move this onto a production IIS server whereby the site will be a separate website using host headers.

I've copied c:\DotNetNuke\MEC across to the production system. I've created an IIS 6 website called MEC, set-up host header and pointed it at the folder. DNS is all set-up so that http://mec.milkshakeweb.co.uk points to this new website.

However, when I load up http://mec.milkshakeweb.co.uk it redirects to http://localhost/mec which doesn't exist. I know a bit about aliases and I'm sure that maybe an alias will help here but:

  1. http://localhost/mec will never resolve to the website on this production server. http://localhost is the default web site but I'm trying to use a completely separate site
  2. I temporarily added a localhost/mec virtual directory just so I could log on. I see that the default portal is still http://localhost/mec which doesn't look right
  3. I can't edit http://localhost/mec and even if I could, I'm not sure what to change it to :-)
  4. The website and host headers are working. I added a test.htm to the website and I can open http://mec.milkshakeweb.co.uk/test.htm so the host headers and DNS are working fine
  5. I tried adding mec.milkshakeweb.co.uk as an alias but that doesn't work

If I maybe understood how DNN is using the alias table, I might be able to work out how to fix this.

Cheers, Rob.

 
New Post
8/11/2008 10:17 AM
 

Hello Rob,

I'm unsure if you haven't tried this already but since I had a similar situation, here goes what I needed to adjust:
1) Log in as host account
2) Go to Admin > Site Settings page
3) In the Portal Alias section add the HTTP alias you want, example "domain.com/dnn"

That should fix your problem if you're using port 80.

 
New Post
8/11/2008 11:53 AM
 

Hi Rob,

You are correct... it is definitely an issue with your portal aliases. Go to Portals, then select the main portal, and create a new portal alias. Enter:

mec.milkshakeweb.co.uk

as the portal alias. And it should work fine. You will need to do this BEFORE you upload the site, otherwise you won't be able to get into the site to make the change. I think you can add it directly in SQL if you don't want to re-upload... I don't recall the name of the table, but I remember it being pretty obvious.

Robert

 
New Post
8/11/2008 2:23 PM
 

I should have read more thoroughly before responding... I see that you tried adding the portal alias already in step 5. If that didn't work, try refreshing the application pool. It is likely that the old portal redirect is stuck in the server cache. Once you refresh the app pool, IIS should pick up the new DNN alias.

Robert

 
New Post
8/12/2008 10:33 AM
 

Thanks for that - messing around with the application pool worked a treat. In the end, I created a new application pook for DNN (it was actually sharing the same pool as the default web site) and it's leapt into action.

Cheers, Rob.

PS. Hmm, wonder why I'm not getting notifications from here - time to check spam I think.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Migrate from localhost to IIS web server using multiple sitesMigrate from localhost to IIS web server using multiple sites


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