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 ...Installing DotNetNuke on ISP That Blocks Port  80Installing DotNetNuke on ISP That Blocks Port 80
Previous
 
Next
New Post
2/20/2007 11:38 PM
 

I have been running DNN v 3.x upgraded to v4.x to host 3 non-profit portals on my home server for several years with great success.  I have installed a new second ISP who blocks port 80 and I want to run DNN on that ISP and cancel my old ISP for performance reasons.

On my old ISP, I have used Mydomain.com to create an A record that points to my home server IP and all works fine. With the new ISP, I need to do the same, but use port 8080 instead of the default of 80.

I have spent 3 weeks trying different schemes of redirection and just can't get DNN to work correctly.  Other Active Server pages and .Net pages work fine. 

Has anyone had any experience with using ports other than port 80?  I'm a programmer by trade, so coding workarounds are an option.

Thanks in advance.  Brad

 
New Post
2/21/2007 10:35 AM
 
This is more of a apache/IIS issue then a DNN issue from the sounds of it. If you edit the http port on whatever web server s/w you are using DNN should work fine.
 
New Post
2/21/2007 11:05 AM
 

 

Make sure the Port Number is included as part of your PortalAlias, and then in web.config, add an app setting (if it is not there) called "UsePortNumber" and set it to true:

 <appSettings>
  <add key="UsePortNumber" value="true"/>

I haven't tested this, but the code is there to support it.


DotNetNuke Modules from Snapsis.com
 
New Post
2/21/2007 2:03 PM
 

Thanks - I will give that a try later tonight when I get home. 

One additional complication is I don't want users to have to include the port number on the URL, for example http://www.mywebsite.com:8090 .  In the past, I have gotten around this by usings a stealth redirection where by http://www.mystrealthwebsite.com is a frameset that includes http://www.mywebsite.com:8090 in the visible frame.

Setting UserPortNumber to True may solve that issue.

 

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Installing DotNetNuke on ISP That Blocks Port  80Installing DotNetNuke on ISP That Blocks Port 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