Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

About

News Press Releases News Coverage Press KitCareersContact DNN

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 ...Cannot install 4.5.5 on a different portCannot install 4.5.5 on a different port
Previous
 
Next
New Post
8/22/2007 4:19 PM
 
ykalinov

Joined: 5/7/2007
Posts: 2

I am having problems to run a clean dnn 4.5.5 on a different port. The installation went fine and I can see the home page too. But when I try to login or register than the url is without the port(it's using the default port)  http://localhost/Home/tabid/36/ctl/Login/Default.aspx?returnurl=%2fDefault.aspx  instead :

 

http://localhost:5555/Home/tabid/36/ctl/Login/Default.aspx?returnurl=%2fDefault.aspx ... if I manually add the port to the url I can go to the login page. Also if I switch back to port 80 everything seems fine.

I am trying to run the dnn on win2003serverR2

Thanks
 
New Post
8/23/2007 8:44 AM
 
Sebastian Leupold


Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

www.dnnwerk.de
Joined: 3/8/2004
Posts: 46212

make sure, you aded the new siete address as portal alias: log in as superuser ("host"), fo to Portals in Host menu and select your portal. scroll down settings page to the far end and add then new address (e.g. www.mydomain.com:81)

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
8/23/2007 5:08 PM
 
ykalinov

Joined: 5/7/2007
Posts: 2

I dig into this more deeply and found out that when I start the installation from http://localhost:81 than the alias which is created for the default portal is http://localhost and probably this is the reason why the login/register links are without the port and are not working.

If I start the installation from www.mydomain.com:81 than the alias which is created for the default portal is correct: www.mydomain.com:81 and everything is working.

This looks to me like a bug or very 'strange' behaviour.

Also I found out another 'strange' thing. In the second case when I have a working dnn on www.mydomain.com:81. I tried to create a second alias for the portal as http://localhost:81. In this case when I try to open dnn from http://localhost:81 the url is automatically redirected to www.mydomain.com:81, so this second alias is unusable. Note that I did the test without the port and evrything was working. I could access the portal both from www.mydomain.com and http://localhost.

So please can somebody explain to me if those are bugs with dnn and port or something i cannot understand ?

Thanks
 
New Post
8/31/2007 10:10 AM
 
Roberta Freese

Roberta Freese's Avatar

Joined: 6/17/2004
Posts: 89
I am experiencing a similar issue with DotNetNuke Version: 04.05.05 on XP with SQLExpress 2005 using a non-80 port. The application installs with the default portal as localhost, no port number, which means 80 which I can't use. I have added aliases, but still the link on the Logo skin object goes to the default alias when I am on the site as localhost:1010.

If I access it via one of the other aliases, the logo link persists to that alias, which is fine.

Is this a bug?

There is no way I have found other than going into the database to change which alias is the default for a portal so localhost will seem to always be there. Am I missing something? Is this a bug or a feature? I could see it as a failsafe, so people with access to the server could get in, but combined with the above it's a small problem.

I really like the new install wizard, and the bug fixes to the Windows Auth so far.

Thanks for any insights,
Roberta
 
New Post
9/15/2007 11:07 PM
 
John Hildebrant

Joined: 8/4/2005
Posts: 97

Did you get it to work on a port other than port 80?

I added a portal alias for 192.168.1.2:81. I changed IIS to run on port 81. Then I accessed DNN using http://192.168.1.2:81 and changedall other portal aliases to use port 81. I reconfigured my router to forward port 81 instead of 80. It didn't work at first, but then I remembered that I needed to also add port 81 to Windows firewall exclusions and it worked. Now I just have to figure out how to using my domain services  control panel to forward port 80 to port 81.
 
 Page 1 of 3
123Next 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Cannot install 4.5.5 on a different portCannot install 4.5.5 on a different port


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