In my last post about the server side of my website (Version 3.3 of my websites: the technical side of things and Version 3.3 of my websites: the software side), I talked about a problem I was having with GreenGeeks that they couldn’t solve. It was a lot more complicated than just one problem, or even their laissez-faire approach to changing settings on my site without telling me, it was more of a governance issue and I finally had to bail on them. I’m still using them for one site that has low traffic, just until the prepaid balance is used up, and then I’ll migrate it over to my new host.
Because I did indeed find a new host, as I said…I moved to WebHostingCanada. And things were going along pretty well with them.
I had an error at one point, one that I haven’t resolved yet, where my WP-CRON (the file that regularly runs a set command at a set time) doesn’t want to post “scheduled” posts. So, for example, if I write a post, and I want it to go live at 8:00 a.m. tomorrow, you use the schedule feature in WordPress and at 8:00 a.m., or shortly thereafter when WP-CRON runs, it notices a pending post, and switches it to live. Or it is supposed to. For some reason, while some of the Cron features work for other things, it won’t “schedules” my posts to go live and actually make them live at that time (it schedules them, it just doesn’t do it). Like an alarm clock that just doesn’t go off when it should.
Not a giant issue, I rarely schedule posts that way, and when I do, it’s often part of a larger strategy that requires manual intervention anyway.
Then I upgraded to a new version of WordPress. Then another. All good.
Then I went up to a version where suddenly I couldn’t save my updates. It was like the auto-save would start as I was typing, and never complete. So when I went to later save, it wasn’t able to “activate” when I pressed “update”. Other people were having this too, with nobody seeming to have a solution.
Now, the normal way to resolve this is to go to your plugins and deactivate everything. Check again — if it works, then you have a plugin conflict; if it doesn’t, it likely means it is something else (* remember this asterisk). You then move along to themes, switch to a basic theme, see if the conflict goes away. Etc. It helps you narrow down to what is wrong. If you disable your theme and your plugins and your connections to just about everything, it might be a server problem, something wrong with your config.
Which is where I was looking for solutions. Because disabling my plugins and theme didn’t resolve the problem. But my server settings all looked fine.
Except for one small glitch. My server load was high. Now I had this before with Greengeeks when running Piwigo and WordPress, and they thought it was some sort of outside attack. Webhosting said “nope, not that”, this looked more like a config problem to them. So I got a phone call from them noting it was really high and asking if they could log in and check a few things. They weren’t spammers, they didn’t need my credentials, they just wanted permission before they started poking around.
I was like, “hell, yeah”. Greengeeks went in, poked around and changed things, without asking or even telling me. Here Webhosting Canada was, phoning me in person to ask if they could look around my setup and see if there was anything going on. I walked the guy through the background, stuff I’d tried in the past, and off he went. I wished him luck, as this could have been a rabbit hole.
He found the problem in less than 3 minutes. As soon as he saw one of the security files set up by Better WP Security, it was clear what the problem was. The file was HUGE, and it was calling itself. So every time I logged in or even loaded a page, it would go into an almost perpetual loop of constantly checking and then rechecking and then rechecking itself again. He tweaked the file, disabled the plugin, and the load dropped to normal. It was just that one plugin.
Now, back to that asterisk. Disabling the plugin hadn’t helped. Because disabling it didn’t undo the security file changes. The plugin wasn’t active, but the huge file was still being triggered. Undoing those changes and making the changes relatively straightforwardly with another security plugin to do the same thing worked PERFECT.
And my editing / saving problem went away too.
Their totally different attitude to solving the problem made all the difference for me. And while diagnosing WP problems is not their job, that’s a config problem, they did it at no charge.
I feel somewhat unfair now about the previous hosts. They had the same issue but no idea how to solve it, and all evidence was pointing to a server problem, not a software config problem. But the guy found it in under 3 minutes once he stepped outside the normal “not my problem” box that most tech supports have. Back when I was working tech supports, it was the same “not my problem” attitude of others that drove me batty. And my alternate “let’s see if I can help with anything else while I’m here” attitude is what made me popular with my clients.
Thumbs up to WebHosting Canada. The site’s working great. WP-CRON is still acting up, but I can live with that for now. And it gave me the confidence to merge the two sites into one (#50by50 #02 – Who am I when I’m online?). I also reconfigured the categories and groupings into Government (Civil Service, Development, Government), Hobbies (Astronomy, Computers, Humour, Ideas, Learning, Photography, Quotes, and Recipes), HR (HR Guide and PS Transitions FP), Personal (Experiences, Family, Goals, 50by50, Spiritualism), Reviews (Book Reviews, Music Reviews, TV reviews), Writing (Libraries, Publishing, Art of Writing) and Links.
I’ve also decided to be a little less demanding re: the “one category per post” rule that I’ve been doing, it’s hard to find things sometimes where I’m talking about a goal that pertains to one of the headings, for example — is it a post about goals or a post about the hobby?
I’m liking the new design, and trying to be a bit more flexible.
Often it is because one feature of the site works REALLY well, and draws me in a certain direction, only to later have that feature either be less important relative to other features, or just stop working well. Sometimes it is an issue with the hosting company.
I didn’t do separate blog entries for version 3.0 where I basically had WordPress all up and running, or version 3.1 where it was a combination of two WordPress sites, one Piwigo subsite for photos and videos, or even version 3.2 where I merged it into 1 WP site and one photo subsite. Things were working pretty well, and I had transitioned over time from Spelunking Web Design (too little bandwidth and storage) to Netfirms (solid for a while until I ran into some config issues with storage) to Greengeeks (which let me host all my pix and integrated well with Google Storage for video). Usually when I have transitioned from one site to another, it has been either my needs outgrowing the basic offerings or the costs associated with my needs being much cheaper elsewhere. Each hoster has slightly different rules and offerings, and as my needs changed, I switched to keep costs down on what are basically personal sites with no commercial value.
This past year though, going back to February, I’ve had a small battle with Greengeeks. Things were going along mostly fine, after I had switched to them last fall (Cutting the cord – Part 5 – Internet hosting). Then, suddenly, things weren’t fine.
The beginning of the end of a relationship
I had consolidated my previous two WordPress sites — polywogg.ca and thepolyblog.ca — into a single site (polywogg.ca and redirected thepolyblog there too), and with the previous focus of what the two sites were about, I was able to more cleanly integrate them. It just made sense at the time for me to have everything together, no need to separate out “personal” from more “professional” musings, and separate menu options to help keep things sorted.
But then I noticed a problem in February with something rather small initially. I was running a “to do” list app on the site…well, actually three of them. One for work, one for personal, one for “other”. Plus a calendar that my wife and I could share. Like with hosting my photos on the site, it seemed to me that if I had a whole site to myself, why would I use other sites, commercial or otherwise, to host my info?
One day I went to do something on the to-do list and the subsite wouldn’t load. Dead. Fatal errors out the wazoo. This was odd, it had been working the week before just fine. Two other lists were also “dead”. And the calendar. WordPress loaded fine, but the look was a bit off. I checked the photo site and it too was acting weird for layout. Connected to the help desk, asked a few questions, and they located the problem almost immediately. They had auto-upgraded my site from PHP 5.6 to PHP 7.0.
If you’re a layperson, you might think, “Sweet! Free upgrade!”. If you’re a little more knowledgeable about sites, you might think, “They upgraded you automatically?”. And if you’re way more hardcore than me, you likely are thinking, “WTF??? Why would they upgrade you automatically? Did they tell you so you could test your config? What kind of hoster would change your site without warning, notice or testing?”. Guess which camp I fell into.
The upgrade broke my todo list installs and the calendar as they weren’t 7.0 compatible. WP’s core is 7.0 compatible, but all the plugins apparently were not. Hard to tell, precisely, but WP was a bit off. PiwigoPress, that I was using for my photos, also didn’t completely like the upgrade tweak in the background, but I’ll come back to that.
They switched me back to 5.6, lists seemed fine, calendar loaded, everything else worked, it seemed like “no harm, no foul”. At first. Then about a week later, I started noticing my photos didn’t seem to load properly. The layout screen for a gallery, for example, would load, but not all the photos. Some were just placeholder symbols in Firefox, Chrome and Internet Explorer/Edge. Definitely a server issue if all three were treating it the same. But it wasn’t consistent. Sometimes everything would load fine. Home seemed fine, work seemed more intermittent. Then I tried it on my tablet, worked great. Decided it was a temporary bandwidth issue, moved on.
Then I uploaded a batch of new photos, and all hell broke loose on my site. Pics wouldn’t render at all, any format, any location, any connection. It just did NOT want to load right at all. Then some would, others never. I tweaked, I checked, I tweaked, I checked. No idea what was wrong. I hadn’t changed anything in almost two months, but now, suddenly nothing worked? I went back to Greengeeks support to see if anything else had happened? Nope.
The larger investigation begins
I thought it might be the PHP version, as they were going to phase out lower support. So I transitioned all my lists to a new app/site temporarily and then from there more recently to one called TickTick. Accessible from work, comes with app, updates in real-time reliably between Andrea’s phone and mine (we share shopping lists for groceries, for example, so she can make the list and I can buy the stuff), good toggle options to switch things on and off. I moved our calendar to Sunrise, which then was closing shop, and now to Google, since we can both run reliable apps to synch. So I was down to just WP and Piwigo, and they seem to like 7.0 reasonably fine.
Yet wonkiness remained. Over time, I narrowed a feature down that wasn’t working in Piwigo. Photo conversion wasn’t working right. It didn’t seem to be adjusting the size, and the rendering was taking forever.
Apparently, unbeknownst to me, the switching from 5.6 to 7.0, and then back, was not a simple switch. The switchback was actually a complete reset of some sort. Features in PHP setup that had been “on”, like one called GDIMAGE and another like IMAGEMAGICK, were now switched off by default. Now that is not something I would ever play with — once I get the initial setup right, there would be no reason for me to go into that extremely technical side of the configuration. It’s almost like going in and editing the Registry in Windows. You *might* have to do it for something specific, but rarely manually. And I found the default change by accident.
Why would they matter? GDIMAGE and IMAGEMAGICK are library functions for PHP (not quite the right term, but close enough) that add image conversion to the list of things PHP can do. Such as enabling Piwigo — I uploaded photos in one size, and it would convert them to other sizes so you have the thumbnail for small viewing on one type of layout, medium for another, large for a third, and then the full image (if you tell it to keep it, which I did). I had unlimited storage, and having those different sizes is supposed to make everything load better/quicker without having to do resizing on the fly.
But with them off, Piwigo wasn’t working right. It was trying, but I configured and reconfigured things out the wazoo before I found the missing libraries problem. Then I tried to put everything back to the way it had been, but things still weren’t quite right.
I started getting warnings that the server load was too high. Too high? How could that be? I had a WP site that had double-digit visitors on a good day, another that had visitors once or twice a year that I host for someone else, and a photo site that might have visitors once a month. No way could I be overloading the server. Yet the logs didn’t lie. 10K hits in a single day, most asking for pages that didn’t exist, lots of redirects, some attempts to log in. Spam attack in some ways, access attacks in others, and just a lot of pic loading. Sort of. Some of it was just Piwigo still struggling with the load to convert graphics sizes.
Greengeeks and I started a series of exchanges as we tried to nail down the problem. They, like any bad hoster, start with the premise that it’s all the user’s fault and that they didn’t do nuttin. Except they had. The original PHP switcheroo. Then, on a regular basis, they would try to help, and they would tweak a setting they thought would help. Except they would do it without telling me. I would be in the middle of testing multiple configs, resetting things, and suddenly one of my changes looked WRONG. Something that shouldn’t have caused that change. I’d undo it but the change would remain.
And I would go down a rabbit hole for a couple of hours or even days trying to figure out WHY that changed with my changes, only to find out it wasn’t my change. It was them changing background settings in the middle of my testing and not telling me. Meaning I would have to go back to the beginning and start the testing all over.
I was getting increasingly hostile about their support. Particularly after they swore it was PiwigoPress causing the problems. I finally gave access to one of the actual developers to check the config directly, something I was floored he was willing to do. I had been all over the Piwigo forums trying to find a possible cause, and then he offered to check since none of the things I was looking for should have been the problem. Everything was set properly. No issues. And Piwigo is being run on literally hundreds of thousands of installs without issue. The problem was NOT Piwigo.
I finally started to figure out what had happened. This is a bit simplistic and misleading description, but basically it was a combination of several features. WordPress liked PHP 7.0 but a security plugin within WordPress did not. Sort of. It basically changed the way it handled sub-directories — since my WP install was at the equivalent of WWW.SITE.CA, and my Piwigo was in WWW.SITE.CA/PHOTOS, the WP security plugin was trying to control the photos site too. It wasn’t designed to do that, but it wasn’t expecting virtual subdomains to be located below the main root. At least as far as I can tell. Equally, the PHP 5.6 to 7.0 to 5.6 switcheroos turned off my image processors, which sent Piwigo into a tizzy. Between the two, i.e. the image processing and the overly active security plugin, I was really struggling to find the source of the reconfiguration issue.
Adding in multiple changes without Greengeeks telling me they changed something, the problem was impossible. I couldn’t be sure my “testing” was working, and frequently it wasn’t — cuz they changed something in the middle of my efforts.
Ratcheting up to a governance issue
This seems like an odd way to describe it, but I was now dealing with a governance issue. I explicitly told them they could do diagnostics if they were helping, and identify things I might look at, but UNDER NO CIRCUMSTANCES were they to make any further changes to my actual setup. They did anyway.
So I opened a ticket of complaint. Someone deleted it. Literally, it disappeared out of the tracking system. I opened two new ones — one with the same info and one to find out what happened to my original ticket. Both were deleted.
At this point, the relationship was basically toast, but I’ve paid for three years worth of hosting to get the lowest price, and while I’m willing to eat that cost (decided that upfront when I paid it), I wasn’t willing to go gently into the night. I tweeted a couple of their major customers who provided testimonials on the “greatness” that was Greengeeks, I tweeted their CEO, I tweeted their IT specialist. Suddenly people started paying attention to my tickets.
I didn’t get any better service, but they were at least paying attention. Now, separate from the pain and frustration, many of you might jump to the obvious two solutions:
Kill the account, move on;
Delete everything, reinstall from scratch.
I was hoping for (2) still, but there’s a small problem with that plan. I had no way of knowing that if I got it all working and installed right, another change from GG wouldn’t come along and swamp my setup. So I wanted to know how to mitigate that risk. I started asking a series of Qs of the tech group that I wanted answered sequentially so I could get to the point where I would say, “Okay, if I blow off WordPress, and reinstall, AND I blow off Piwigo and reinstall, how do we do this in the least painful way possible?”.
Backups were fine for WP as I could “reload” the database options i.e. import all the content again. However, Piwigo was now so corrupted in the install that I had no confidence the backups wouldn’t produce the same result — I needed a brand-new fresh install. And reuploading of 7000 photos! With descriptions re-added for albums, etc. Now, I have a good setup for sorting pics at home, it was easy to reupload, and I could have done a DL and new UL of the existing structure, but I figured going nuclear on my install would be easier.
About this time though I realized that I no longer trusted the host. I had transcripts from the same guy, the one I complained about, where it said “A”, then “not A”, then “A”, then “not A”, then “A” and finally “A because you told me it was A”. The guy was a lying sack of excrement. And I still had no accountability response from GG to say how the guy was allowed to delete my complaints in the system, nor were my outstanding issues addressed.
It was time to break up
I started shopping for a new host. I talked to a few, explained some of my problems / frustrations, told them what I needed, and what I was willing to spend. I zeroed in on WebHostingCanada, partly as when I asked some technical questions, they jumped immediately to the problems it took me 3 months to solve on my own. The guy told me up front that one of their cheaper options wouldn’t be enough as the hosting industry didn’t always truly tell the right stats on certain things, essentially telling me that while it says “x”, it’s partly throttled (which isn’t advertised). The exact problem I seemed to be having with GG and which 3 months of testing had revealed but they wouldn’t admit. He even made me laugh at one point…I told him the specs for something technical in my current setup and he said, “Oh, that’s so sad” i.e. that the setup was so limited.
The transition didn’t go completely smoothly, but it did “go”. But that’s the basis for another post.
In terms of Greengeeks, I left my hosting account active for the remaining 2 years — I’m hosting another site through there, bare minimal load, and if their server has problems, it won’t affect me. At the end of the two years, I’ll transition to a site I already have.
While I’m now on my fourth hoster in 18 years, and my third one in 3, I’ve made some other config issues which should help. And I’m still paying less than I was previously, and getting more power. I can (hopefully) live with that.
When people cut the cord, most just look at TV, internet and home phone. Some add in cellular. For me, there was a fifth area — internet hosting of my websites. Yes, you read that correctly. Plural.
After a redesign about two years ago, I had PolyWogg.ca set up as my “personal” site. ThePolyBlog.ca was my more “professional” site, writing and musings about more formal topics. I also host AstroPontiac.ca for a board I sit on. And within polywogg.ca, I also had sub-sites for photos, calendars, to do lists, etc. Most of the sites were fully integrated with my photo site cross-linked to my personal and professional sites so that I can post my media there without duplicating it in WordPress. I’ve messed around with my site design going back to 1998, seventeen years of tweaking etc. The latest tweak was creating a new subsite for astrophotography blogging and pics.
I have had various hosts over the years. One big one I had was a small company in the Prairies that a friend was using. Small, decent support for tweaks, not a lot of bells and whistles but definitely personal support. I mentioned in an earlier post that I considered running my own server, partly because of the cheap hosting costs and partly to have my own private cloud available to me easily. In the end, I decided not to run my own server, but I was ambitious with my web design and the small company wasn’t going to meet my long-term storage needs. I went big.
Mostly the company here in Ottawa worked well for me for a long time. I was paying for a business account to give me more email addresses, more storage, etc. and a LOT of room to grow, but mostly to get the higher level of support if and when something went wrong. When they were bought by Netfirms in the U.S., and everything was merged, there were definite growing pains. It took a lot of work and some complete redesign in the end to get me where I wanted to be, with multiple subsites running and everything separate by function. It worked, but the overhead to keep it all up to date was killing me. Too many updates, plugins, etc. The separated design helped immensely though to figure out what one set of subdesigns would look like, and then the other. In the end, they were similar but just slightly different enough that previous single-site solutions had been confused. Then disaster struck. Kind of.
Netfirms had a DNS attack, and it took down a bunch of their servers. My site has some plugins that monitor the site being “up” or “down” through regular monitoring from the plugin’s websites, and my inbox filled up with notifications. Site A is down. Site B is down. Site C is down. Site D is down. Site A is up again. Site B is up again. Site A is down again, etc. 36 hours of notifications of sites being up and down. Then I got the message from Netfirms that was the all-clear signal. Everything had been resolved, all was working. Except my sites weren’t back up yet. They were still down. I contacted support who assured me everything was fixed; I assured them it wasn’t since I couldn’t log in to my site. They refused to help, basically arguing with me that the problem was fixed. When I finally convinced them, no, it was still not fixed, they said, “Oh, yeah, they’re still working on it.” Really? That’s what I’m getting for business level support? $180 a year to host all my sites, minimal load on their servers, and outright lies. “It’s fixed” and then “they’re working on it” when the first lie didn’t take. I escalated to Tier 2 and got the same run around. I waited a day, still not fixed, tried again, same run around. First they told me it was completely fixed, and then when I showed them my site was down, they said the technicians were still working on it. Really? Again with two completely opposite stories? Sorry, I called it quits right then and there. I needed a new webhost, and why not look for one a bit cheaper while I was at it.
There are lists out there of the top five webhosts and some of the deals are awesome. But I liked the personal side of the first host, not thrilled about being the little number in the big cog again. I canvassed some friends, and one of them suggested GreenGeeks.com. I fell in love with them just from the name. Ignore the fact that I called them GreenGreeks about a dozen times when I was accessing their site, I checked the specs and price. I basically need unlimited subdomains and full domain hosting. Not really, probably 10 would suffice, but more than most small companies offering 1-2. This often runs into a problem not with the subdomains but with the number of databases it will let you create — some stop at 5-8, and if you count 1 for PolyWogg, 1 for ThePolyBlog, 1 for astropontiac, 1 for a calendar, 3 for separate to do lists, 1 for a photo site, 1 for a cloud/file manager, etc., I’m at 9 and I’m not even maxing out my plans yet. I can get by without a lot of upload/download bandwidth for the sites (I don’t get a lot of traffic), but I like having lots of storage space to have an easy-to-access personal cloud. Mail servers are a must, but almost everyone has those. A few other bells and whistles, and I’d be good to go. What did I get?
GreenGeeks gives me unlimited storage. Sweet. Unlimited bandwidth. Double sweet. Three different choices for email server. I’m in love. Simple user interface for the control panel, personalized support that is decent, subdomains, addon domains, DNS management and registration (which I don’t need, but nice to know it’s there), some SEO and marketing tools (not as extensive as Netfirms, but decent), access to my logs (what? really? would have had to ask at some other sites), and perhaps most important, the Softaculous Apps Installer as their default install program (not the only way to do it, just the default). I’ve installed another app that does ToDo lists well, had to do it manually as not available in Softaculous, and it was a relative breeze. The help files could be a little more up to date, but I got it to work first time, just a little tweaking of the instructions.
So Netfirms was charging me $180 for the year. GreenGeeks? Also $180. For three years. $5 a month instead of $15. For better support, more options, and a personalized experience. Tailored more to my needs. An easy trigger to pull.
Now, don’t get me wrong. Moving my old site over has been a pain in the patootie. WordPress went relatively easily, but I ended up with a config issue the first time and even though they fixed it, I wasn’t 100% confident it would stay “patched” and not self-destruct later on. Kind of a background hack that solved the immediate problem, but I wasn’t sure it didn’t have others lurking in the shadows. So I blew everything off and reinstalled manually from scratch. Then imported as much as I could of the existing base.
There is one thing missing from GreenGeeks but it was missing from Netfirms too. None of the sites will let you stream video directly. They make you upload and store it at Youtube or its clones. Video just kills them and like most hosts, they just don’t support it without a lot more cash outlay. My videos are only personal videos and I was crossposting with DailyMotion. But the wife wasn’t happy with the ads that went with DailyMotion, so I’ve moved the video files over to Google Drive. Which necessitated re-adding the links to the photo site, but that wasn’t about cutting the cord, or the new host, just something that happened coincidentally at the same time as I made the other change. I only mention it as it is a factor for a lot of people when they make a change — the cost and structure change, but how complicated do you make it to take advantage of the window of opportunity to implement other changes at the same time? As an aside, I had to threaten Netfirms with legal action to get a partial refund of the remaining year’s worth of prepaid service (I basically asked for a refund because they had not provided the contracted service). It’s only $30 back, but better than nothing.
Overall, I love the new host. At a third of the price and better service, what’s not to love?
