computing:rustdesk
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| computing:rustdesk [2026/01/01 18:56] – oemb1905 | computing:rustdesk [2026/01/02 04:26] (current) – oemb1905 | ||
|---|---|---|---|
| Line 12: | Line 12: | ||
| This tutorial is for Debian users who want to create a self-hosted RustDesk instance manually. This covers installing the relay server (hbbr), the signaling server (hbbs), and the gohttp server (for client downloads and/or configs). After installing these services, I go through how to setup each systemd unit and, additionally, | This tutorial is for Debian users who want to create a self-hosted RustDesk instance manually. This covers installing the relay server (hbbr), the signaling server (hbbs), and the gohttp server (for client downloads and/or configs). After installing these services, I go through how to setup each systemd unit and, additionally, | ||
| - | <code bash> | + | |
| - | sudo ufw allow 22/tcp | + | sudo ufw allow 80/tcp |
| - | sudo ufw allow 80/tcp | + | sudo ufw allow 443/tcp |
| - | sudo ufw allow 443/tcp | + | sudo ufw allow 21114: |
| - | sudo ufw allow 21114: | + | sudo ufw allow 21116/udp |
| - | sudo ufw allow 21116/udp | + | sudo ufw enable |
| - | sudo ufw enable | + | |
| - | </ | + | |
| Let's now download the latest version of rustdesk, unzip it, and then copy the binaries into the standard location inside ''/ | Let's now download the latest version of rustdesk, unzip it, and then copy the binaries into the standard location inside ''/ | ||
| - | <code bash> | + | |
| - | cd /tmp | + | wget https:// |
| - | wget https:// | + | unzip rustdesk-server-linux-amd64.zip |
| - | unzip rustdesk-server-linux-amd64.zip | + | sudo mkdir -p / |
| - | sudo mkdir -p / | + | sudo cp amd64/hbbs amd64/hbbr amd64/ |
| - | sudo cp amd64/hbbs amd64/hbbr amd64/ | + | sudo chmod +x / |
| - | sudo chmod +x / | + | |
| - | </ | + | |
| After the relay and signaling servers are installed and copied to the standard locations, we can download and install the gohttp server: | After the relay and signaling servers are installed and copied to the standard locations, we can download and install the gohttp server: | ||
| - | <code bash> | + | |
| - | sudo mkdir -p /opt/gohttp / | + | cd /tmp |
| - | cd /tmp | + | wget https:// |
| - | wget https:// | + | tar -xzf gohttpserver_1.3.0_linux_amd64.tar.gz |
| - | tar -xzf gohttpserver_1.3.0_linux_amd64.tar.gz | + | sudo cp gohttpserver / |
| - | sudo cp gohttpserver / | + | sudo chmod +x / |
| - | sudo chmod +x / | + | |
| - | </ | + | |
| We can now navigate to our dedicated rustdesk directory and generate our keypair: | We can now navigate to our dedicated rustdesk directory and generate our keypair: | ||
| Line 118: | Line 112: | ||
| We can now enable all the units and start the services: | We can now enable all the units and start the services: | ||
| - | sudo systemctl daemon-reload | + | |
| - | sudo systemctl enable rustdesksignal rustdeskrelay gohttpserver | + | sudo systemctl enable rustdesksignal rustdeskrelay gohttpserver |
| - | sudo systemctl start rustdesksignal rustdeskrelay gohttpserver | + | sudo systemctl start rustdesksignal rustdeskrelay gohttpserver |
| - | sudo systemctl status rustdesksignal rustdeskrelay gohttpserver | + | sudo systemctl status rustdesksignal rustdeskrelay gohttpserver |
| We can now drop the gohttp server behind an apache reverse proxy. To do that, let's install certbot, cut a certificate, | We can now drop the gohttp server behind an apache reverse proxy. To do that, let's install certbot, cut a certificate, | ||
| Line 221: | Line 215: | ||
| Check your configs with '' | Check your configs with '' | ||
| - | - **ID Server**: hackingclub.org | + | * **ID Server**: hackingclub.org |
| - | - **Relay Server**: hackingclub.org | + | |
| - | - **API Server**: https:// | + | |
| - | - **Key**: API Key from above | + | |
| Here's an example of what this section looks like. Note that entering a value in API Server is moot - that's only supported by the premium/ | Here's an example of what this section looks like. Note that entering a value in API Server is moot - that's only supported by the premium/ | ||
| Line 230: | Line 224: | ||
| {{ : | {{ : | ||
| - | Enter the same values on your primary workstation. Once that's done for your workstation and at least one client, you can then specify the '' | + | Enter the same values on your primary workstation. Once that's done for your workstation and at least one client, you can then specify the ID your " |
| - | <code bash> | + | |
| - | sudo systemctl stop rustdesksignal rustdeskrelay gohttpserver | + | cd /tmp |
| - | cd /tmp | + | wget https:// |
| - | wget https:// | + | unzip -o rustdesk-server-linux-amd64.zip |
| - | unzip -o rustdesk-server-linux-amd64.zip | + | sudo cp amd64/hbbs amd64/hbbr / |
| - | sudo cp amd64/hbbs amd64/hbbr / | + | sudo chmod +x / |
| - | sudo chmod +x / | + | sudo systemctl start rustdesksignal rustdeskrelay gohttpserver |
| - | sudo systemctl start rustdesksignal rustdeskrelay gohttpserver | + | sudo systemctl status rustdesksignal rustdeskrelay gohttpserver |
| - | sudo systemctl status rustdesksignal rustdeskrelay gohttpserver | + | |
| - | </ | + | |
| That's basically it. The new binaries are executed and controlled by the pre-established systemd units, so you merely replace the binaries and make them executable and you are good to go. If the gohttp server has been updated, similarly: | That's basically it. The new binaries are executed and controlled by the pre-established systemd units, so you merely replace the binaries and make them executable and you are good to go. If the gohttp server has been updated, similarly: | ||
| - | <code bash> | + | |
| - | sudo systemctl stop gohttpserver | + | cd /tmp |
| - | cd /tmp | + | wget https:// |
| - | wget https:// | + | tar -xzf gohttpserver_NEW_VERSION_linux_amd64.tar.gz |
| - | tar -xzf gohttpserver_NEW_VERSION_linux_amd64.tar.gz | + | sudo cp gohttpserver / |
| - | sudo cp gohttpserver / | + | sudo chmod +x / |
| - | sudo chmod +x / | + | sudo systemctl start gohttpserver |
| - | sudo systemctl start gohttpserver | + | sudo systemctl status gohttpserver |
| - | sudo systemctl status gohttpserver | + | |
| - | </ | + | |
| The password is specified in the systemd unit, which remains unchanged. Just make sure to restart the service as directed above and it will invoke that same value, but on the updated go server. You should now be fully up to date. Hope this helps others wanting to avoid using the automated script / understand all the moving parts of the instance. Happy hacking! | The password is specified in the systemd unit, which remains unchanged. Just make sure to restart the service as directed above and it will invoke that same value, but on the updated go server. You should now be fully up to date. Hope this helps others wanting to avoid using the automated script / understand all the moving parts of the instance. Happy hacking! | ||
| --- // | --- // | ||
computing/rustdesk.1767293810.txt.gz · Last modified: by oemb1905
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: GNU Free Documentation License 1.3
