Search results for

#Turbify

#1 Click this link to see Blog page --> 05/27/2020



#TechSupport #Yahoo #Blog
I can’t tell you how much dread I feel at this announcement. EVERY time these idiots improve, upgrade, etc. it turns into a major pain in the ass for me. I have never dealt with a more inept bunch of people and each time I wonder why I don’t move the Blog to a different web host. The last time they did this they turned off the backward-compatibility and I had to rewrite a lot of code. Hard telling what they will screw up this time.

This might also explain the sluggishness and down time of late.

I suspect they have a bunch of teenagers in India doing the transfer of data to this new system.

So if the Blog disappears (again) on or after June 9 you will know why.

Update: 05/27/23
Almost three years later and another selloff to a new outfit (#Turbify). This time they really hosed everything up and my site was FUBAR for weeks. Still not completely repaired.

MjL

#2 Click this link to see Blog page --> 04/25/2023

There were no real-time entries for today
because of the #Turbify FUBAR on 4/25.

MjL

#3 Click this link to see Blog page --> 04/26/2023

There were no real-time entries for today
because of the #Turbify FUBAR on 4/25.

MjL

#4 Click this link to see Blog page --> 04/27/2023

There were no real-time entries for today
because of the #Turbify FUBAR on 4/25.

MjL

#5 Click this link to see Blog page --> 04/28/2023

There were no real-time entries for today
because of the #Turbify FUBAR on 4/25.

MjL

#6 Click this link to see Blog page --> 04/29/2023

There were no real-time entries for today
because of the #Turbify FUBAR on 4/25.

MjL

#7 Click this link to see Blog page --> 04/30/2023

There were no real-time entries for today
because of the #Turbify FUBAR on 4/25.

MjL

#8 Click this link to see Blog page --> 05/01/2023

There were no real-time entries for today
because of the #Turbify FUBAR on 4/25.

MjL

#9 Click this link to see Blog page --> 05/02/2023

There were no real-time entries for today
because of the #Turbify FUBAR on 4/25.

MjL

#10 Click this link to see Blog page --> 05/04/2023

I’m slowly getting back into my daily habit and routine. At least the frustration with #Turbify and their collective stupidity is beginning to wear off. I still have a lot of editing to repair the chaos originally caused by the 4/19 “migration”. It is going to take some time but hopefully those idiots are done messing with us.

MjL

#11 Click this link to see Blog page --> 05/05/2023

#Turbify #GreatBlogCrash
When my Blog access was initially messed up I started keeping notes and I share a bit of that anger and angst here.

MjL

#12 Click this link to see Blog page --> 05/25/2023

#Turbify #GreatBlogCrash
I received an email from Turbify tech support regarding their recent FUBAR and fiasco. Keep in mind, that happened a month ago.

On Monday, May 22, 2023
Hello Michael,

Thank you for your patience with this process.

Good news, we have taken steps on our end that have resolved the issue and you should now be able to see your site loading as intended. The cause for your issue is the error logging on your site triggering resource abuse suspensions. Please review your site and the errors it is generating to resolve them as they may again trigger an abuse suspension if they are not addressed.

If you encounter further issues or have additional questions, please reply and let us know.

Thank you again for your patience with this process. We appreciate your business and look forward to assisting you in the future.

Regards,

Aaron
Turbify Support

My reply the same day (3 days ago)
Could you tell me please what file contains the error logs and what directory to look into? Thanks, Michael

No reply since then. This is very typical of these people. They screw things up for weeks at a time and then blame it on the customer with some scary sounding techno-babble. I hate this crap.

MjL

#13 Click this link to see Blog page --> 06/10/2023

#Turbify Here is an example of the typical interaction with tech support regarding the FUBAR of the Blog site. Constantly trying to blame their failures as my fault. And there are gaps of many days or even weeks before I get a nonsense reply.

This particular email chain started on May 1st.


On Monday, May 22, 2023 at 01:35:33 PM CDT,
Turbify Customer Experience <customer-experience@turbify.com>

Hello Michael,

Thank you for your patience with this process.

Good news, we have taken steps on our end that have resolved the issue and you should now be able to see your site loading as intended. The cause for your issue is the error logging on your site triggering resource abuse suspensions. Please review your site and the errors it is generating to resolve them as they may again trigger an abuse suspension if they are not addressed.

If you encounter further issues or have additional questions, please reply and let us know.

Thank you again for your patience with this process. We appreciate your business and look forward to assisting you in the future.

Regards,

Aaron
Turbify Support


From: Michael Legel [mjlegel@yahoo.com]
Sent: 5/23/2023 12:49 AM
To: customer-experience@turbify.com
Subject: Re: Error - Account Suspended on the Website
(Case: 01859907)

Could you tell me please what file contains the error logs and what directory to look into?
Thanks, Michael


On Thursday, June 8, 2023 at 04:04:24 PM CDT,
Turbify Customer Experience <customer-experience@turbify.com>

Hello Michael,

Thank you for your reply.

The error log can be found by searching for error_log in your file manager, once found select it and click the view option to see the errors.

If you encounter further issues or have additional questions, please reply and let us know.

Thank you again for your patience with this process. We appreciate your business and look forward to assisting you in the future.

Regards,

Aaron
Turbify Support


From: Michael Legel [mjlegel@yahoo.com]
Sent: 6/9/2023 12:53 AM
To: customer-experience@turbify.com
Subject: Re: Error - Account Suspended on the Website
(Case: 01859907)

I searched for error_log, none exist?

Michael


Turbify Customer Experience
<customer-experience@turbify.com>
To:mjlegel@yahoo.com
Fri, Jun 9 at 12:21 PM
Hello Michael,

Thank you for your checking on that.

In reviewing I have confirmed that no new errors are being recorded by our server which would cause the error_log file to generate. You may still want to review the coding of your site but at this point the issue appears to be fully resolved.

If you encounter further issues or have additional questions, please reply and let us know.

Thank you again for your patience with this process. We appreciate your business and look forward to assisting you in the future.

Regards,

Aaron
Turbify Support

MjL

#14 Click this link to see Blog page --> 07/05/2023

#Turbify I received an ominous email from the blog server tech support and immediately started a chat discussion with them very early this morning. Looks like the #Blog is in danger of disappearing again.

Chat Transcript

MjL

#15 Click this link to see Blog page --> 07/20/2023

Just spent an hour chatting with #Turbify tech support about my FTP not uploading files. No help whatsoever. It may be a while before I can upload files again. Sorry.

MjL

#16 Click this link to see Blog page --> 07/20/2023

My Blog FTP started working again some time this afternoon. I wouldn’t have known had I not checked it. No notice from #Turbify.

MjL

#17 Click this link to see Blog page --> 08/23/2023

I hope to revisit the tagged entries again. (As I did above.)
I was just getting into doing that when #Turbify torched the Blog site. I’m still rewriting code every day to recover from that fiasco but would like to get back to tagging comments.

MjL

#18 Click this link to see Blog page --> 09/09/2023

I’m getting emails from #Turbify threatening to suspend my account again for PHP script errors. Most of the errors have been caused by the last fiasco where they “upgraded” my account to the latest versions of software and they are not backward compatible. The Blog is older than some of these technicians.

I will be trying to resolve these issues but if the the #Blog disappears (again) at least you will know why.

MjL

#19 Click this link to see Blog page --> 09/10/2023

#Blog #Turbify
I will be spending a lot of time trying to tie up all these logged “errors” and the vast majority aren’t really errors. The code works, just not in the way it is expected to by the filter. They are wasting more energy looking for problems than the problems they think they are finding. An unreferenced index or empty variable causes no problem if never addressed by any other part of the code. Hopefully I can convince them to focus on more pressing issues if they exist. What bothers me the most is that most of these problems were caused weeks ago when THEY changed the system architecture and code versions.

MjL

#20 Click this link to see Blog page --> 09/12/2023

I got a rather lengthy reply from the #Turbify tech support guy and it seems I was right about the log files being more important than the errors themselves. At first I was a bit ticked about it but finally decided he was at least trying to help by explaining. We are all prisoners of the policies we have to live (or work) with.

Here is an excerpt of his explanation:
The core issue was the log size and
how that was impacting the servers,
not the specific errors themselves.

This is a server wide log, meaning it is used by all hosting
accounts on the server (not just yours). With how many
errors your account was dumping into it servers were running
out of disk space. The reason I honed in on the date and
time logs was each line was twice as long as the others,
meaning each took up twice as much disk space. Getting rid
of them, even though they were only warnings, had more
impact line per line than clearing out any other lines.

Seems to me it would be easier to reduce the length of the error message to save space, but I didn’t say anything because he probably can’t control that. Or get bigger hard drives, but I didn’t say that either. I will be spending more time going through code pages to remove the code causing these log errors. The sad thing is the “errors” probably don’t slow the system any more than the log file routine that acquires them. Rules are rules.

MjL

#21 Click this link to see Blog page --> 10/03/2023

I have been going through all my Blog pages, files and scripts for the past couple months and think I have gotten most of them repaired from the #GreatBlogCrash #Turbify caused. Hopefully ALL is working properly again and if not; Please Tell Me. I found tons of pages from the years 2006 thru 2011 that haven’t been working while I was at it.

MjL

#22 Click this link to see Blog page --> 04/20/2024

It was a year ago today for the Great #Blog Disaster when #Turbify updated / upgraded a complete FUBAR of the site. I am still tripping over portions of the Blog that don’t work right.

MjL

#23 Click this link to see Blog page --> 08/06/2024

I’ve been fooling around with this #Blog for eighteen years!
Doesn’t seem so long if you say it fast.

On this anniversary the bill from #Turbify almost doubled. I called up the billing dept. yesterday and was told it was because of all the “improvements” that were made. That would be when they destroyed the Blog for almost a month and I’m still finding things to fix because of it.

Talk about adding insult to injury. I managed to change plans to something less expensive but still too costly. The price of my online addiction.

MjL

#24 Click this link to see Blog page --> 09/19/2025

I see the Blog is back up. It was dead at 3 a.m. I couldn’t connect to anything. I called #Turbify and spoke with a young lady from a foreign land and finally got a “ticket”. It seems to work for now.

MjL

#25 Click this link to see Blog page --> 09/20/2025

I went to bed at around 10:15 last night after having my routine a bit messed up by #Turbify. I was up again a little after 2 a.m. to find the Blog dead again. I called tech support again. This time I went about my usual routine and discovered the Blog was working a couple hours later. I have no idea what is going on with these people.

MjL

#26 Click this link to see Blog page --> 11/11/2025

I had a moment of panic yesterday when the “too many connections” glitch struck again for about an hour. I emailed my concern to #Turbify tech support, but I don’t what, if anything, they had to do with it.

MjL

#27 Click this link to see Blog page --> 03/08/2026

The “Too Many Connections” errors struck again yesterday. I finally spent some time chatting with a #Turbify tech support person. (At least I think it was a person.) I prefer the text chat because I don’t have to deal with the foreign accent and my deafness. I am now the proud owner of another Case Number. Last November it took over a week to get this same problem resolved.

MjL

#28 Click this link to see Blog page --> 03/12/2026

#Turbify closed out my “too many connections” trouble ticket.
Guess what? Their errors persist.

MjL