I just spent several hours trying to figure out why a site of mine broke after upgrading it to 4.3.6.

It seems that if a dnn site uses a custom port such as "www.dotnetnuke.com:8083" the site will "loop forever" in IE and you will get an error in Firefox "The page isn't redirecting properly" after upgrading.

The bottom line is, something was changed in the new version that breaks this functionality. Everything works correctly for the site again if I change the site to use port 80, remove the "port part" of the url and update the Portal Alias table.

Anyone else see this problem?

Also can anyone on the core team maybe provide some insight into where in the code this might have occurred so I can fix it and post the changes for everyone's benefit until the next fix is out?

Thanks

Hi,

I spent ages trying to install DNN436...Every time I tried to open the site I got a 'Cannot find server error'

Now I know why!

Like you I still haven't got a solution from anyone..

Having same issue.  I'm just trying to get it to run on the ASP.NET Debug Server (eg http://localhost:1217).  This is my first experience with DNN so it's a big let down that this software doesn't work!

Matt