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 ...Non standard port installationNon standard port installation
Previous
 
Next
New Post
3/1/2007 7:21 AM
 

I have a fully functional DDN site working on a server via virtual directory,

Using DNN 3.3.5

ASP.NET 1.1

SQL Server 2000

Windows Server 2003

The server administator has redirected web traffic coming in on port 80 to 82.

IIS is set to port 82

DDN portal alias includes mywebsite.com and also mywebsite.com:82 - it needs both aliases, without the second one with the port added, the home page will not load.

With this settings the home page will load from typing URL mywebsite.com, but when I click on a page link, it automatically inserts ':82' into the URL. It fails to load, but if I manually delete the ':82' from the URL, it will load the page.

I also notice some of the skin settings are not loading ... there is a coloured bar across the top and bottom of the page ... I am using a DNNDesign skin.

There are other posts that talk about this but I can't find one that actually provides a solution. Any help or pointer greatly appreciated.

 

thanks

 

 

 
New Post
3/2/2007 5:39 AM
 
the problem is, that dnn is reuested on port 82. so it will answer the request on port 82. i'm not sure if there is usefull solution for that; i don't think so. perhaps you could make a website redirecting to "yourdomain.com:82".
 
New Post
3/2/2007 9:28 AM
 
This is a case where you may actually want the UsePortNumer switch turned OFF in your web.config. So under appSettings, make sure you have:

<add key="UsePortNumber" value="False" />

PortalAlias tweaking -- especially with port numbers and nonstandard setus -- is unfortunately pretty tedious. I can't replicate that particular setup on my development machine, so I may not be of much more help.

Brandon Haynes
BrandonHaynes.org
 
New Post
3/3/2007 8:31 PM
 
Thanks ... tried this ..used both 'True' and 'False' for this key ... niether worked. but thanks for your reply.
 
New Post
3/3/2007 9:18 PM
 

bbhermann wrote
the problem is, that dnn is reuested on port 82. so it will answer the request on port 82. i'm not sure if there is usefull solution for that; i don't think so. perhaps you could make a website redirecting to "yourdomain.com:82".

Could you explain a little further on how I would make a website to redirect to "mydomain.com:82" please. I assume the website that redirects is "mydomain.com" ? thanks

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Non standard port installationNon standard port installation


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