![r/rustdesk icon](data:image/svg+xml,<svg xmlns="http://www.w3.org/2000/svg" width="256" height="256"><rect fill-opacity="0"/></svg>){kind=small}
rustdesk client config works 50% of the time
My company has made the switch over to rustdesk from a competing product. We are on the business self-hosting plan and run the pro version of the server. We use rustdesk for on-demand support where a customer calls in and needs help, so we generally do not permanently install rustdesk, instead using it for quick support sessions, with a few exceptions.
The problem we have been running into is that we host the rusdtesk exe on our website with the host and key encrypted into the file name as outlined here in the docs. So, the filename is rustdesk-licensed-{encrypted string}.exe and I've found this works about 50% of the time with clients, the other 50% the settings get ignored and the customer ends up on the free servers.
While this isn't the end of the world, I have to instruct our techs to remove out server and key to connect to those clients in those instances and then put them back when finished which is a hassle.
Has anybody else run into this? If so, have you found a solution that works reliably to keep the server settings intact?
I've setup our own custom build using GitHub actions but those EXE's aren't digitally signed so almost 99% of the time Windows Defender SmartScreen or AV products try to block it.
Comments Section
At the end, add "--".
Example: rustdesk-licensed--{encrypted string}--.exe
I have noticed that in some cases, when double downloaded, something like "copy (1)" is added to the end of the file name, and this ruins our config.
By adding -- at the end right after our config string, even if something is added to the file name, it won't corrupt the config string, and rustdesk will correctly retrieve it.
Interesting! I’ll give that a shot. Thanks you.
I can't get this to work with the encrypted string. Hoping this gets fixed soon, because currently I have no way of connecting clients who have downloaded the file more than once.
Compile with GitHub and have your settings hardcoded. Been using that for about 6 months now and not one connection failure due to server and keys yet.
I don’t have an answer to your issue but this is a very real solution.
I agree this would be the ideal way to do it as there is absolutly no way the settings would get dropped. Do you sign your own EXEs after they are compiled? or how do you get around the SmartScreen/AV picking it up? I find it's easier for my techs to change their settings as opposed to having to guide a customer into clicking "I understand the risks...yada yada yada" or whitelisting it in their AV.
Do you know if the 50% clients (connect to public server) installed RustDesk before?
Unsure but I'd venture to guess probably not. I have a few machines I've tested on that I know for certain have never used rustdesk previously that exhibit this problem.
Same Same issues. The custom build with Github actions are not digitally signed. So lots of AV blocking, AV deleting it and pretty much useless for support. Perhaps someone with more experience could figure out how to make those custom builds look ok to AV products. Anyone have ideas?