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 ...Redirect loop to public internet, but not internal networkRedirect loop to public internet, but not internal network
Previous
 
Next
New Post
10/7/2009 8:51 AM
 

 I have put together a site for a customer, that is using DNN Community Edition 5.01.02.  The DNN platform is running on Windows Server 2003, with IIS 6 (of course), use .Net 3.5. This customer utilizes the webserver for a multitude of tasks, so the DNN install is on a seperate Website configuration than their other sites.

I have a development arena setup, for internal testing only, at test.mysite.com.  I have their website, using the dnn platform setup at www.mysite.com.  The original files that were used in the test environment, and that are used for development, are located in the C:\Intepub\test.mysite.com\httpdocs folder, which is also the home directory of the test site in IIS 6.  The live files are located in the C:\Inetpub\www.mysite.com\httpdocs folder, which is also the home directory of the live site in IIS 6.

When I access the site, connected to my customer's VPN connection, both the test and live sites come up without any problem, and are quite snappy.  However, when I disconnect from their VPN and try to access the live site, I receive the oh so dreaded redirect loop that is the subject of quite a few posts I have seen on Google searches.  

I have configured the bindings so that they are using www.mysite.com and the appropriate IP address for the site.  This particular customer uses ISA server as their firewall, so I am not sure if something from that level is causing my issue or what.

I have modified the Web.Config file to allow "Full" Trust (no change)
I have restarted the  IIS Server Serivce (no change)
I have double / triple checked the PortalAlias for a trailing slash "/" (not there)
I have stopped and started the website site in IIS (no change)
I have created a seperate .Net AppPool (no change)

I am running out of ideas, and out of time.  The way this site was installed was like so:

The test site was setup utilizing the DNN Install Wizard.  The database is running on SQL Server 2005, and was created in the development arena initially.  Upon completing the site, and receiving approval from my customer that the site was configured how they wanted it to be, I did the following:

  • Copied the DNN files from c:\inetpub\test.mysite.com\httpdocs to the C:\inetpub\www.mysite.com\httpdocs location.
  • Updated the PortalAlias table to read www.mysite.com in the HTTPAlias column in the database
  • Updated the HostSettings table record: HostURL : to have a SettingValue of http://www.mysite.com
  • Created the IIS Website and pointed it to the location of the new live files (in the www.mysite.com\httpdocs folder)

Then when accessing the site internally, it comes up fine.  I only get the redirect loop when the site is attempted to be reached from the outside world.  Any help on this matter would be greatly appreciated as I am at my wits end now.

Thanks
Kyle Schultz

 

 
New Post
10/7/2009 6:17 PM
 

Stop the test site and try accessing the live site with ip and www.livesite.com.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Redirect loop to public internet, but not internal networkRedirect loop to public internet, but not internal network


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