Both sides previous revisionPrevious revisionNext revision | Previous revision |
computing:rustdesk [2024/11/02 17:17] – oemb1905 | computing:rustdesk [2024/11/02 17:26] (current) – oemb1905 |
---|
You can always download the package as a .deb and install it directly. The [[https://github.com/rustdesk/rustdesk-server/releases/tag/1.1.12|rustdesk repository]] has the latest amd64. I used wget to grab this, and installed it with dpkg -i. If you take this approach, you will need to set up the hbbs/hbbr environments manually. After reviewing the code and discussing the project with members of the [[https://matrix.to/#/#pubglug:gnulinux.club|pubglug community]], I decided the script was just fine. The script prompts the user with two questions. First, do you want to be IP-based or domain-based, I chose domain. It also asks if you want to set up the http server; I also chose yes. After the script was done, I went ahead and focused on setting up apache2's reverse proxy configs. | You can always download the package as a .deb and install it directly. The [[https://github.com/rustdesk/rustdesk-server/releases/tag/1.1.12|rustdesk repository]] has the latest amd64. I used wget to grab this, and installed it with dpkg -i. If you take this approach, you will need to set up the hbbs/hbbr environments manually. After reviewing the code and discussing the project with members of the [[https://matrix.to/#/#pubglug:gnulinux.club|pubglug community]], I decided the script was just fine. The script prompts the user with two questions. First, do you want to be IP-based or domain-based, I chose domain. It also asks if you want to set up the http server; I also chose yes. After the script was done, I went ahead and focused on setting up apache2's reverse proxy configs. |
| |
* HTTP Virtual Host | * [[https://repo.haacksnetworking.org/haacknet/haackingclub/-/blob/main/configs/webservers/apache/apache-rustdesk-domain.com.conf?ref_type=heads|HTTP Virtual Host]] |
* SSL Virtual Host | * [[https://repo.haacksnetworking.org/haacknet/haackingclub/-/blob/main/configs/webservers/apache/apache-rustdesk-domain.com-ssl.conf?ref_type=heads|TLS Virtual Host]] |
| |
Use the configs above and adapt to your needs. However, before you put them in place using ''a2ensite'', you should first setup TLS for your domain using the default virtual host. Leaving ''000-default.conf'' as the active virtual host for now, run the following commands: | Use the configs above and adapt to your needs. However, before you put them in place using ''a2ensite'', you should first setup TLS for your domain using the default virtual host. Leaving ''000-default.conf'' as the active virtual host for now, run the following commands: |
cat /opt/rustdesk/id_ed25519.pub | cat /opt/rustdesk/id_ed25519.pub |
| |
The output above is your API key. On each client that you want to use with this server, you open the RustDesk client, unlock Network Settings, and enter this key into the parameter called "Key." In the sections above, enter you FQDN.tld without http:// or https://. Here's an example: | The output above is your API key. On each client that you want to use with this server, you open the RustDesk client, unlock Network Settings, and enter this key into the parameter called "Key." In the sections above, enter you FQDN.tld without http:// or https://. Here's an example: \\ |
| \\ |
| |
{{ :computing:screenshot_from_2024-11-02_11-12-52.png?direct&600 |}} | {{ :computing:screenshot_from_2024-11-02_11-12-52.png?direct&800 |}} |
| |
| \\ |
| // |
Personally, I choose to use both one-time keys and set/static passwords for the connections, but those are personal preference decisions, so I won't detail that here. From here on out, just make sure to set up all other clients equivalently and you are all set. After you confirm all is working, you can test to see if RustDesk was indeed using your new self-hosted relay by attempting to use it when your VPS is powered down. The connection will fail because neither client is using the RustDesk default server any longer and yours is down. A bit overkill, but we like to confirm things at Haack's Networking lol. Well, hope this helps other Debian users who want to use and set this up without using docker! | Personally, I choose to use both one-time keys and set/static passwords for the connections, but those are personal preference decisions, so I won't detail that here. From here on out, just make sure to set up all other clients equivalently and you are all set. After you confirm all is working, you can test to see if RustDesk was indeed using your new self-hosted relay by attempting to use it when your VPS is powered down. The connection will fail because neither client is using the RustDesk default server any longer and yours is down. A bit overkill, but we like to confirm things at Haack's Networking lol. Well, hope this helps other Debian users who want to use and set this up without using docker! |
| |
--- //[[webmaster@haacksnetworking.org|oemb1905]] 2024/11/02 16:39// | --- //[[webmaster@haacksnetworking.org|oemb1905]] 2024/11/02 17:23// |