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 ...run dnn on iis 7.0 locally on port xx ( not 80)run dnn on iis 7.0 locally on port xx ( not 80)
Previous
 
Next
New Post
5/19/2009 11:16 AM
 

When you create a new web site in IIS 7.0 you have to select an nonstandard port ( not 80 ) i.e. 85.

You then access your site with http::/localhost:85/, when run first time it successfully install dnn.

When I select 'Login' dnn fail's to show the login page due to that it dosn't preserve the port number. It comes up with (http::/localhost/ Home/tabid.....) missing the port number in the host, should be (http::/localhost:85/ Home/tabid.....).
The web.config file has default preserveport=true.

I have tried with both 4.9.3 and 5.00.01 both failing on IIS 7.0

If I on IIS 5.1 switch port to port 85 on the default web site and add both 4.9.3 and 5.00.01 as virtualDirectories, dnn is preserving the port number.

any ideas

regards

Henrik

 
New Post
5/19/2009 11:30 AM
 

Henrik,

instead of using a different port, I'd suggest to use a dedicated server name (e.g. DNN493) , you will need to add to local DNS or to /windows/System32/drivers/etc/Hosts file for access from local machine only.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
5/19/2009 12:12 PM
 

Why are you having to select a non-standard port?  Do you already have a site running on port 80?  You can always add a new IP address to run a second site on port 80, or use host headers.

Also, don't install from "localhost" or you run into issues right away.  Nobody will ever access it as "localhost" so why install that way?  Install from a valid URL.

Your real issue is that the portal alias doesn't have the port number included.  Add a new portal alias that includes the port number.

Jeff

 
New Post
6/30/2009 11:22 PM
 

hi Sebastian,

ok, i have the same problem, is it bug on dnn 5.1? cause im going to use this release for production, afraid it will gonna fail.

right now it still on my local, i try both port 80 and other then 80. for port 80 it success, other then 80 : yes i have create a portal aliases and change a hosts file under windows/system32.../hosts, when i ping to the address i get reply, but when i try to login, come up with errors.

any idea?

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...run dnn on iis 7.0 locally on port xx ( not 80)run dnn on iis 7.0 locally on port xx ( not 80)


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