Linux Gaming

15774 readers

339 users here now

Gaming on the GNU/Linux operating system.

Recommended news sources:

Related chat:

Related Communities:

Please be nice to other members. Anyone not being nice will be banned. Keep it fun, respectful and just be awesome to each other.

founded 4 years ago

MODERATORS

[email protected]

Moonlight isn't working (discuss.tchncs.de)

submitted 4 months ago by [email protected] to c/[email protected]

12 comments fedilink hide all child comments

Hi I got the following problem. I successfully created a Tailscale network and a user from outside the network can login and connect to my network. That part works properly. We use a Fedora Linux PC as a host (Sunshine) and Moonlight Client on a Windows 10 PC. After tinkering for hours we can now see each other but I get the following issue "Request Timed Out (Error 4)" This issue always happens after inputting the PIN which is displayed on the Windows (Moonlight) on my Fedora PC (Sunshine) the client cannot connect after that but still sees my PC online and as a viable option to connect.

Additional Info: I've asked in the Moonlight Discord but I still got no answer.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 4 points 4 months ago* (last edited 4 months ago) (5 children)

Maybe firewalld is getting in the way. You can temporarily disable it:

sudo systemctl stop firewalld

If that doesn’t work, you can see if SELinux is the issue. Temporarily disable:

sudo setenforce 0

Be sure to re-enable SELinux:

sudo setenforce 1

[–] [email protected] 3 points 4 months ago (2 children)

Wouldn't it be better to open specific ports than disabling the entire firewall? Or am i missing something?

[–] [email protected] 9 points 4 months ago* (last edited 4 months ago) (1 children)

Better for testing to disable, then figure out ports and stuff afterward if the disable worked, I assume is the logic

[–] [email protected] 2 points 4 months ago

Good point, thanks for clarifying

load more comments (2 replies)