Go Daddy

I wouldn’t worry about losing your posts. Though the site may have been disabled, it would not be standard procedure for our staff to actually delete your data. You or your friend (whoever has access to the Go Daddy Hosting Control Panel for the hosting account) should be able to perform a backup of the database so you can get a copy for safe keeping or for migration to another server. Here’s a quick walkthrough for making a backup of a database on our shared hosting services: http://x.co/dNu6

Please note, though, that moving to a new provider is not necessarily the best solution. In fact, you may have similar issues at another provider if you get a similar hosting service without addressing the problem that your site exhibits – that is, overuse of shared hosting resources due to an overly intensive database query. It may be better to simply stop using the StatPress plugin and find another solution for tracking the stats of your site. If that is not an option and you’d prefer not to make changes to your site, you should consider moving to a more powerful hosting environment, like a dedicated server, where the impact of a query won’t negatively affect other users.

I hope this response is helpful to you. If you have any additional questions about how to proceed, the account holder can contact our Support staff for assistance or advice about managing the account in question.

Just to confirm the hosting account is all set up and good to go right? Sounds like you made the nameserver change correctly. Also just make sure your A Record IP is set to your hosting accounts IP address. To find your hosting accounts IP see: http://x.co/cntL To learn how to change your A Record IP see http://x.co/moddns Hope this helps! ^Colby Go Daddy Social Media Team

kwilsonoffice,

I could probably figure out what’s going on if I knew the domain name, but there’s another option – you could do an auto install using the Hosting Connection tool. If you’d rather do that, here are the instructions for how to do it: http://x.co/cICq
If you have any trouble with is, feel free to call Go Daddy Support. Contact info is here: http://x.co/cICy

jonrowe,

I just visited the site you mentioned in your initial post, and it appears to be working. Did you get the issue resolved? Can you tell us what the issue was and how it was fixed?

Well, I’m happy to hear that we got you past the importing issue 🙂 Thanks for coming back to let us know.

As for the speed, is there any chance you’re on a Windows hosting plan? If so, I’d recommend switching over to Linux for the best possible PHP performance (here’s how – http://x.co/bUpr ). If that’s not it, it’s possible there has been a load spike or some other condition that temporarily slowed things down. I agree, though, that contacting our Support staff is the best way to proceed.

This could be happening for a number of reasons. You probably have some old, vulnerable code on your site, but finding exactly what it is may be difficult. It is likely a plugin or theme, though it could also be vulnerable code elsewhere in your account (not necessarily in the affected WordPress site). Another possibility is that your hosting username and password have been compromised through malware on a machine you used to access your account. For this reason, I suggest you update anti-virus software and update the passwords associated with your GoDaddy.com hosting account and your WordPress site.

As for fixing your site, the best way to address this is to completely clear your account of all files and install a fresh instance of WordPress so you know it’s clean. Before you clear the files, you would backup your site’s database, the uploads folder, and any other files you customized (like your theme’s css files). Check the uploads folder to make sure only images (and any other file you might have uploaded for your site) are there. If you find rogue php files, they should be cleared too.

If you’d prefer that Go Daddy’s Security Team investigate the cause and assist you with cleansing the site, we do offer a Security Scanner service. You can learn more about this service at http://x.co/bPMW

SteveNetRivet,

I’d like to investigate the specific account you’re referring to, but I need to know the domain name. Have your clients’ interactions with our Support staff been on the phone or through email? If they were through email, could you post the Incident ID number here so I can find it and review the situation? If there’s no existing incident, you can create one here – http://x.co/heretohelp – or just post the domain name in this thread.

For the record, the issue users were experiencing when this thread began has been resolved. I can only guess that what your client is seeing is caused by something different even if it results in the same symptom. Furthermore, if FastCGI is an option on an account, there should always be an option to disable it. Yet another reason I’d like to look into this myself – if there’s something unusual or unintended going on with the account, I want to catch it as quickly as possible.

I hope to see your response soon.

Generally speaking, in order to avoid email disruption, you just need to make sure that your MX records do not change during the process. Note that MX records are defined in the zone file, and the zone file is stored on your nameservers.

So, what you need to do is make sure that a zone file is setup and assigned the proper MX records prior to changing the nameservers to your new provider.

[removed the advertising]