Learn More





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 ...Whoops. Should have posted here. GODADDY, shared hosting, extensionless url hotfix, primary url.Whoops. Should have posted here. GODADDY, shared hosting, extensionless url hotfix, primary url.
New Post
6/14/2016 11:54 AM

People have been saying over and over again not to use GoDaddy. I have successfully used GoDaddy for years to support multiple sites for multiple people.

I have always used a throwaway url to build a site, and then added a portal alias for the existing url when it was time to switch over. I easily made the existing url the primary url of the account. This wasn't working in the new plesk hosting. I had a fresh 7.06 install and then updated this to 7.4 something.

I called at 3:16 on Sunday to try to figure it out with Plesk. I had to totally rename the hosting account to get it to be the primary url. Once I did this I was getting 404 errors all over the place for every subpage. 

I investigated, tried things, and then called back at 5:05 to ask if the microsoft hotfix had been applied to the server:

Even though this was about extensionless urls, it fixed in that case. They said they would get back to me about the hotfix within 24 to 48 hours.


I called back at 11:40 on Tuesday to get an update to make sure that my request didn't go into a black hole. They had no ticket on file. It went into a black hole. They told me that they couldn't even TELL me if the hotfix was applied or not due to security reasons and because it was a shared hosting environment. They said no other hosting company would tell you if a hotfix was applied or not as well. I asked so no one can run extensionless urls on a godaddy shared hosting environment? They said DNN is not great at pathing, they couldn't help me, and go get support from DNN, without telling me what the server was running.

So, questions, has anyone successfully used the PLESK hosting to change the primary url on GoDaddy? Has anyone run extensionless URLs on GoDaddy (something that I want to do)? Am I just totally technologically inept?

Does anyone have equipvalent uptime, pricing, as GoDaddy who run friendly DNN servers where hotfixes are applied and they let you know that it can run DNN?

I have a MAJOR site where I need this question answered asap.

New Post
6/14/2016 12:12 PM

I am going back to the first primary to see if that fixes things, but I also found this:

ASP.NET Routing is a powerful feature introduced in .NET 3.5 SP1 and included with .NET 4.0 that allows a developer to route URL’s that are not real files. There are several ways you can accomplish this same task, but having it in the ASP.NET pipeline allows the developer great flexibility in how URL’s are routed. However, it does not always work “out-of-the-box” for devs. The most common error I’ve seen is a 404 error – meaning the page cannot be found.

There can be several contributing factors. If you are attempting to utilize extenionless URL’s, ensure you have the appropriate IIS hotfix installed: More commonly however, the issue is a result of the module not firing for your request type. The easy fix is to add runAllManagedModulesForAllRequests=”true” to the modules tag in your web.config. However, that could have performance implications as you are now telling IIS to ignore the preCondition setting for all modules. The alternative solution is to remove the managedHandler preCondition for the URLRouting module:

      <removename=UrlRoutingModule />
      <addname=UrlRoutingModuletype=System.Web.Routing.UrlRoutingModule preCondition=“”/>

New Post
6/14/2016 12:19 PM

Changing the name of the hosting account back to the name that I don't want it to be fixes the url problem. I can now get to all of the subpages of the site, but it doesn't have the primary domain name that I want.

New Post
6/14/2016 12:27 PM
if you want to modify primary domain address, you need to add the new one to the Site Aliases (in Admin > SIte Settings) and make it primary.

Cheers from Germany,
Sebastian Leupold (Microsoft MVP)

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group   European Network of DotNetNuke Professionals

Speed up your DNN Websites with TurboDNN
New Post
6/14/2016 12:34 PM
Sebastian, I did do that. It is the primary site alias, but the initial primary alias is listed below as well and it doesn't have a trash can next to it, so it is what the system is currently using. I have canonical redirect to the primary because, while it is a throwaway url, it still pertains. The site map goes to what I want to be the primary url, but the wrong url is showing up in the url locator box at the top of the page.
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Whoops. Should have posted here. GODADDY, shared hosting, extensionless url hotfix, primary url.Whoops. Should have posted here. GODADDY, shared hosting, extensionless url hotfix, primary url.

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.
Try Evoq
For Free
Start Free Trial
a Demo
See Evoq Live
Need More Information?