Scam report against | 1862877-memester101 | $330

[AntiKeys]

Username: memester101
Profile Link: https://www.nulled.t...877-memester101
Short Description Of Product/Service: Developing a bot
Thread of sales: none
Screenshots of conversation: https://imgur.com/a/8x6SGtI
Amount scammed: $250 + $80

Proof of payment (IMPORTANT, PLEASE POST): https://imgur.com/a/8x6SGtI

Additional Information: 

 

Bought a bot from a while ago, it's still working perfectly fine except his security. I am not able to access the bot anymore as his security is down and I can't do anything now

 

I don't want a refund, I just want a fix, he's reading my messages but no reply. 

I am able to host something if he doesn't have a server, just let me know

[Memer]

blame rdp.sh , lucas was on the problematic server, it got resetted and lost all my data (including the auth)

[AntiKeys]

blame rdp.sh , lucas was on the problematic server, it got resetted and lost all my data (including the auth)

Is there any way you can get this up again?

[RDPsh]

blame rdp.sh , lucas was on the problematic server, it got resetted and lost all my data (including the auth)

 

Hello,

blame us for what exactly? All of our servers are perfectly up and running, if you face issues you must contact us via email, otherwise how can we be able to know about a problem?

 

Best Regards,

RDP.sh Support

[Memer]

Hello,

blame us for what exactly? All of our servers are perfectly up and running, if you face issues you must contact us via email, otherwise how can we be able to know about a problem?

 

Best Regards,

RDP.sh Support

server was not letting me login, restarts frequently.
I had multiple issues with your servers, after I moved to another provider all is gucci. I have mailed you multiple times in the past, after you said "Oh you restarted it too many times, if you restart again we'll block you" I decided just to move away and to keep this server for the auth, but i failed.

[RDPsh]

server was not letting me login, restarts frequently.
I had multiple issues with your servers, after I moved to another provider all is gucci. I have mailed you multiple times in the past, after you said "Oh you restarted it too many times, if you restart again we'll block you" I decided just to move away and to keep this server for the auth, but i failed.

Hello,
you were spamming the restart button after knowing that it wasn’t going to solve the problem, we’ve kindly asked you to stop doing that, that was all.

We’ve solved your problem anyway, and we were always available to help you.

Best Regards,
RDP.sh Support

[Memer]

well, our definition of kindly is a different then, you said youll terminate my account if I continue to press restart, the servers were constantly down, had to restart them every few days and hope theyll be up, your response was "it isnt possible" and to give me 3 extra days, I decided to move to another service, but sadly you auth server died. 

[RDPsh]

well, our definition of kindly is a different then, you said youll terminate my account if I continue to press restart, the servers were constantly down, had to restart them every few days and hope theyll be up, your response was "it isnt possible" and to give me 3 extra days, I decided to move to another service, but sadly you auth server died. 

Hello,

servers aren't constantly down, you were doing something on your specific server that was causing the problem, either that and/or you weren't keeping your server up to date, which is mandatory for Windows Server 2019, otherwise you face stability issues that don't depend on us at all.

 

We have over 1300 running instances at the moment, nobody is facing issues. We are always here available to help and we want to deeply check your case because we don't want to leave any customer unsatisfied.

Please send us another email with your details and we will check.

 

"your auth server" that isn't related to RDP.sh at all, so we cannot be blamed for that.

 

Best Regards,

RDP.sh Support

[Lucas]

Closed. Regardless of that, I will keep insisting on memester to search for the backup. Considering it's been over 6 months since the purchase of the tool and that the tool had a specific warranty (of a week, if I recall correctly) there's not much I can do.