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.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
DeluxHost.net | High Performance | [PRE-ORDER] NEW VPS Deals | START 7€ ANNUAL | NED
This discussion has been closed.

Comments
You are beyond help.
If your response is just an image and "You are beyond help," then it’s clear you're not here for a productive discussion—you just want to argue.
We’ve explained our reasoning, acknowledged concerns, and even said we’re open to improving our processes. If you have actual constructive feedback, we’re happy to listen. But if your only goal is to throw insults and dismiss everything we say, then there’s nothing more to discuss.
At the end of the day, our priority is ensuring service uptime for our customers—not entertaining pointless back-and-forth arguments.
@DeluxHost if your purpose was to set-up my network, why doesn't it even work?


Seeing the kinds of arguments he makes, didn't expect any less
If the issue persist please open a ticket and we are happy to help you with the problem!
Anyway your screenshot is confirming what we just told until now, logs talk...
A simple "history" because I'm lazy and won't go around finding what files you changed means nothing. Do I have to explain you what .bash_history is?
I'm literally going to reinstall this VM, there's no point in me to dig further. Thankfully, I didn't even store anything sensitive in it.
btw

And you want still discuss on it? Seriously? 😂😂😂
Don't you realize that doing what you did is literally against the law?
Do I need to explain you what the GDPR (and many more) is?
You can do whatever you want as we are answering to you for 1 hour and an half without any problem.
If you want also, please, go ahead and make some further check to show here what other files was edited.
This is becoming a surreal situation really 😂😂
We have already answered before in other comments, i'm not gonna reapeat more.
I wasn't even using their templates, since Virtualizor's ones are (IMO) trash
But qemu-guest-agent was (somehow) installed in the system, idk how it got there tbh
I genuinely love when clueless, garbage and untrustworthy providers take 0 responsability for what they do. Makes for very very fun reading too.
It’s disappointing that you feel that way. We’ve been responsive and transparent, providing clear explanations throughout. If there’s a specific concern you have, we’re more than happy to address it directly, but throwing out insults doesn’t move the conversation forward. We’re committed to providing good service and resolving issues as quickly as possible, and we always encourage constructive feedback. If you need any help, feel free to open a ticket
Let me respond to this one with a few quotes:
So, I have an unmanaged service, right? Why the f* do I need to explicitly request to handle things on my own?
You did adjust it, that's for sure, but you didn't even input the right network adapter, and so, was in an (even more) broken state than before
Also, if you didn't know, VNC doesn't run at the VM level, but in your host node (unless you proxy it), it's literally a display adapter that's connected to the VM and (in your case) not even in the same subnet as my VM.

You still haven't disabled VNC since you made those changes btw
Let me be clear, I don't see bad intentions from you, but you surely lost my trust and many of people's because of this action. NO ONE asked u to login into my server, and there's a reason as to why some providers ask you this information before accessing your server if you need help in a ticket.

You laughing over all of this truly shows how you are.
How does this relate to the situation of my VPS in your location in Amsterdam today?
Don't forget that providing hosting or space is still a matter of trust. You simply do not enter a customer machine or webspace without his/her consent. Also restarting a VPS of a customer several times without notifying him/her is - in my opinion - off limits [And that has been done also. "Have you turned it off and on again" as a solution comes to my mind as clear sign of uncapable technicians]
@DeluxHost Respectfully, I see where he is coming from.
You don't get the point - so I agree with the statement "you are beyond help".
If I come to your house (of which I am the landlord) with a gun, have a dummy key that I use to gain access, walk around your house - I don't take anything, but just walk around - and I go out again. You look at that as "I don't see that there is a problem"?
Don't know about your country, but I'm living in the Netherlands and there it's considered a problem and I'd be in serious trouble.
@DeluxHost can i get a refund since i have privacy concerns hosting any kind of data with your company.
Pop corn time 🍿
Qemu-guest-agent self installs on debian if it detects the hint provided by the host.
Could you clarify which Debian version? That's something I'm totally unheard of.
@DeluxHost as one of your customers I'd ask you take the concerns being raised here seriously.
I don't doubt that you've only ever accessed VPSs with good intentions, (i.e. to fix specific issues), but you really shouldn't do that at all without getting the customer's consent first.
As a European company, providing services to European customers from European locations, you need to be really careful about GDPR. A single complaint to the relevant data protection authority would cause you a massive headache, whether it was upheld or not, because you really don't want to get audited and possibly fined.
Generally, if you need to perform actions on customer instances then it should be done in the form of a script that is run remotely rather than hands-on-keyboard, unless the customer has explicitly requested it, (and even then you're providing an unmanaged service so should probably charge them extra for the remote hands anyway).
So please take this advice in the spirit it's intended. Just admit you made a mistake here and establish a policy that your staff won't access customer VPSs again without explicit written permission, (i.e. through a ticket or whatever). It's a simple thing that would cover your ass legally and help restore trust here in the community.
+1, opened a ticket, as my services is not even active (just preordered)
Since he himself has admitted it here, there is enough evidence. GDPR is not something to play with
JFC why wouldn't you just reflect on what you did, see the concerns that people are raising, check the law (LOL!) rethink your answers and say fucking sorry, fucked up, we will change our behavior for future?
Invoice #5444 paid but Offer X - X-4 pending
You should've just used cloud-init. If for some reaaon customer removed it (their choice and you should respect that) from their systems, notify them in ticket instead, no need to hack into your customers' servers.
You can restrict what actions QEMU guest agent can perform. However, nothing* will really protect you from a malicious hypervisor (or its' owner), including FDE - encryption key can be dumped from VPS' RAM.
This is an accepted risk, the practice banks on the fact that your average LET host won't know how to do this and/or to make it as annoying as possible.
Doesn't have to be related to confidential stuff, just stop hosts from pulling shit like this.
What about not paying them instead?