Rustdesk ignores --config string on deployment, works in gui #3221

New issue

Closed

opened 2026-02-21 01:12:48 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-21 01:12:48 -05:00

Owner

Originally created by @jpb1s on GitHub (Jan 8, 2025).

Bug Description

We use the Powershell script to deploy rustdesk via ansible on Windows 11. While setting a password works and the ID is correctly returned from the script, the --config parameter doesn't seem to have any effect. When I add the same config string to the GUI via settings / network / "Import server config" it works fine and sets the ID Server, Relay Server and the API key. We'd really like to deploy Rustdesk at scale without having to manually configure the network settings.

Is there a good way to debug this on my end? I'd appreciate any pointers.

How to Reproduce

Setup your own Rustserver
Setup Rustdesk with the settings of your server
Copy the config string via settings / network / "Export server config"
Edit the Powershell script to contain the exported config string
Run the powershell script on your system
Check the network settings to see whether they were applied

Expected Behavior

I'd expect Rustdesk to apply the config string when passed with --config. At least I'd expect some kind of output if it couldn't be applied for some reason.

Operating system(s) on local (controlling) side and remote (controlled) side

Ubuntu 24.04 -> Windows 11 (irrelevant, as issue is before control)

RustDesk Version(s) on local (controlling) side and remote (controlled) side

1.3.1 -> 1.3.6 (irrelevant, as issue is before control)

Screenshots

I don't think screenshots are helpful, will add if requested.

Additional Context

No response

Originally created by @jpb1s on GitHub (Jan 8, 2025). ### Bug Description We use [the Powershell script](https://rustdesk.com/docs/en/self-host/client-deployment/#powershell) to deploy rustdesk via ansible on Windows 11. While setting a password works and the ID is correctly returned from the script, the --config parameter doesn't seem to have any effect. When I add the same config string to the GUI via settings / network / "Import server config" it works fine and sets the ID Server, Relay Server and the API key. We'd really like to deploy Rustdesk at scale without having to manually configure the network settings. Is there a good way to debug this on my end? I'd appreciate any pointers. ### How to Reproduce 1. Setup your own Rustserver 2. Setup Rustdesk with the settings of your server 3. Copy the config string via settings / network / "Export server config" 4. Edit [the Powershell script](https://rustdesk.com/docs/en/self-host/client-deployment/#powershell) to contain the exported config string 5. Run the powershell script on your system 6. Check the network settings to see whether they were applied ### Expected Behavior I'd expect Rustdesk to apply the config string when passed with --config. At least I'd expect some kind of output if it couldn't be applied for some reason. ### Operating system(s) on local (controlling) side and remote (controlled) side Ubuntu 24.04 -> Windows 11 (irrelevant, as issue is before control) ### RustDesk Version(s) on local (controlling) side and remote (controlled) side 1.3.1 -> 1.3.6 (irrelevant, as issue is before control) ### Screenshots I don't think screenshots are helpful, will add if requested. ### Additional Context _No response_