DNN on the Plesk!

The company I am working for has decided to host a website on a hosting with Plesk control panel.
For most websites, without pointing our DNS to this new IP, we can preview the site we create via the plesk sitepreview.
Our website is DotNetNuke-based.
To install DNN on the host, we copied the DNN website downloaded from www.dotnetnuke.com and put it under httpdocs/DotNetNuke directory (accessed via ftp).
We then created a virtual directory with the same name i.e. DotNetNuke and created a database to hold its data.
The connection string can be obtained via the control panel or you can contact the customer service for further assistance if you cannot find it.
To start configuring DNN, we then access the site via sitepreview expecting to see the DNN Wizard start page.However, DotNetNuke doesn't seem to like the sitepreview feature.Whenever we try to access the sitepreview, it redirects us to Godaddy's parking site (we host our domain with Godaddy).
Now what?If we can't access the site, how can we start setting up the DNN?This problem doesn't occur on a local machine since we can access the site directly (not via the Plesk sitepreview).After a few chats with the customer service, we realized that there is a way to fake our machines out to point to the live site IP address without having to go through the sitepreview.Yes! Modifying the hosts file is the solution.
Go to C:\WINDOWS\system32\drivers\etc (I presume that we have installed WINDOWS on c: drive). Or you can type %SYSTEMROOT%\system32\drivers\etc instead. Look for the hosts file named "hosts" (without any extension). Open it in your favorite text editor e.g. Notepad. Add the following lines after line. --> This is why it accesses localhost when we type as a url in the browser.
Please note that our domain is marathonsys.com.    marathonsys.com Save it and restart your browser (if opened). Now every time you enter www.marathonsys.com or marathonsys.com in your browser, it will access To access our DNN web site, use http://www.marathonsys.com/dotnetnuke or http://marathonsys.com/dotnetnuke for the url.
This is normally used to test our websites on a test server.
But it can also be used in this case :)
These settings may need to be removed after we point the DNS to this host. We can either remove the lines or just comment them out by putting a sharp sign (#) at the beginning of the lines as we can see at the beginning of the hosts file that they used it to put some comments in the hosts file.
I hope this helps anyone working with DotNetNuke on the Plesk.
Bookmark and Share