Stablehost hosting

Had to move (and hosting today.

My previous two IPs on (WHP) had all sorts of, um, adult-sounding website names (DirtyWivesClub? euroButts?),, and more recently [interestingly, it looks like WHP moved my account on their own volition as of mid-March, about a month after I switched the traffic to Stablehost, to webhosts sometimes (finally) figure out loading issues on their own?]. WHP was very inexpensive, unfortunately I ran into problems back in early 2016 that were resolved by moving my account (but I had to nag them to do it; but did cause trouble for a week or more until they finally acquiesced to move my account to another server.  Everything was fine for a year or so, until Feb 2017 when performance problems arose again, so I jumped ship to Stablehost, which is about twice the price, after a “50% off” coupon (that recurs) through WebHostingTalk forums.

Prices comparison of old vs. new hosting, updated 5/9/2017:

  • WebhostPro “Easy” $3/mo (drops to $2/mo for 24 months — they’ve always limited to 5GB storage, but recently reduced the number of hosted sites to two, which would no longer be enough for me. They typically have a new customer promo of 20% off — but I assume that doesn’t recur.
  • Stablehost “Unlimited Pro” $9/mo (drops to $8/mo for 24 months — but was “lifetime” 50% off the published rate with the code mentioned above. The number of hosted sites, and storage amount are supposedly unlimited.

The new server certainly has very few sites on its IP, only 9 as of today. Stablehost has a datacenter in Phoenix, for what it’s worth… but they are filling it up, there are 113 on 5/9/2017.

Looking back at traffic, there is a LOT of ‘bot traffic; crawlers / spiders / scrapers and just plain malicious scripts probing for vulnerabilities. I did finally install and turn on caching (supercache) and that makes a big difference. I also blocked all but the IP address where I usually am for wp-login (that doesn’t help xmlrpc.php attacks by the way; wordfence does throttle that, too though).

Moving wordpress installations went ok. WHP uses installatron, and Stablehost uses softalicious as installation and backup managers but both have more-or-less the same functionality. I used an installatron backup to “overlay” a fresh softalicious install; having only to adjust the db prefix, and database names. Other minutia a few places supercache plugin refers to the full pathname (was /home/azbikela, now /home/bombercu) that needed adjusting.

Softalicious / Softaculous

WHP used Installatron for the same functions, it’s a script installer, management and backup tool. The backup in Installatron is better, more choices, e.g. it had the option a combined daily / weekly / monthly rotations.

The Softalicious backup system seems to work okay. I have initially set it to do daily backups, and retain no more than four. Curiously, so far anyway, the backup for azbl blog consistently happens at 1218p local time (phx, which is handily my time zone, as the server is located in a phoenix area data center), and  the cazb blog fires every day at 1006a.  [Update: sometime in April, Stablehost turned OFF softaculous’ automated backup feature. That sort of irks me, but can still make manual backups anytime, and for any sort of crisis situation, Stablehost has a pretty fancy self-serve restoration tool called R1 Soft  and they keep full daily backups for it looks like 6 weeks or so. I used this to restore my wordpress installation when jetpack pushed out a bad update]

This activity consistently causes a couple of minute CPU spike to 40 – 50%, a brief I/O spike, a fault or two, and a bump of ~ 100MB phy mem usage

Backups are stored in ~/softaculous_backups

Random Issues

The issues below like Eliminate 404’s and wp-cron, supercache are what i did to attempt to optimize performance…

Eliminate 404’s?

404’s cause wordpress to get involved: lots of overhead, (i would guess?) and returns a large file (relatively speaking).

I was seeing thousands of requests for apple-touch*.png per month, so I generated a set of such icons and placed them in the root of There’s a cleverer way to put just one and use .htaccess rewrite to use just one file but whatever.

Fixed / straightened out some missing css references under the articles folder.

I get a lot of  these and return 404, not sure what to do? : /?author=1 (and 2, and 3 and all the way to 14! )

Disable wp-cron

I did this but I’m not sure it’s a good idea. The concept is to replace a call to wp-cron that supposedly fires with every request that wp handles with a “real” cron job which simply executes wp-cron.php on some schedule; e.g. every 4 hours or whatever. It involves adding a line in wp-config.php, and adding a cron job through cPanel.

The plugin crontrol can be handy; it displays the list of wp-cron jobs. Unfortunately it doesn’t have any sort of history (that i can find), that would be handy.


This is the most-obvious step to take to reduce shared hosting resoucrce issues/problems. Tried W3 Total Cache but didn’t like/understand some of its features. Then moved on to SuperCache.  At the moment it’s configured with mod/rewrite (works completely without wp intervention once it’s cached) on azbl; and for variety with php caching on cazb.

When using mod/rewrite, the location of the cache files must be within the root of the domain being cached; but with php (the default/recommended) they can be moved anywhere in the home directory of the account. This is better in the sense then the cached files can be separated and therefore not backed up by softaculous; the cache files quickly grew to ~ 20MBytes per installation. So they were moved here (and also exclude the wp_cache folder in the cPanel backup file :


cazb ‘Cache Timeout’ is disabled (‘0’ seconds) and runs once a day a 0222am; I doubt it causes a noticeable load, but I can check just in case.

azbl is still mod/rewrite. but timeout and garbage is as above except 0444am.

Stablehost Update, a few months later

Working well, performance seems good, I haven’t tweaked out supercache but doesn’t seem necessary.



I tried to use WHP email back when I switched from godaddy to WHP (2015?). This was a disaster, as apparently since WHP is, ahem, less discriminating in the types of customers they have, they end up with spammy customers sharing the same IP, and this in turn causes the server’s (WHP’s server) IP to be blacklisted by various spam filters. The simple/easy answer is to (continue to) keep the domains (,, etc) registrared at Godaddy, and use godaddy’s free email forwarding. Works like a charm.

I haven’t tried since to try and find out if perhaps Stablehost’s servers are better (better at not being blacklisted). They are probably ok.



One thought on “Stablehost hosting”

  1. This type of “attack” is enough to cause a spike to ~ 80% CPU utilization for a minute or two	[13/Mar/2017:01:50:46	-0700]	GET /FCK/ HTTP/1.1	404	18723	-0	-0	[13/Mar/2017:01:50:47	-0700]	GET /FCKeditor/ HTTP/1.1	404	18729	-0	-0	[13/Mar/2017:01:50:48	-0700]	GET /admin/fck/ HTTP/1.1	404	18729	-0	-0	[13/Mar/2017:01:50:49	-0700]	GET /admin/fckeditor/ HTTP/1.1	404	18735	-0	-0	[13/Mar/2017:01:50:50	-0700]	GET /ckeditor/ HTTP/1.1	404	18728	-0	-0	[13/Mar/2017:01:50:51	-0700]	GET /common/fckeditor/ HTTP/1.1	404	18736	-0	-0	[13/Mar/2017:01:50:51	-0700]	GET /editor/ HTTP/1.1	404	18726	-0	-0	[13/Mar/2017:01:50:52	-0700]	GET /editor/fckeditor/ HTTP/1.1	404	18736	-0	-0	[13/Mar/2017:01:50:53	-0700]	GET /editor1/ HTTP/1.1	404	18727	-0	-0	[13/Mar/2017:01:50:54	-0700]	GET /editorold/ HTTP/1.1	404	18729	-0	-0	[13/Mar/2017:01:50:55	-0700]	GET /fck/ HTTP/1.1	404	18723	-0	-0	[13/Mar/2017:01:50:56	-0700]	GET /fckeditor/ HTTP/1.1	404	18729	-0	-0	[13/Mar/2017:01:50:56	-0700]	GET /fckimg/ HTTP/1.1	404	18726	-0	-0	[13/Mar/2017:01:50:57	-0700]	GET /images/upload/FCKeditor/ HTTP/1.1	404	18743	-0	-0	[13/Mar/2017:01:50:58	-0700]	GET /images/upload/fckediter/ HTTP/1.1	404	18743	-0	-0	[13/Mar/2017:01:50:59	-0700]	GET /images/upload/fckimg/ HTTP/1.1	404	18740	-0	-0	[13/Mar/2017:01:51:00	-0700]	GET /inc/fckeditor/ HTTP/1.1	404	18733	-0	-0	[13/Mar/2017:01:51:01	-0700]	GET /include/fckeditor/ HTTP/1.1	404	18737	-0	-0	[13/Mar/2017:01:51:02	-0700]	GET /includes/fckeditor/ HTTP/1.1	404	18738	-0	-0	[13/Mar/2017:01:51:03	-0700]	GET /js/fckeditor/ HTTP/1.1	404	18732	-0	-0	[13/Mar/2017:01:51:04	-0700]	GET /manage/fckeditor/ HTTP/1.1	404	18736	-0	-0	[13/Mar/2017:01:51:05	-0700]	GET /scripts/fckeditor/ HTTP/1.1	404	18737	-0	-0	[13/Mar/2017:01:51:07	-0700]	GET /sysadmin/fckeditor/ HTTP/1.1	404	18738	-0	-0	[13/Mar/2017:01:51:09	-0700]	GET /system/fckeditor/ HTTP/1.1	404	18736	-0	-0	[13/Mar/2017:01:51:10	-0700]	GET /upload/FCKeditor/ HTTP/1.1	404	18736	-0	-0	[13/Mar/2017:01:51:11	-0700]	GET /upload/fckediter/ HTTP/1.1	404	18736	-0	-0

Leave a Reply

Your email address will not be published. Required fields are marked *