[SOLVED] Rustdesk Issue - Agent Configuration Deployment

Questions about WAPT Packaging / Requests and help regarding Wapt packages.
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Locked
clafon
Messages: 109
Registration: Nov 06, 2024 - 10:56

January 23, 2025 - 3:49 PM

Wapt version: 2.6.0.16795 - Enterprise Edition
Server OS: Debian 12
Target operating systems: Windows 10
Os Machine administration: Win server 2022

Good morning,

I'm creating this forum post alongside our Discord discussions, in case it can help other users

We set up a Rustdesk server on a dedicated server. We validated its operation with a manual configuration of the workstations.

Having WAPT Enterprise, we wanted to industrialize the deployment; to do this, we imported the package: rustDesk-config-template
He warns us that he needs his dependency, namely the package rustdesk and he downloads it.

Note: the Rustdesk package version that is downloaded is an x86 version (which caused us problems when deploying it on our x64 machines), so we had to manually download the x64 version

The procedure followed:
in the "Private Repository" we right-clicked on the rustdesk-config-template package and launched the "update package".
rutdesk1.PNG
rutdesk1.PNG (16.34 KiB) Viewed 8364 times
Then we selected "Run update-package for selected packages",
rutdesk2.PNG
rutdesk2.PNG (19.35 KB) Viewed 8364 times
after answering "yes" to the first question
rutdesk3.PNG
rutdesk3.PNG (5.85 KB) Viewed 8364 times
We have completed the requested information (sorry, the forum doesn't seem to allow me to add more screenshots):
{
"host": "YOUR_SERVER_IP",
"relay": "YOUR_SERVER_IP",
"key": "YOUR_PUB_KEY", (note that the key may end with an =)
"api": ""
}

We confirmed the order by clicking "OK" and then clicked "Upload selected packages". This created a package for us rustdesk-configThis package contains a rusdesk.cfg file with the previously saved configuration coded.

After discussing it with Simon on Discord, it appears that the coded configuration had an extra carriage return. We therefore repeated the entire procedure, and although the configuration seems correct this time, we see no change, namely:

Station 1: Manually configuring the Rustdesk client: Working OK
Station 2: Advanced configuration with Wapt: Not working
Station 1: Removal of manual configuration + advanced configuration with Wapt's: Not working

However, if I leave the configuration manual and push the configuration via Wapt, it still works. So I'm wondering if the package contents are actually being applied to the package...

When pushing a configuration with Wapt, on the RustDesk client in "Settings > Network > ID/Relay Server" the fields remain empty.
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

January 24, 2025 - 09:59

Hi Cédric,

After reviewing the code, I noticed there was indeed an issue when the configuration wasn't converted to cfg but to json.

I've made a fix in the store; please try it out.

Simon
clafon
Messages: 109
Registration: Nov 06, 2024 - 10:56

January 27, 2025 - 1:27 PM

Good morning,

I downloaded and tried to use v20 but there seems to be a small bug:
rustdesk_config_20.PNG
rustdesk_config_20.PNG (21.54 KB) Viewed 8295 times
Where can I find the "Audit data" file?

Edit: Found it, unlike the previous package, the JSON question should be answered with no
clafon
Messages: 109
Registration: Nov 06, 2024 - 10:56

January 27, 2025 - 1:49 PM

I confirm it works correctly, :) thank you.
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

January 27, 2025 - 4:26 PM

Thanks for the feedback, I also made a small patch today for the Linux clients.
clafon
Messages: 109
Registration: Nov 06, 2024 - 10:56

January 27, 2025 - 4:41 PM

sfonteneau wrote: Jan 27, 2025 - 4:26 PM Thanks for the feedback, I also made a small patch today for the Linux clients.
And for a MacOS client?
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

January 27, 2025 - 4:46 PM

I tried here, but even with manual RustDesk configuration, it didn't work.

Security on Mac is "different," so you have to accept quite a bit of the GUI stuff; in the end, I don't know if it's even possible...
clafon
Messages: 109
Registration: Nov 06, 2024 - 10:56

January 27, 2025 - 4:50 PM

Ah...that's a shame,
but thank you.
Locked