This is the fix GoDaddy apparently did.
This is the file code for the .htaccess file if anyone needs it.
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
I also noticed in the .bak file GoDaddy saved of the file that crashed the site is the iThemes code and the code from WP-Supercache. I wonder if the somehow the combination of the two is in conflict.
**From what I understand**
Shared servers don’t like websites that use a lot of memory. WP is generally a static site that doesn’t put a lot of requests to servers, especially when you use creative caching techniques. But WP Security makes your site more ‘active’ in order to do things like log, and back-up and require more of the shared servers memory. More memory for your site, means less for other sites, which doesn’t allow GoDaddy (or any other low-cost shared host) to sell space on that server to as many clients. Thus, they get grumpy and try to move you to a WordPress hosting service for an extra $5/mo, or something like that.
I’ve found that clients are stuck disabling the memory intense portions of the plugin (which are well documented), switching to managed WP hosting, or paying more for VPS service where you can manage your memory usage. Either way, you’re not going to get a better product without paying more or becoming more clever than your hosting service.
However, it may be nice to remind them that the security of your site actually protects their servers from DoS attacks.. so they should encourage secure WP installations. Perhaps they’ll have some recommendations for you.. otherwise your vulnerabilities may cost them. :/ wa-wa
jpmizell,
Thanks for the reply. I have a lot of time trying to understand what is going on with this iThemes update fiasco and GoDaddy was using it to plug a new service. I can understand that, it’s business. However, it’s new service and some of people I have talked to at GoDaddy really don’t seem to have a clue about their new service. I have questions and they do not have answers and seem to just resort to some scripts they have memorized or in front of them.
The site is back up and running and for now I am just going to see what develops.
Hey JP, I’d like to look into the issue and your support experience a bit deeper. If you’re willing, please send me an email: mendel@godaddy.com with your account details.
Same thing is happening to me with a site hosted at GoDaddy. However, I have a couple other sites on the same virtual dedicated server that do not seem to be impacted.
I should note here the issue has long ago been resolved. GoDaddy had nothing to do with the problem and it was an upgrade from iThemes causing the issue.
The fix was to first deactivate the plugin and remove it from the MySQL database and the reactive it. That worked and I have had no issues since.
That said, GoDaddy did take the opportunity to try to sell me on their WP dedicated server. Still on the shared server.
@davidleblanc
Thank you for letting the community know.
As the issue seems to be resolved (and you are the topic creator) please mark this topic as ‘resolved’.
For anyone bumping this topic with ‘me too’ posts please start your own topic as per the WordPress.org forum rules/guidelines.
dwinden
