You are not logged in.
Greetings,
I am currently connecting using rustdesk + tailscale and it works great connecting to my raspberry PI (Having rustdek-server installed) . But on my desktop Arch installation I basically cannot connect to it. I can ping the machine using the tailscale IP.
I can actually login but without using the rustdesk-server (tailscale ip and publick key) by using the normal rustdesk ID not self holsted. I have tried disabling entirely firewalld.
I can access shared folders using taiscale IP on my Arch box, but something is preventing for me to connect using self-hosted Rustdesk.
I am on KDE with Wayland, but the issue is that after I put my tailscale IP and click on connect ---> I get stuck in connecting status until timeout.
Also I do not know what additional information to provide that can be helpful.
Tailscale is running
systemctl status rustdesk-server-hbbs.service --> enabled and running
In rustdesk: enable direct ip access is checked. on ID/Relay server the ID = tailscale IP for my arch box --> Key = /opt/rustdesk-server/data/ --> .pub key used.
Any help is most welcome.
Offline
I started down the path of installing RustDesk as a self hosted application. However, after looking at https://tailscale.com/blog/tailscale-ru … top-access it convinced me that I don't need to self host. Tailscale already does what the RustDesk server does. I made the changes on each client and connected directly and that worked for me.
Offline
I started down the path of installing RustDesk as a self hosted application. However, after looking at https://tailscale.com/blog/tailscale-ru … top-access it convinced me that I don't need to self host. Tailscale already does what the RustDesk server does. I made the changes on each client and connected directly and that worked for me.
Thansk! but for some reason if I disable rustdesk server and remove the network ID and key , and I only use the Tailscale ip, I cannot connect either, it stays in connecting...
Weird think is that I can ping and even access my shared files. I stopped the firwall to take it out of the equation, same as for the rustdesk-server services. No luck ![]()
Offline