Comments on: Comparison of VPS Providers http://tipsfor.us/2011/04/18/comparison-of-vps-providers/ Tech Tips, Reviews, Tutorials, Occasional Rants Sat, 31 Aug 2013 15:50:35 +0000 hourly 1 https://wordpress.org/?v=4.8 By: Why GoDaddy is a Horrible Host | TipsFor.us http://tipsfor.us/2011/04/18/comparison-of-vps-providers/#comment-13475 Sat, 24 Dec 2011 19:18:41 +0000 http://tipsfor.us/?p=2631#comment-13475 […] may remember my earlier comparison/rant of VPS Hosting Providers. GoDaddy was on that list of hosts to avoid, but recent events have loaded my arsenal with […]

]]>
By: Amit Kumar http://tipsfor.us/2011/04/18/comparison-of-vps-providers/#comment-12917 Tue, 06 Dec 2011 14:29:13 +0000 http://tipsfor.us/?p=2631#comment-12917 Hi Everett ,
Really very very useful info …
thanks a lot….:)

]]>
By: Everett - TipsFor.us http://tipsfor.us/2011/04/18/comparison-of-vps-providers/#comment-8525 Tue, 19 Apr 2011 12:02:21 +0000 http://tipsfor.us/?p=2631#comment-8525 Terry, I appreciate that you took the time to respond to this article, but holy !#^%@$% smokes, the time to make things right is LONG gone. VPS.net HAD that chance and blew it. I carry a big stick, and when it finally comes out, mother-f’ers get WHACKED. I waited, I pleaded, I damn near *begged* for a response during the course of the incident outlined above, and I basically got NOTHING. *Nobody* over there shot me straight. This flaming was not out of the blue: I had the common decency to offer your company the chance to make things right back then by filing several relevant tickets (which were largely ignored) and then informing VPS.net of my intention to publicize my experience, and unlike VPS.net, I actually do follow-through and do what I say I will do.

Throughout this experience it was like the left hand didn’t know what the right hand was doing: it was clear from Nick Nelson’s responses to me that he had no recollection of the previous discussions that he had participated in, nor was there any acknowledgement or appreciation on his part of the suffering I went through. VPS.net did refund the fees for the snapshot “service”, but nobody at VPS.net had the balls to admit to having screwed up save for one tech, and only then after I basically had him at gunpoint. It was just piss poor, so I refuse to waste any more time with VPS.net. I gave you my *full attention and time* for a sleepless period of about 4 days and all I got was a bunch of waffling BS responses, so no thank you, my time is more valuable than to spend it writing pointless emails so you can feel better about how your company operates.

If you want to know how to improve VPS.net, here’s my opinion of where to start:

1. Have integrity. Not easy for a corporation, but if you say you’ll do something, then *do it*. Not because your lawyers said you had a binding agreement, not because you fear getting flamed if you don’t. Do it *because you said you would.* That’s called keeping your word.

2. Be honest, admit failure. When you screw something up (such as destroying a customer’s server), be up front and honest about the scope of the damage. It’s not flattering to paint yourself in a negative light, but it would have spared you this negative review and it would have saved me many hours of stress. Even your comment was a bit off-base: basically after the hell I went through, the only comment from VPS.net that I would plausibly tolerate would have been something along the lines of “You’re absolutely right. We screwed that up BIG TIME. And although we cannot really make amends for this, we have done everything in our power to make sure it never happens again.”

3. Don’t offer services you can’t guarantee (this gets back to #1). If one of my client’s sites gets hacked or goes down and they are relying on me to provide backups, do you know how ridiculous it would be if I dug up some legalese fine print that recused me of any liability? It’s just whiney corporate BS, and I have no respect for it.

]]>
By: Terry Myers http://tipsfor.us/2011/04/18/comparison-of-vps-providers/#comment-8522 Mon, 18 Apr 2011 22:55:08 +0000 http://tipsfor.us/?p=2631#comment-8522 Hi Everett,

Thank you for the candid review. I’m extremely disappointed to hear about your experiences using us at VPS.NET. Could you please contact me at terry(at)vps.net? I would love to have the opportunity to review your circumstances and see if we might be able to make things right. If not, we can at least make sure future customers don’t have the same frustrating experience.

Thanks,

Terry Myers

]]>
By: (mt) Matt http://tipsfor.us/2011/04/18/comparison-of-vps-providers/#comment-8520 Mon, 18 Apr 2011 19:25:55 +0000 http://tipsfor.us/?p=2631#comment-8520 Sorry to hear about your bad experience. Even though our (gs) has had its share of issues in the past, we are working on constantly improving that product for our customers. Recently, it seems that our maintenance has provided higher stability and performance for our customers on the (gs). Finally, our shared service and VPS are two completely separate products, therefore, it would be a bit unfair to compare them.

But the focus of the article is about our VPS, so it seems like your main issues with our (dv) fell with command line issues and Plesk. To correct one problem that you were having, SSH only kicks you out of the session after 5 minutes of inactivity. If you were having problems connecting and navigating, we do provide knowledge base articles on working with SSH to make your life easier. Also, permissions for access to particular directories can all be managed through Plesk.

http://wiki.mediatemple.net/w/%28dv%29:Enable_SSH_for_FTP_user

http://kb.mediatemple.net/questions/16/Connecting+via+SSH+to+your+server#dv

If Plesk is the major problem, it would probably be best to look at something like our (ve). With the (ve), you are getting a blank box to install whatever you choose. We recommend that customers that purchase the (ve) have a solid knowledge of Linux before using it, as we don’t provide any support for it.

I hope this helped clear up some of the issues you were having. Please let us know if you have any other suggestions with anything we can improve.

]]>