pictures

Jappler Recommends: Do Not Use iPowerWeb Hosting

hr
hr Heading 2 Icon Jappler Recommends: Do Not Use iPowerWeb Hosting

I have a lot of hosting companies - thanks to my clients who come in with all kinds of hosting companies. I have found that some hosting companies are better than others in terms of support and I just found another horrible support company that I wanted to mention: iPowerWeb. I was on hold multiple times today for over 30 minutes and I waited to “Live Chat” with someone for over 20 minutes. When someone actually got on and tried to help, after 1 hour, they told me they could not help me and had to escalate the issue. Yikes. (other hosting posts)

jappler recommends: liquid web.

hr
hr Heading 2 Icon jappler recommends: liquid web.

It has almost been two years since I moved all my sites to Liquid Web for my hosting needs and am still very happy with them. If you take a look at my hosting category, you can see I have been around the block a few times. I have had a few issues, BUT, everyone who I have spoken with is very knowledgeable, helpful, and always been on top of the issue. If you are interested in a new web host, I highly recommend Liquid Web.

not yahoo! over yahoo! web hosting.

hr
hr Heading 2 Icon not yahoo! over yahoo! web hosting.

I have enjoyed looking at multiple hosting options through clients in the last few months. Yesterday I worked with Plesk on one account and another who uses Yahoo! for hosting. Just as I was getting ready to write a positive blog post on Yahoo’s web hosting I ran into a snag when uploading and preparing the WordPress site for my client…Yahoo! does not allow you to use mod_rewrite Permalinks. So instead of having nice URLs like /services/ and /contact/ you have to use ?page_d=4. Gross. So in short - if you are using WordPress and want to maintain it yourself (always have the latest, most secure version, etc) I do not recommend using Yahoo! for WordPress sites.

jappler recommends: do not use godaddy.com for hosting.

hr
hr Heading 2 Icon jappler recommends: do not use godaddy.com for hosting.

Over the past few months I have had the chance to look at a number of hosting companies and their “control panels” by working with a number of clients. It seems as a number of people flock to godaddy.com because of it’s price (really cheap), but I have learned - once again - that you get what you pay for. If you want to have a very simple 1-5 page static web site, go for it - use whatever host you want. If you want anything else, after working with over 20 hosting companies, I can easily say that I would not go with godaddy.com. Why?

The admin area (control panel) is horrible in general. Not intuitive at all.
No backup on demand (or scheduled) available
Working with .htaccess files is a pain - as they do not work right away, there is a “wait time”.
The admin area (control panel) is slow and sometimes even times out
Free support is almost non-existent
Creating a database is not instantaneous
Paid support (talk to someone) is a joke (at least in my experience)
I am not alone in my recommendation

I could go on, but I have a busy day ahead of me. … [more]

mysql database corruption.

hr
hr Heading 2 Icon mysql database corruption.

What got me up early Saturday and then up at 1am on Sunday? Server hardware failure…which led to some database corruption. I have never had to deal with database corruption, so I did not even know my problem was database corruption until after calling the helpful tech guys at Liquid Web. (I am not one to usually call tech support, but at 136am on a Sunday…I did not feel like spending time at mysql.com or google.com.)

I first noticed something on Saturday morning, but after restoring a database table from a backup, everything was golden. I told myself…it had to have been from some user error. Monday morning, after my Nagios server paged me, I noticed that jappler.com had several mysql fetch_row () errors after the server came back up. I decided that this problem was not user error and something else was going on. As soon as I told the tech guy the error that I was seeing onjappler.com and other web sites I manage, he asked me if I had tried “repairing” the databases. I had not even thought about it (especially … [more]

web hosts, the journey continues once again.

hr
hr Heading 2 Icon web hosts, the journey continues once again.

Well, after multiple outages in the last few weeks, I think it is once again, time to move to another host. I had high hopes for Host Gator but I cannot handle too many more conversations with the tech support people because of outages. Next up: another go at a VPS account at Liquid Web. The conversion begins tonight.
[tags]web hosts, jappler.com, Host Gator, Liquid Web[/tags]

automate cpanel backup.

hr
hr Heading 2 Icon automate cpanel backup.

For months I have been manually backing up my web sites. Last night, I learned my lesson and realized I needed to have something more dependable in place. (and I am pretty damn dependable). I finally took the time to research the process of automating a CPanel update.
The script I found and used is freely available and easy to use.

How to completely automate your CPanel backup and store the files remotely:

There are three main parts to this process:

The backup script.

Download the script.
Edit the script's configuration variables as needed (see instructions on the download script page (see above).
Set up a cron job via CPanel (cron jobs is one of the main icons in the list) so your script will run every x minutes/hours/days/weeks/months.

The files you want backed up on your host. The script will have CPanel perform a full backup of all your files and databases. (The same if you were to choose "full backup" within the Backup module of CPanel.)
The location where your files go when they are automatically backed up.

Define the server/computer you want your files to get backed up to. If you are like ... [more]


search

subscription information

Blog RSS

Comments RSS



Powered by FeedBlitz

blog categories

blog tags

most popular posts


blog archive

standards

Get Firefox!
XHTML
CSS