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 StartedNew to DNN Plat...New to DNN Plat...Running from localhostRunning from localhost
Previous
 
Next
New Post
2/26/2011 11:26 PM
 

Hi,

I’ve installed DNN in a directory named VnGuest on localhost. Everything is working via http://localhost:1960/vnguest/ but if I try http://localhost/vnguest/ first I get the following error, so I delete the line of code below, and try again but it keeps defaulting to http://localhost/VnGuest/Install/Inst... how do I stop that. I need it to run from localhost before continuing, if I cant get it to run from there I don’t like my chances of getting it up and running on remote servers where I have way less control.

 

<httpRuntime useFullyQualifiedRedirectUrl="true" maxRequestLength="8192" requestLengthDiskThreshold="8192" requestValidationMode="2.0" />

 

Cheers,

Mike.

 
New Post
2/27/2011 6:51 AM
 
Woah - you cant delete that line of code from your web.confg.

But by setting your initial website up using a port number - there is a setting that gets forced to true in your web.config.

<!-- set UsePortNumber to true to preserve the port number if you're using a port number other than 80 (the standard)
-->
    <add key="UsePortNumber" value="true" />

In a normal dnn install that particular line is commented out - but im guessing that its not commented out in yours.

<!-- set UsePortNumber to true to preserve the port number if you're using a port number other than 80 (the standard)
    <add key="UsePortNumber" value="true" />
-->

But having said this - I'm not aware that it would necessarily cause this sort of problem on its own.

If you look in your portals settings - portal aliases - you will most likely find that your portal alias explicitly references the 1960 port.
In which case you will need to add a new portal alias for http://localhost/vnguest/ to your aliases before dnn will recognise that it exists.

Westa
 
New Post
2/27/2011 6:35 PM
 

Hi,

I fixed the first issue, VS2010 had created the site as a .NET Version 4.0.

But neither of the above mentioned ideas worked.

I set up a new alias localhost/VnGuest set it as the default and. Now it is defaulting to via localhost/VnGuest alias straight to the install page and I can’t view the site at all.

Cheers,

Mike.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedNew to DNN Plat...New to DNN Plat...Running from localhostRunning from localhost


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