Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop

Categories

In this Discussion

Home › Providers
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Warning: databreach recycled server(s) from @VPSSLIM

13»

Comments

  • barbarosbarbaros Member

    @VPSSLIM said:
    Additionally, it’s important to mention that you purchased a very low-cost deal (128GB RAM with an E5 CPU for €24 per month). Despite that, we went the extra mile and provided you with an additional free month due to earlier issues with your other server. This is precisely why we would have appreciated if you had reached out to us first through a support ticket instead of making this public post without giving us the opportunity to assist you.

    Which package should I buy so I can access data of your previous customers, as you said €24 per month is too cheap.

    Literally, you fucked this up, and have balls to say you offered them a courtesy.

    Thanked by 1Mumbly
  • VPSSLIMVPSSLIM Patron Provider, Veteran

    @alincupunct said:

    @PinHead said: After a downtime of almost 1.5 month(!!!) last thursday they managed to provide a replacementserver with username and password.

    @VPSSLIM An EXTRA month over the 1 and a half months of downtime?

    On top of the downtime compensation of course. But that's not the point now. The point is there went something terribly wrong in this case causing the server not to wipe. It should have so we investigated all other configs and it was with just this server. We are taking measures in place as well to manually monitor all dedicated server setups from now as well if the installs and wipes (terminations) are running correctly to rule out any such event again.

  • cmeerwcmeerw Member

    @VPSSLIM said: You did not open a ticket at any point about this issue, nor did you reply to our last ticket where we provided explanations and requested feedback. If you had reached out, we would have resolved this for you right away.

    How do you resolve a data leak via a ticket? The data has already leaked.

    And have you informed the customer whose data you have leaked?

  • alincupunctalincupunct Member

    @VPSSLIM said:

    @alincupunct said:

    @PinHead said: After a downtime of almost 1.5 month(!!!) last thursday they managed to provide a replacementserver with username and password.

    @VPSSLIM An EXTRA month over the 1 and a half months of downtime?

    On top of the downtime compensation of course. But that's not the point now. The point is there went something terribly wrong in this case causing the server not to wipe. It should have so we investigated all other configs and it was with just this server. We are taking measures in place as well to manually monitor all dedicated server setups from now as well if the installs and wipes (terminations) are running correctly to rule out any such event again.

    Least you can do. Even if the service was 5$, that downtime is unacceptable.

  • matey0matey0 Member

    @VPSSLIM said: This is precisely why we would have appreciated if you had reached out to us first through a support ticket instead of making this public post without giving us the opportunity to assist you.

    I think the user is perfectly capable of wiping the disks and re-installing the system. This isn't something that required assistance but an explanation, which you've now given.

    I get that you would've liked this to stay in a support ticket and not become public drama, but issues like this should be publicized.

    Honestly no idea what the BIOS has to do with this in your setup, but IMO something like this should never happen and should be automatically verified, raising an error on failure.

    Thanked by 1borkedascii
  • VPSSLIMVPSSLIM Patron Provider, Veteran

    @matey0 said:

    @VPSSLIM said: This is precisely why we would have appreciated if you had reached out to us first through a support ticket instead of making this public post without giving us the opportunity to assist you.

    I think the user is perfectly capable of wiping the disks and re-installing the system. This isn't something that required assistance but an explanation, which you've now given.

    I get that you would've liked this to stay in a support ticket and not become public drama, but issues like this should be publicized.

    Honestly no idea what the BIOS has to do with this in your setup, but IMO something like this should never happen and should be automatically verified, raising an error on failure.

    Unfortunately mistakes happen. It matters that we learn from them. I'm not happy about this either. Hence we took further monitoring measures in the future to double check.

  • VPSSLIMVPSSLIM Patron Provider, Veteran

    @cmeerw said:

    @VPSSLIM said: You did not open a ticket at any point about this issue, nor did you reply to our last ticket where we provided explanations and requested feedback. If you had reached out, we would have resolved this for you right away.

    How do you resolve a data leak via a ticket? The data has already leaked.

    And have you informed the customer whose data you have leaked?

    I mean contact us via ticket and not make a post on a forum and not say anything to us. OP made a post but did not warn us via a ticket so we had to find out via LET. He's of course free to share his experience.

    Old user has of course been sent a warning. Though we have no believe OP has bad intentions and the data has been wiped on the server.

  • deer76deer76 Member

    @itsTomHarper said:
    Looks like the previous customer didn't care about their data security. Usually before I cancel a server I reboot to rescue mode and shred all the drives with multiple passes to ensure all my sensitive data is gone, be it a VM or a dedi.

    @itsTomHarper said:
    Looks like the previous customer didn't care about their data security. Usually before I cancel a server I reboot to rescue mode and shred all the drives with multiple passes to ensure all my sensitive data is gone, be it a VM or a dedi.

    You don't need to run shred on SAN disks, and not even on modern hdd/ssd, it's security theatre. Just wipe once with any byte you like.

    Thanked by 2tentor forest
  • matey0matey0 Member

    @VPSSLIM said:

    @matey0 said:

    @VPSSLIM said: This is precisely why we would have appreciated if you had reached out to us first through a support ticket instead of making this public post without giving us the opportunity to assist you.

    I think the user is perfectly capable of wiping the disks and re-installing the system. This isn't something that required assistance but an explanation, which you've now given.

    I get that you would've liked this to stay in a support ticket and not become public drama, but issues like this should be publicized.

    Honestly no idea what the BIOS has to do with this in your setup, but IMO something like this should never happen and should be automatically verified, raising an error on failure.

    Unfortunately mistakes happen. It matters that we learn from them. I'm not happy about this either. Hence we took further monitoring measures in the future to double check.

    If your customer was some big company and you were a big provider like AWS this would've been a billion dollar lawsuit.

    Good that you're taking measures.

  • cosmicmythscosmicmyths Member

    @VPSSLIM I would imagine the OP thought you may respond quicker to a forum post as your replies to tickets are either slow or non-existent from the many experiences written and experienced by users of this community.

    Thanked by 1PinHead
  • ascicodeascicode Member

    @matey0 said:

    @VPSSLIM said:

    @matey0 said:

    @VPSSLIM said: This is precisely why we would have appreciated if you had reached out to us first through a support ticket instead of making this public post without giving us the opportunity to assist you.

    I think the user is perfectly capable of wiping the disks and re-installing the system. This isn't something that required assistance but an explanation, which you've now given.

    I get that you would've liked this to stay in a support ticket and not become public drama, but issues like this should be publicized.

    Honestly no idea what the BIOS has to do with this in your setup, but IMO something like this should never happen and should be automatically verified, raising an error on failure.

    Unfortunately mistakes happen. It matters that we learn from them. I'm not happy about this either. Hence we took further monitoring measures in the future to double check.

    If your customer was some big company and you were a big provider like AWS this would've been a billion dollar lawsuit.

    Good that you're taking measures.

    A big company wouldnt forget to pay.
    I think someone just let it go and thats why it wasnt paid for the next period of time.

  • matey0matey0 Member

    @ascicode said:

    @matey0 said:

    @VPSSLIM said:

    @matey0 said:

    @VPSSLIM said: This is precisely why we would have appreciated if you had reached out to us first through a support ticket instead of making this public post without giving us the opportunity to assist you.

    I think the user is perfectly capable of wiping the disks and re-installing the system. This isn't something that required assistance but an explanation, which you've now given.

    I get that you would've liked this to stay in a support ticket and not become public drama, but issues like this should be publicized.

    Honestly no idea what the BIOS has to do with this in your setup, but IMO something like this should never happen and should be automatically verified, raising an error on failure.

    Unfortunately mistakes happen. It matters that we learn from them. I'm not happy about this either. Hence we took further monitoring measures in the future to double check.

    If your customer was some big company and you were a big provider like AWS this would've been a billion dollar lawsuit.

    Good that you're taking measures.

    A big company wouldnt forget to pay.
    I think someone just let it go and thats why it wasnt paid for the next period of time.

    Yeah but it seems like this could've happened regardless of why the server changed hands.

Sign In or Register to comment.