Hi,

I thought I'd saved my topic but I can't see it. So here goes...

I've installed DNN 4.9.1 on my localhost server on my home lan. Everything works good so far.

Since I want to work on the site outside my home lan, I have setup a No-Ip dynamic ip with one of my domain name. www.quebecvirtuel.com .

Since my isp do not allow open port 80 I've setup a redirection on port 8080.  Inside the lan everything works but outside the redirection on port 8080 works but when it is time to load default.aspx, it tries to connect to 127.0.0.1

I have tested my IIS -Vista installation with the IIS default web site and everything works so I know it has something to do with DNN config or else.

I have setup the http alias on my portal and change server config in web.config.

What else do I need to do for the DNN web site to load.

P.s try www.quebecvirtuel.com
Thanks for helping.

Éric

Did you add an entry for your URL to the PortalAlias table? If your URL is www.quebecvirtuel.com, you will need to put that into the table.

As I've stated, I already did that !

Hello,

I have not setup DNN in this way, but if you have the portal alias in the DNN install and the site is not getting picked up I would first of all see if you can get a basic html page to load using the redirection method you are using. - If this works for a url to your LAN at least you know that the redirection and ports are working correctly.

As I've stated, I have done already and it works perfectly.

Is there anything else I need to do beside Portal http alias for DNN pickup my URL ?

Thanks

Éric

 

 

ok try this as a test - put an app_offline file in the root of your DNN installation files - this will be displayed over the default.aspx and is useful for upgrading - if this displays on your domain name thats another check that it definitely works.

I have attached one to this forum post so you can quickly upload it.

If that works, then the only thing that I can think of is to just have the domain name in the portals alias list, so if you have a localhost URL first in a portal alias list delete it ( create a backup first of course) and have the domain name as the only item in the portal alias list.

Hi Lee,

I have done some test with your file. Tests were done inside my lan not outside. When I use hhtp://localhost/dnn/492/test2 I see your file and when I rename it to .temp the dnn site comes on.

When i try with www.quebecvirtuel.com with no app_offline.htm the site comes up but when I use the offline file I get  a http 404 error.

The primary alias is hhtp://localhost/dnn/492/test2 and it does not seem to be editable.

Oh, I have just tested outside the lan with my pda and your offlein file works.....

Try it www.quebecvirtuel.com

Éric

I think that you need to go to your site settings page and ADD a portalalias entry for www.quebecvirtuel.com.

Yes, I have done that, thanks, when I use Lee's offline page It loads perfectly with the domain name www.quebecvirtuel.com  even though it's redirected to port 8080. But for unkowned reasons the default.aspx probably loads but the web.config is not set corretly to handle port 8080.

I have checked the web.config. Theres is a setup for ports <> 80 you need to set to true... I have done so but no luck.

Other thing I need to let you know because it could have an effect on the situation  is that at installation time using your video for installation with vista and sql express 2005, after the Permissions tests next step test the database connection. I could never choose the choice you ask to tick. I had to  check the other choice (second choice).

Everytime I want to do a second iinstallation, it does not work. I need to re-install SQL express.

Does the PortalAlias also include the port number?  I seem to recall that it should.

You should NEVER have to reinstall SQL Server.  The problem lies elsewhere.

I made It, Thanks

I did put the port in my alias but no luck. Know I,ve added the router wan IP with port 8080.

I will test by removing one by one to see what is needed Exactly,

Thanks again !!

P.S. I wll put a new thread regarding the other problem of creating new DNN TEST installation.