Go Daddy

Rev. Voodoo,

I’m sorry to hear that your blog exhibits this issue. Rest assured, though, that it is not normal. Just today, I tested both a core update and a plugin update… each displayed the appropriate update text properly and completed in very short order.
If you’re curious to see this for yourself, you can always add a new WordPress instance to your hosting account in a subfolder. Use it as a testbed to see how a fresh install works on your specific server. If you still have this problem with a fresh install (no custom theme and minimal additional plugins), I’ll want our Hosting Team to take a look at it.
If you give it a shot, let me know how it goes by posting in this thread and, assuming you’re comfortable doing so, include a link to the blog or let me know how else to contact you privately.

vickistep,

As emke said, it shouldn’t make that much of a difference how many pages you have. Of course, there is technically a limit because there is a size limitation for a database, but I don’t think 400 pages would hit the one gigabyte limit. In terms of power, though, it doesn’t matter if you have an Economy or Deluxe plan. A Deluxe plan offers some additional features, like more disk space and concurrent users, but the available processing power is the same.
If the time ever comes when you do need additional power, you’d want to look into getting a dedicated server or our new Managed Hosting service. However, that usually isn’t necessary for a WordPress site unless very power-hungry plugins are used.

If you’re using a web.config file, you definitely don’t want to have one WP install in the root while there is another in a subfolder. This scenario may cause a problem because the web.config in the root will control the content in the subfolders. Instead, you would want to move the root instance into a subfolder (which seems to be your goal). It takes a couple steps, but it can be done. I explain below.
With that said, I would sooner recommend you switch to a Linux server to resolve your issue. Linux is generally better at handling PHP, which WP uses, and having a WP instance in the root of a Linux account doesn’t have this negative effect. Talk to a Support representative at GoDaddy.com before making the switch, but if you confirm switching to Linux wouldn’t adversely affect you in some other way, these are the steps for initiating the change: http://x.co/ZNTT
Note: If you do make this switch, make sure to set your permalinks setting to “default” after the switch, then set it back to your preferred setting. You must complete this step for each WP site in your account in order for permalinks to work after an operating system change.

If you prefer to stay on the Windows server, this is how you would change things to get the primary domain on your account hosted in a subfolder instead of the root:
First, change the primary domain name on your hosting account to some placeholder name. For example, if your domain is normally “domain.com”, try changing it to “domain_placeholder.com”. This change may take up to 24 hours to complete.
Once that’s done, just add the domain to the hosting account as you would any other domain. Keep the placeholder domain as the primary – your root folder would not need anything inside it other than the subfolders you use for the other domains and any other system-related folders GoDaddy.com creates for the account.
This article from our Help Center will help with changing the primary domain and adding/removing other domains: http://x.co/ZNTS

Saw your post. Glad you were able to get everything resolved. Don’t be afraid to call Support! They should always be willing to run some tests. Thanks for your patience.

Hema,

A 503 error usually means that there are too many concurrent connections to the website. However, unless your site is getting an extremely large amount of traffic, I wouldn’t expect you to hit that limit on an Unlimited plan. This plan can handle at least 600 simultaneous users, which is a lot.

If you think this really is a concurrent connection issue, you may need to consider getting a different type of hosting plan – ie, a dedicated server or an Instant Datacenter plan.

If you think that’s not the issue, I would recommend enabling error logs so you can research further. How to enable error logs: http://x.co/Z6aX
If you’re unable to determine the cause after investigating error logs, submit a trouble ticket to our Support team for review. You can do that from this page: http://x.co/Z6b5

I agree with duck__boy’s suggestion, but I also wanted to let you know that you can request a security review by the GoDaddy.com Security Team.

If you ever suspect there has been malicious activity on your site, just fill out this form – http://godaddy.com/securityissue – and your site will be reviewed. Depending the situation, we may clean the code directly, advise you to make certain changes, and/or provide other information that could be helpful to you.

Please don’t hesitate to take advantage of this service if and when you need it.

Yeah, this is definitely a bit confusing, but you can break it down to just a few important factors:

* The domain you want to use must be pointed to the proper hosting account. This is normally as simple as applying the appropriate nameservers for the hosting provider in question.
* The hosting account must be setup to use the domain name that you’ve directed to it. In other words, it needs to know that you sending domain X to it rather than some other domain.
* The WordPress settings need to have the correct path in both the “WordPress address” and “Site address” settings. These two are usually the same and normally just the domain name that you’re using for the site.

So, you said that domainB.com is using the HostGator nameservers. That’s step one. Now, you need to make sure that the hosting account at HostGator is setup to display a site for that domain. If you’re not sure how to do that or you want to check that it’s setup correctly, contact their Support team to help out. Once you’re sure it’s setup properly, confirm the two settings in WordPress are set for domainB.com, and that should be it.

Hi Sally,

It looks like you have gotten some helpful information from your peers. The articles that @cubecolour posted should solve the problem you are describing. ^Courtney