Nighly Builds ignoring Github Actions Secrets. Using self hosted server no longer works. #3926

New issue

Closed

opened 2026-02-21 01:43:13 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-21 01:43:13 -05:00

Owner

Originally created by @BCHTester on GitHub (Jan 16, 2026).

Bug Description

It looks like Flutter Nightly Builds are ignoring the Github Actions Secrets when building my own RustDesk executable.
Why?

How to Reproduce

Go to https://github.com/rustdesk/rustdesk/fork and click “Create fork”.
On the fork you just created go to “Settings -> Secrets and variables -> Actions”.
Click “New repository secret”, for the name put RENDEZVOUS_SERVER, for the secret put your servers name/ip address.
Click “Add secret”.
Click “New repository secret” again, for the name put RS_PUB_KEY, for the secret put your servers public key.
Click “Add secret”.
On the fork you just created go to “Settings -> Actions -> General”.
On the right, select “Allow all actions and reusable workflows”.
On your fork you just created go to “Settings -> Actions -> General”.
Scroll down and under Workflow permissions enable “Read and write permissions”.
Then go to your fork and click Actions, and on the left, select “Flutter Nightly Build”. Then on the right, click “Enable workflow”.
Finally you can click “Run workflow” to build the RustDesk clients for all of the supported platforms.
After the workflow is done running you can download the packages it built.
Go to the main page of your fork, on the right click “Releases”. The packages you just built will show up under “Nightly”.

Expected Behavior

RustDesk files should use the Server and Public Key you entered on your Secrets but it still uses the default server

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

Windows 11 > Windows 11

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

1.4.5

Screenshots

Additional Context

No response

Originally created by @BCHTester on GitHub (Jan 16, 2026). ### Bug Description It looks like Flutter Nightly Builds are ignoring the Github Actions Secrets when building my own RustDesk executable. Why? ### How to Reproduce 1. Go to [https://github.com/rustdesk/rustdesk/fork](https://github.com/rustdesk/rustdesk/fork) and click “Create fork”. 2. On the fork you just created go to “Settings -> Secrets and variables -> Actions”. 3. Click “New repository secret”, for the name put RENDEZVOUS_SERVER, for the secret put your servers name/ip address. 4. Click “Add secret”. 5. Click “New repository secret” again, for the name put RS_PUB_KEY, for the secret put your servers public key. 6. Click “Add secret”. 7. On the fork you just created go to “Settings -> Actions -> General”. 8. On the right, select “Allow all actions and reusable workflows”. 9. On your fork you just created go to “Settings -> Actions -> General”. 10. Scroll down and under Workflow permissions enable “Read and write permissions”. 11. Then go to your fork and click Actions, and on the left, select “Flutter Nightly Build”. Then on the right, click “Enable workflow”. 12. Finally you can click “Run workflow” to build the RustDesk clients for all of the supported platforms. 13. After the workflow is done running you can download the packages it built. 14. Go to the main page of your fork, on the right click “Releases”. The packages you just built will show up under “Nightly”. ### Expected Behavior RustDesk files should use the Server and Public Key you entered on your Secrets but it still uses the default server ### Operating system(s) on local (controlling) side and remote (controlled) side Windows 11 > Windows 11 ### RustDesk Version(s) on local (controlling) side and remote (controlled) side 1.4.5 ### Screenshots <img width="998" height="525" alt="Image" src="https://github.com/user-attachments/assets/2697ab92-3e43-4939-abca-2876a5376a7f" /> ### Additional Context _No response_