-
-
Notifications
You must be signed in to change notification settings - Fork 7.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fail to connect to Fedora with the nightly build due to selinux #4267
Comments
Also tested with a debian based distro (Xubuntu 22.04) which works with the nightly build. |
@rustdesk any suggestions if you do not think this is valid? |
Tried disabling "Direct IP Access", and also tried appending "/r" to the id, both do not work. Any comments? |
Hi there, non-developer here. I am having multiple issues after upgrading to Fedora 38 as well. Based on some troubleshooting I did, if both "Direct IP access" and Wayland are disabled, yours may be an issue with selinux. Try this: quit the rustdesk application if you have it open, stop the rustdesk systemd service, set selinux in permissive mode and then restart the service, sudo systemctl stop rustdesk
sudo setenforce 0
sudo systemctl start rustdesk Then try connecting to your Fedora 38 machine. If it works, the issue is with selinux. Don't forget to reset selinux to enforcing mode once you are done, sudo setenforce 1 If the issue is with selinux, the only way I found to make the current rustdesk nightly work under X11 is to permanently disable the rustdesk systemd service (that is, unless you want to permanently disable selinux, which you should not do). Perhaps the developers will want to comment on the consequences of doing so, until they find a fix. I found that rustdesk still works on X11 with the service disabled (although you will probably need to manually open the rustdesk application in order to connect to your machine, since then rustdesk will not be running in the background). For the developers, I believe these are the relevant selinux logs in this situation:
|
@NoisyCoil Thanks, confirmed, |
Great. If so, @rustdesk could perhaps remove the duplicate label from this issue, re-open it, and modify its title to reflect that RustDesk nightly has issues on Fedora 38 (or earlier?) due to selinux? For more context, here are the complete selinux logs from journald:
Some notes:
|
@rustdesk Any decision on whether this issue should be re-opened, as it is not fixed? |
tracked by #3565 |
I will point out for future reference that this issue is not Android-specific (on the local side), but may affect Android as well as any other OS (like Fedora as per title) that uses selinux on the remote side. Thanks. |
Here is a workaround #3565 (comment) |
Other tools like anydesk will work out of the box. So it looks like an general design problem of rustdesk. And disable SELinux is extreme bad idea in the view of security. |
Bug Description
Environment: Fedora 36 to 38 with gnome. With the specfic configuration, connection is not possible with error:
Fail to connect via rendezvous server: Please try later
.How to Reproduce
etc/gdm/custom.conf
Expected Behavior
Successful connection.
Operating system(s) on local side and remote side
Win/Android -> Fedora
RustDesk Version(s) on local side and remote side
nightly -> nightly
Screenshots
N/A
Additional Context
Running Fedora with gnome on both physical machine and virtual machine.
Tested version 1.1.9 and the nightly build. The former works but the latter does not.
With wayland enabled, it is possible to connect by confirming sharing screen on the target machine with the nightly build.
Tested both self-hosting and default configuration, which does not affect the behaviour.
Tested with both android and win local sides, which does not affect the behaviour.
Not sure what information is required to ease debugging. Please instruct if any.
The text was updated successfully, but these errors were encountered: