moonlight-stream / nvidia-gamestream-issues

Repository for tracking known GameStream issues that require a fix from Nvidia
11 stars 1 forks source link

RTSP handshake error 60 after driver update #32

Open cgutman opened 2 years ago

cgutman commented 2 years ago

A few users have reported RTSP handshake error 60 after updating their drivers. The issue is not affecting the majority of Moonlight users (including myself), but it affects some users very consistently. It must be something specific to their client, host, or streaming settings that is triggering the issue reliably.

Error 60 is ETIMEDOUT which would indicate either a connection timeout or a timeout waiting for a reply from the host. In some cases, GeForce Experience will fail to reply to RTSP messages while waiting for NvStreamer.exe to start. Specific invalid streaming settings (such as resolutions below 256x256) are known to cause NvStreamer.exe to crash, so that may be what's happening here.

Affected users, please provide the following info:

DouglasC2022 commented 2 years ago

I am currently experiencing this issue but only over online attempts, not in local network. I am able to connect successfully when at home in my network, but attempts to connect from anywhere else causes me to get this error. I have ensured the ports are open and available through my router / modem.

cgutman commented 2 years ago

Ah, if it happens on remote streaming but not local streaming that definitely points to some issue with port forwarding. I suspect the issue is with UDP port 48000. GeForce Experience will stall the RTSP handshake until it gets a response on that port, so that can lead to timeouts if it's not forwarded properly.

Can you confirm that you have that UDP 48000 forwarded properly?

mikesells commented 2 years ago

I have the same issue as above. My belief is that no forwarding is necessary if I'm using something like ZeroTier correct? I have run moonlight tester and it says all is well.

cgutman commented 2 years ago

That's correct

jvmesa commented 2 years ago

Same error for me. For more info: Only online. LAN / WLAN works fine. Client = Ipad Pro 11 IpadOS 15.5 M Driver = 516.59 Moonlight Internet Streaming Tester pass correct (attached). Launching the game/app I see client connects with PC and initiate the process correctly,The game/app is launched in the PC but at the same time the client stops returning this error code. The game/app remains working on the PC so I should close it locally.

Thanks

TestOK

dmiyamasu commented 1 year ago

I am experiencing this issue too. Any updates?

billyjacoby commented 1 year ago

I'm having this same issue using a Wireguard VPN that works for a number of other services.

aur3l14no commented 1 year ago

Same, I'm having this same issue using a tailscale.

cyturralde commented 1 year ago

Does anyone have a fix for this?

gtttt33399 commented 1 year ago

Same issue: I access my LAN via OpenVPN on my NAS from outside my network and receive the rtsp 60 error when trying to connect to Sunshine on my PC. Also happens when I connect via TailScale directly to the PC. Moonlight client reports no issues when I select the "test network" option and all other remote services are working via the VPN. I've got the port forwarding set up properly on my router, etc. running a 4090 on the 531.79 driver.

If I click on an app via Moonlight while on my VPN, the program starts up (which I can see when I hop on my PC later) but then the 60 error hits.

This used to work fine with GFE in the past (although I couldn't tell you what driver version, unfortunately).

Attaching the log here as well — everything until "CLIENT DISCONNECTED" is me connecting via my laptop on the home network, everything afterwards until [2023:05:21:22:31:59] is me trying to connect from a mobile network and OpenVPN.

sunshinelog.txt

EDIT: Think I managed to sort it out by editing my OpenVPN config. Enabled redirect gateway (which is fine for my purposes — might not be for others!) and manually defined the DNS servers.

thelazurus commented 1 year ago

Running into the same issue through Tailscale.

joshdee commented 1 year ago

Same exact issue as well. But I have a router that is capable of self-hosting a VPN through my whole home Wi-Fi, specifically Amplifi Alien. It's a minor issue but I really want to use Tailscale. ^^

SgtSweetieBelle commented 1 year ago

same issue. router port forwarded and everything :(

ClassyCar commented 1 year ago

I've got the same issue. Has anyone found a solution yet? I'm using Zerotier one and trying to connect to my PC from my iPhone.

adnanjamil-frontend commented 11 months ago

Same issue here, any solutions? Connecting with iPhone using Zerotier

Oolong22 commented 11 months ago

Anyone found a solution? Using Tailscale to connect from my Iphone. (Sidenote: it seems like a lot of us having problems comes from trying to connect from Iphone. I'll try with my laptop later to see if that's the case)

boyphongsakorn commented 6 months ago

any update? i have a same issue with Tailscale (Mac and Android)

slrgt commented 2 months ago

Still having the same issue. Happens on tailscale and zerotier but not if im local. Im on an iphone

alanwake47 commented 2 months ago

Same issue. Iphone 14 Pro Max and Ipad Pro M4 11in. Seems like and iOS specific thing. Works flawlessly on android. I even used my iPhone as a hotspot for my Pixel 7 and was able to connect. I use Tailscale, & Sunshine to remotely connect

knittycatkitty commented 2 months ago

Same issue, iPhone 14 Pro Max on iOS 18

can verify it works on Galaxy A51 on Android separately though, must be an iOS issue

newlandk commented 1 month ago

iPhone 16 Pro on iOS 18.1 Public Beta 2

I'm hoping this may guide towards a more permanent solution assuming this is able to solve anyone else's issue.

TLDR: Providing Wireguard a 0's route (0.0.0.0/0) in the Allowed IPs list fixed the "error 60" issue and is working as expected now.

Test scenarios

Network Connection Wireguard Allowed IPs Result
VPN via Guest Wireless Network 192.168.0.0/24 (Same network Sunshine host) Working
VPN over 5G 192.168.0.0/24 NOT Working (error 60)
VPN over 5G Hotspot 192.168.0.0/24 NOT Working (error 60)
VPN over 5G 192.168.0.0/24, 0.0.0.0/0 Working
VPN over 5G Hotspot 192.168.0.0/24, 0.0.0.0/0 Working

In all of these scenarios I can confirm with packet captures that traffic is traversing the tunnel between my phone and the host running Sunshine. In the scenarios where it's not working I can see that it's receiving 200 OK from the server and bidirectional traffic to TCP ports 47989 and 47984, but never establishes the UDP stream.

My peer endpoint is listed as an IPv6 address when on cellular and most likely traversing a 6to4 gateway. I'm thinking this may be a catalyst as the first test traversing my guest network over VPN is IPv4 only and worked as intended with only the internal networks routed over the VPN. Plumbing in the 0's route effectively making the VPN a full tunnel seems to be changing the behavior allowing it to establish the stream.

sopresig commented 3 weeks ago

I can successfully stream within the local area network, but when I connect to my sunshine through an FRP tunnel, I have confirmed that the port forwarding for all seven ports is configured correctly, and I can also ping through. However, I encounter ERR 60.

DailyDisco commented 6 days ago

Any solution to this yet?

Does UDnP have to be enabled?

knittycatkitty commented 6 days ago

I haven’t been able to attend to this issue as I’m currently missing a charger for my Lenovo laptop and want to source a new/used one locally.

I’ll update when I get my hands on one.

Justin R.

On Tue, Nov 19, 2024 at 11:38 PM Diego (D) @.***> wrote:

Any solution to this yet?

Does UDnP have to be enabled?

— Reply to this email directly, view it on GitHub https://github.com/moonlight-stream/nvidia-gamestream-issues/issues/32#issuecomment-2487411564, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKE74S5PKSXX4UW5I5SXI5L2BQG6DAVCNFSM5XLVJ332U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TENBYG42DCMJVGY2A . You are receiving this because you commented.Message ID: @.*** com>