Below is the step by step guide to install DotNetNuke on GoDaddy.
1. Login to your GoDaddy account and browse to GoDaddy Hosting Connection® (the Application Management Page).
2. Search/Find DotNetNuke in the Content Management Category.
3. Click Install and follow the installation wizard. You will need to choose/fill up:
- Domain name.
- Database name and password.
- Installation directory. Note: I normally create a directory for each domains and install DNN to the domain’s directory.
- Super-user name and password.
- Admin user name and password.
4. Wait for the installation to take place. It normally takes about 30 minutes to install, you can check the status at your GoDaddy Hosting Connection.
5. Browse to your domain and follow through the installation wizard (Yes, you need to go through another installation to fully deploy your DotNetNuke. 
). In case you bumped into “Error 500” like me, don’t worry; please follow the instruction below. Otherwise, skip to Step 12.
6. If you bump into “Error 500” like me, we have to make some minor changes in the web.config file.
7. Use FTP tool (like FileZilla) to download your web.config file and turn on “CustomError” configuration in your web.config file. Read another post written by me on “How to turn on CustomError”.
8. Surf to your domain again; if you did Step 7 correctly, you should be able to view the details of the error (like the sample below).
9. Let’s try to debug these errors one at a time. The errors are normally generated by IIS because of “… duplicate collection entry of type ‘add’ with unique key attribute ‘name’…”.
10. So, add a ‘remove’ tag before the ‘add’ tag will normally helps. Take for example the error above (Config Error: Cannot add duplicate collection entry of type ‘add’ … set to ‘ScriptHandlerFactory’.) can be fix by:
<system.webServer> <handlers> <remove name="ScriptHandlerFactory" /> <add name="ScriptHandlerFactory" verb="*" path="*.asmx" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" /> </handlers> </system.webServer>
11. Re-upload the latest web.config to your domain’s directory and re-refresh (Ctrl+F5) your website. Repeat Steps 9 & 10 until you clear all the errors. Below is my web.cofig to remove all the errors.
<system.webServer> <asp scriptErrorSentToBrowser="true"/> <httpErrors errorMode="Detailed"/> <modules> <remove name="ScriptModule"/> <add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" preCondition="managedHandler" /> <add name="Compression" type="DotNetNuke.HttpModules.Compression.CompressionModule, DotNetNuke.HttpModules" preCondition="managedHandler" /> <add name="RequestFilter" type="DotNetNuke.HttpModules.RequestFilter.RequestFilterModule, DotNetNuke.HttpModules" preCondition="managedHandler" /> <add name="UrlRewrite" type="DotNetNuke.HttpModules.UrlRewriteModule, DotNetNuke.HttpModules" preCondition="managedHandler" /> <add name="Exception" type="DotNetNuke.HttpModules.Exceptions.ExceptionModule, DotNetNuke.HttpModules" preCondition="managedHandler" /> <add name="UsersOnline" type="DotNetNuke.HttpModules.UsersOnline.UsersOnlineModule, DotNetNuke.HttpModules" preCondition="managedHandler" /> <add name="DNNMembership" type="DotNetNuke.HttpModules.Membership.MembershipModule, DotNetNuke.HttpModules" preCondition="managedHandler" /> <add name="Personalization" type="DotNetNuke.HttpModules.Personalization.PersonalizationModule, DotNetNuke.HttpModules" preCondition="managedHandler" /> <add name="Analytics" type="DotNetNuke.HttpModules.Analytics.AnalyticsModule, DotNetNuke.HttpModules" preCondition="managedHandler" /> <add name="RadUploadModule" type="Telerik.Web.UI.RadUploadHttpModule, Telerik.Web.UI" preCondition="managedHandler" /> </modules> <handlers> <remove name="WebServiceHandlerFactory-Integrated" /> <remove name="ScriptHandlerFactory" /> <remove name="ScriptHandlerFactoryAppServices" /> <remove name="ScriptResource" /> <add name="LogoffHandler*" path="Logoff.aspx" verb="*" type="DotNetNuke.Services.Authentication.LogOffHandler, DotNetNuke" preCondition="integratedMode,runtimeVersionv2.0" /> <add name="RSSHandler" path="RSS.aspx" verb="*" type="DotNetNuke.Services.Syndication.RssHandler, DotNetNuke" preCondition="integratedMode,runtimeVersionv2.0" /> <add name="LinkClickHandler" path="LinkClick.aspx" verb="*" type="DotNetNuke.Services.FileSystem.FileServerHandler, DotNetNuke" preCondition="integratedMode,runtimeVersionv2.0" /> <add name="CaptchaHandler" path="*.captcha.aspx" verb="*" type="DotNetNuke.UI.WebControls.CaptchaHandler, DotNetNuke" preCondition="integratedMode,runtimeVersionv2.0" /> <add name="ScriptHandlerFactory" verb="*" path="*.asmx" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" /> <add name="ScriptHandlerFactoryAppServices" verb="*" path="*_AppService.axd" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" /> <add name="ScriptResource" verb="GET,HEAD" path="ScriptResource.axd" preCondition="integratedMode" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" /> <add name="Telerik.Web.UI.WebResource" verb="*" path="Telerik.Web.UI.WebResource.axd" type="Telerik.Web.UI.WebResource, Telerik.Web.UI" /> <add name="Telerik.Web.UI.ChartHttpHandler" path="ChartImage.axd" verb="*" type="Telerik.Web.UI.ChartHttpHandler, Telerik.Web.UI, Culture=neutral, PublicKeyToken=121fae78165ba3d4" /> <add name="UserProfilePageHandler" path="User.aspx" verb="*" type="DotNetNuke.Services.UserProfile.UserProfilePageHandler, DotNetNuke" preCondition="integratedMode,runtimeVersionv2.0" /> <add name="HtmTemplateFileHandler" verb="*" path="*.htmtemplate" type="DotNetNuke.HtmlEditor.TelerikEditorProvider.HtmTemplateFileHandler, DotNetNuke.HtmlEditor.TelerikEditorProvider" preCondition="integratedMode" /> </handlers> <validation validateIntegratedModeConfiguration="false" /> </system.webServer>
12. Follow through the installation wizard to fully deploy your DotNetNuke.
13. Below is the summary of what I did/choose in the installation wizard.
- Typical installation.
- SQL Server 2005/2008 Database.
- Copy the given Database Name, Database Server Path and set the Database password (Note: Please use the same password set in Step 3).
- Setup the Super User account.
- Setup the Admin/WebMaster account.
14. Ta-Daa~! Your DotNetNuke powered website is now online. Thanks! Good luck in WorldWideWeb!
I don’t get paid for writing blog posts. Your “Votes” and “Like” is my only motivation, so please “Like” it if you found this information useful. Cheers!!! Check out what other says about this post by clicking at the title of this post. Wondering what I’m up to recently? Check out mySoftinn.com
Tagged: DNN, DNN 5, DNN GoDaddy, DotNetNuke, DotNetNuke GoDaddy, GoDaddy, How to setup DotNetNuke
[...] Go here to see the original: How to setup DotNetNuke on GoDaddy. [...]
Lifesaver, thanks! you rock
Good Morning
I have installed dnn for godaddy but cant seem to get my skin to upload with containers. Do you offer a service to fix some of these issues for me?
Let me know – just need this skin up and going by wednesday
JD
360-708-0056
Hello JD,
I do not have experience helping others in fixing their DNN setup before but I could try.
Send me your web address, username, and password. I will try to fix it. Please send this info to my mail: jeeshenlee@gmail.com
Are you using your own skin? Or using a downloaded skin?
Thanks.
I followed your instructions and they work flawlessly. Thank you.
However, I am having real trouble with getting simple stuff to work (like if I was hosting my own IIS server).
Such as, http://www.gomerrill.com won’t resolve. And you can’t add it as a subdomain. I’ve been staring at Hosting Control Center for nearly an hour and don’t see where GoDaddy allows you to put in what I call an IIS website “Alias” of “www.gomerrill.com”.
For that matter, I can’t get gomerrill.com to resolve to the virtual directory it makes you set up (ROOT\DOTNETNUKE). I am forced to type in “gomerrill.com/dotnetnuke” to get to DNN.
I called GoDaddy techsupport and their suggestion was to put a html redirect in the root, which is nonsense.
Am I missing something blatant? Can you point me in the right direction?
JMM
Hello JMM,
Have you tried looking at the Settings in DNN? You can control how the url is digest in DNN.
Hope this help.
Regards,
JeeShen Lee
that is absolutely fantastic!!! Thank you for saving my hours! Even godaddy support was unable to understand what is going on. shame on them!
hi jeeshenlee , how i can control how the url is digest in DNN??
please help me, i speak spanish, so i need your help!!
very much appriciated boss
I am at my wits end with Godaddy, it turns out you have to place DNN installation in a sub folder, and then have a HTTP redirect meta tag in the root folder. This doesn’t make sense. How on earth do you just point your primary domain at the DNN installation without having to set up sub-domains or redirect? Hope you can help!
I can do the basic install and all seems to work right, but cannot get a new portal to work – updates to a portal affect the host site and vice versa and links from the new portal end up on the host site, usually with a 404 because even the out of the box HOME link is doubling the dnn install directory in the paths. I need hel
now i m trying to install DNN 6.2 but it gives different error and there is no such file web.confing too
Thanks for sharing your thoughts on flaky. Regards