amuck-landowner

Choopa sends out Vultr to drown in the DigitalOcean

tchen

tchen

New Member
I hope they fix the security issues and the capacity planning bit.  Having "sold out" locations defeats the single purpose I have for instant activation APIs.
 
MannDude

MannDude

Just a dude
vpsBoard Founder
Moderator
wcypierre said:
Pardon me, heh. Skimped through the pictures when I was reading it
Click to expand...
No worries, I do it all the time too ;)

Pretty scary stuff, all things considered. Seems like they're likely using the same billing database as their gameservers.com company, too.
 
Zigara

Zigara

New Member
I woke up to see the VM removed, and my security issue ticket closed without a response.

I don't think I can business with a company that just sweeps it under the rug.
 
MannDude

MannDude

Just a dude
vpsBoard Founder
Moderator
Comically enough, though, this thread inspired me to get another DigitalOcean box. My other 3 are operating just splendidly.

Though their Singapore location has terrible network speeds. I was getting about 0.3/Mbps down. Luckily, I have no use for a Singapore VPS so rebuilt that bad boy back in the states.
 
D

DaveA

New Member
Verified Provider
Zigara said:
I woke up to see the VM removed, and my security issue ticket closed without a response.

I don't think I can business with a company that just sweeps it under the rug.
Click to expand...
We didn't sweep it under the rug, there was an issue with a common key randomly generated that matched that of another causing some information to be erroneously displayed in your panel.   Our developers identified the key collision and corrected the situation.    We appreciate you bringing this to our attention.   This was a soft launch on Friday to identify some bugs before our full launch and it spread quite fast.   We are working feverishly to make this a great product.   We appreciate the original posters comments.
 
Zigara

Zigara

New Member
DaveA said:
We didn't sweep it under the rug, there was an issue with a common key randomly generated that matched that of another causing some information to be erroneously displayed in your panel.   Our developers identified the key collision and corrected the situation.    We appreciate you bringing this to our attention.   This was a soft launch on Friday to identify some bugs before our full launch and it spread quite fast.   We are working feverishly to make this a great product.   We appreciate the original posters comments.
Click to expand...
That sounds very poorly designed. It would help to reply to the tickets (even with a canned response) explaining the issue rather than just closing the ticket.

It does not sit well with me any many others. I should not have to read vpsBoard to find this out.
 
Last edited by a moderator:
I

imperio

New Member
DaveA said:
We didn't sweep it under the rug, there was an issue with a common key randomly generated that matched that of another causing some information to be erroneously displayed in your panel.   Our developers identified the key collision and corrected the situation.    We appreciate you bringing this to our attention.   This was a soft launch on Friday to identify some bugs before our full launch and it spread quite fast.   We are working feverishly to make this a great product.   We appreciate the original posters comments.
Click to expand...
Key collusion sounds like clusterfuck :D

Tell your developers to seperate databases/keys etc for different type of your business.I have a server with constant and i do not want my personal information leaked due to your software developer's laziness.
 
Kalam

Kalam

New Member
>tracert wa-us-ping.vultr.com

Tracing route to wa-us-ping.vultr.com [108.61.233.46]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  TOMATOUSB [192.168.1.1]
  2    10 ms     8 ms     6 ms  96.120.100.1
  3     7 ms     8 ms     8 ms  te-0-0-0-15-ur06.tacoma.wa.seattle.comcast.net [68.85.241.45]
  4    12 ms    11 ms    18 ms  ae-28-0-ar03.seattle.wa.seattle.comcast.net [69.139.164.205]
  5    11 ms    15 ms    13 ms  he-1-5-0-0-10-cr01.seattle.wa.ibone.comcast.net [68.86.94.57]
  6    13 ms    12 ms    14 ms  4.68.63.65
  7    12 ms    12 ms    12 ms  ae-2-52.edge2.Seattle1.Level3.net [4.69.147.168]
  8    14 ms    16 ms    16 ms  CHOOPA-LLC.edge2.Seattle1.Level3.net [4.53.158.66]
  9    20 ms    21 ms    20 ms  108.61.233.46.choopa.net [108.61.233.46]

Trace complete.

Not bad, slightly better than RamNode's Seattle location.

>tracert 23.226.229.4

Tracing route to test.sea.ramnode.com [23.226.229.4]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  TOMATOUSB [192.168.1.1]
  2     9 ms     8 ms     7 ms  96.120.100.1
  3     8 ms     9 ms     9 ms  te-0-0-0-15-ur06.tacoma.wa.seattle.comcast.net [68.85.241.45]
  4    10 ms    74 ms    10 ms  ae-28-0-ar03.seattle.wa.seattle.comcast.net [69.139.164.205]
  5    13 ms    14 ms    12 ms  he-1-6-0-0-11-cr01.seattle.wa.ibone.comcast.net [68.86.92.33]
  6    29 ms    30 ms    30 ms  68.86.85.198
  7    32 ms    34 ms    34 ms  pos-0-2-0-0-pe01.11greatoaks.ca.ibone.comcast.net [68.86.87.10]
  8    37 ms    42 ms    39 ms  xe-9-3-0.sjc10.ip4.tinet.net [213.200.80.165]
  9    56 ms    54 ms    57 ms  xe-11-1-2.sea23.ip4.tinet.net [141.136.111.205]
 10    38 ms    34 ms    37 ms  ramnode-gw.ip4.tinet.net [173.241.128.122]
 11     *        *        *     Request timed out.
 12    31 ms    30 ms    33 ms  test.sea.ramnode.com [23.226.229.4]

Trace complete.
 
Last edited by a moderator:
HalfEatenPie

HalfEatenPie

The Irrational One
Retired Staff
So my issue was finally resolved after a bit of an e-mail exchange with one of their support tech (Mike I believe it was).  But I'm still pretty weary of putting money into it.  
 
Zigara

Zigara

New Member
The problem is they really did copy DO's web design. It's basically identical with a bit of changes.

If it had come with a unique design and no security issues, I believe it would have had much more luck and not be called a 'DO clone'.
 
J

joepie91

New Member
DaveA said:
We didn't sweep it under the rug, there was an issue with a common key randomly generated that matched that of another causing some information to be erroneously displayed in your panel.   Our developers identified the key collision and corrected the situation.    We appreciate you bringing this to our attention.   This was a soft launch on Friday to identify some bugs before our full launch and it spread quite fast.   We are working feverishly to make this a great product.   We appreciate the original posters comments.
Click to expand...
So either A. use incremented IDs rather than generated IDs or B. make your generated IDs have a sufficiently big keyspace - a UUID should suffice.
 
lbft

lbft

New Member
According to their support, Sydney and Tokyo won't be available until mid March and other OS options won't be available for at least 10 days.

That on top of the atrocious security fuckup makes me wish I hadn't put money into this thing. I expected better from Choopa - it seems clear that this wasn't ready for launch.
 
Last edited by a moderator:
Setsura

Setsura

New Member
MannDude said:
Read the thread ;)

Namely this post:

And this one:

No thanks!
Click to expand...
I actually saw the same thing as above when I signed up this morning, had someone's mumble(I think) server and CC in my billing. Didn't really try to use the card, but it makes me wonder what if it did work? Not sure how I feel about giving money to them now.
 
You must log in or register to reply here.
Top
amuck-landowner