Phone messages full

[sjlocke]

I really, would like my server space to be available (ie online) when I need it. This morning, when trying to get a client to download some stuff, the site was down.

Anyhoo, I went to call the number on the front page of page-zone, and the phone server said the mailbox was full. I can only assume there is no one on live support, and there should be. Or there should be an updated status on the phone system, with a date of message. Or something! Email status reports. Something to let us know something is going on and you are doing something about it.

[sgibons]

I'll stick my nose in here... I have a $25 reseller account and I host a bunch of domains mainly for friends and colleagues. I've been with page-zone for at least 4 years. Though there are occasional problems, the service has been generally good. I keep an uptime monitor going 24/7 on a spare box in my home and there is rarely any downtime reported.

When problems do hit, like now, they look catastrophic, but the small staff that Jim Snape heads up gets stuff fixed reasonably, considering the price.

The main problem they have is in communication, and there are a few posts here that talk about that so I won't, except to say: don't bother leaving a voicemail. Try calling again, or find Jim's contact info and write to him.

Or, file a support ticket with all the pertinent info and bounce it frequently,

Also, there are people here on the forum who can be helpful, if you include the url you're having a problem with.

Really, for the price you have to be realistic, and there are long stretches of time when I don't even think about page-zone, of Jim, Penny, Lindsay or Butch.

steve

I totally understand the frustration, having myself relied entirely on websites for my mutton and mammon in the past. So while I can't do a perfect job minute by minute, let me assure you of a couple little things that, if you believe it, might help when you're under this kind of pressure again.

There is ALWAYS someone working on tickets at page-zone, phone or not. 24/7 (with maybe a brief lapse over the holidays, but Jim still has that cell, so he works every day of the year). Some of us aren't as quick at solving big problems as others--meaning it takes me an hour to fix a lot of things Jim or Lindsay can fix in ten minutes, though I do have my strong points as well--but the problems are being addressed.

We are also constantly doing little general fixes to make things work better on this new hardware--everything isn't installed yet, cPanel isn't too handy for that because transferring the previously tweaked settings would break more things than just starting fresh has broken. For example, something freaked out on 134 and in the process port 3306 got closed. Nobody manually closed it. I suspect cPanel did it just to keep the support desk full of fresk tickets. But that took me...well, a long time to realize what it was--if you're on 134 and your board or something wasn't working, that's probably why, and I finally fixed it. Resolving half a dozen tickets that I still haven't answered.

And I think Jim should wear an aluminum hat to prevent cancer from the cell phone growing out of his head. Aside from his brief excursions to the store, the hospital, and the data center, I could barely ask him a question because he was helping someone on the phone all day today.

So at least you know there's activity going on behind the apparent silence.

[Edit: and yes--if you want to make sure we get to your problem ASAP, file ONE ticket on it, and bounce it--not every ten minutes, but if we haven't gotten to it in a day or so, please speak up in response to the same ticket. Much more effective to get our attention that way, we try, but there's a lot of work to do, and multiple tickets on one issue is just asking for problems in many ways.

Second edit--If something starts to work, tell us that in the ticket, too--so we can close it! We're constantly fixing things that some users will never see until something they want works, which they'll never know wouldn't have worked ten minutes earlier.]

[SpringerPal]

Originally Posted by Butch Miller

I totally understand the frustration, having myself relied entirely on websites for my mutton and mammon in the past. So while I can't do a perfect job minute by minute, let me assure you of a couple little things that, if you believe it, might help when you're under this kind of pressure again.

We are also constantly doing little general fixes to make things work better on this new hardware--everything isn't installed yet, cPanel isn't too handy for that because transferring the previously tweaked settings would break more things than just starting fresh has broken. For example, something freaked out on 134 and in the process port 3306 got closed. Nobody manually closed it. I suspect cPanel did it just to keep the support desk full of fresk tickets. But that took me...well, a long time to realize what it was--if you're on 134 and your board or something wasn't working, that's probably why, and I finally fixed it. Resolving half a dozen tickets that I still haven't answered.

Hi Butch!

Speaking of "frustration", what's the story on Port 3306? We've relied on this in the past for access via MySQL Frontend but Lindsey sent us back a ticket reply that it was "closed for security reasons"?? Is it open or closed?

You seem to indicate that it's OPEN!?!?

TIA for your attention to this inquiry.

Regards,
SpringerPal

Yes I opened 3306 for the moment on a couple servers as a stopgap fix, the problem being that in these cases it may be serving to keep sites working by accessing the old server the sites had been on. Which isn't any good at all, if that's the case like I think it is, because sooner or later those boards et al are going to have to be run locally.

It's kind of a confusing thing at the moment, and requires specific attention to address fully, which we sort of have to delay to address the other big issues. If I could've figured it out thoroughly at the time I would have fixed it right, because I hate to work on something and not get it completely finished. But as it is I just wanted to get the sites working that weren't and then of course there were other huge things going on.