RTSP handshake fail

[AdriftUrchin]

So the streaming on local works just fine, but when I stream over internet I get that error. It used to work just fine a week or so ago but ever since I tried to use it again it doesn't work. Before I started trying to stream again, I accidentally installed Avast antivirus but deleted that (don't know if that could've caused something to happen). I also got malwarebytes premium trial but that has ended (again I don't know if that could've caused something). I have all the ports forwarded correctly (as seen in the picture below) and I've tested them with the port tester and they are open. I've noticed when I try to open something over the internet that is able to open the application, so some connection is being made. Any help is appreciated as I have been trying to solve this for quite some time now.

[nathankferguson]

Having the exact same issue. Haven't used Moonlight in a while on my mobile, went in to set all my ports from the guide and RTSP handshake keeps failing. Tried every possible TCP/UDP 48010 port combination that I've seen in different threads, and no help.

[Slayer418]

Don't know if you guys are trying to stream on mobile internet or on a WIFI connection (over the internet still) but either way, I heard some mobile service provider (scumbag ones) can block RTSP request, just like a work office, for example, can be behind a proxy that does just the same. I'm myself in the later of these cases, my work place is behind WatchGuard proxy and I'm still trying to find a bypass.

[JoeJoeyMa]

Do you try to confirm that it is a moblie phone instead of a computer that has a problem with the connection? I also having the exact same issue too, but it was visit a LAN computer normally, it was finally found to be a computer.

Make sure Win10 NvContainerNetworkService-NVIDIA NetworkService Container- "C:\Program Files\NVIDIA Corporation\NvContainer\nvcontainer.exe" is open

[nathankferguson]

I can connect over my WiFi no problem, it is just the mobile network that is failing. Didn't think about carrier support as an issue, but could be. I have Cricket Wireless, but I'm fairly certain I was using them last time Moonlight was working.

[AdriftUrchin]

I have two phones, both different mobile networks neither work. I also tried using my schools wifi to no avail.

[GManASG]

I was having the same issue, I am also on cricket wireless and it used to work, they are owned by AT&T, RTSP handshake fails.

I used a vpn I have on my Android phone and I am able to stand successfully with vpn on.

I disable the vpn and handshake fails, my conclusion is they have started blocking RTSP connections. Shane vpn shows down the stream to much.

[MagFlux]

@GManASG,

Thanks for the information, really unfortunate but sounds like it's the service provider causing these issues this based on that. Used to work for me as well and I can no longer connect via cellular on AT&T. It been a while since I tried to stream via my cellular connection, so I can't pinpoint when it stopped working. Like others I can connect and launch applications but the RTSP ultimately fails. Everything works via Wi-Fi just fine.

[MagFlux]

Well, I'd like to add that I just attempted using a demo RTSP stream provided by Wowza media systems and it works for me via Wi-Fi (Comcast) as well as via cellular (AT&T). Not sure what to make of that information but figured I'd provide it. I used the VLC app on Android Oreo 8.1.0 to open said stream.

rtsp://184.72.239.149/vod/mp4:BigBuckBunny_175k.mov

[cgutman]

I wonder if the issue is connecting RTSP at the non-standard 48010 port number that GeForce Experience uses. Can you try running a Wireshark packet capture on your PC while you try to stream over LTE, then save the capture and post a link here?

[AdriftUrchin]

@cgutman Don't know if you asking me, if so sorry for late reply. Anyways I don't know how to do what you said.

[MagFlux]

@AdriftUrchin, Wireshark is a FOSS network packet analyzer utility. I use it quite often for work and have no problem doing it but I just haven't had the chance to do so as work has been keeping me ridiculously busy. That being said if you want to give it a go before I get around to it, check out https://www.wireshark.org/ to download the utility. Since @cgutman isn't asking for you to do any of the analysis, all you need to do is install it, start the capture, attempt to recreate the problem, stop the capture, then send him the capture file so he can analyze it and see what may be going on.

[Meems33]

Similar to https://github.com/irtimmer/moonlight-embedded/issues/609, https://github.com/avtoneru/moonlight-SBS/issues/1.

See https://github.com/irtimmer/moonlight-embedded/issues/609#issuecomment-375469086

It appears the issue was fixed for moonlight-embedded after upgrading moonlight-common-c

[cgutman]

@Meems33 Can you paste the XML output of http://localhost:47989/serverinfo on your PC?

[Meems33]

Per https://github.com/irtimmer/moonlight-embedded/commit/df0114ee051822c580ff45ba3a997e61771b791a it requires updating moonlight-common. I would assume that the same fix would be needed for android as well.

http://localhost:47989/serverinfo:

<?xml version="1.0" encoding="UTF-16"?>
<?xml version="1.0"?>
<root protocol_version="0.1" query="serverinfo" status_code="200" status_message="OK">
  <AuthenticationType>1</AuthenticationType>
  <ConnectionState/>
  <CurrentClient>0</CurrentClient>
  <GfeVersion>3.13.1.30</GfeVersion>
  <GsVersion>gs_04_05_23698325</GsVersion>
  <HttpsPort>47984</HttpsPort>
  <LocalIP>127.0.0.1</LocalIP>
  <LocalIPs>
    <Address>192.168.0.112</Address>
  </LocalIPs>
  <LoginState>2</LoginState>
  <MaxLumaPixelsH264>737235008</MaxLumaPixelsH264>
  <MaxLumaPixelsHEVC>589622848</MaxLumaPixelsHEVC>
  <Mode>0</Mode>
  <PairStatus>0</PairStatus>
  <ServerCapability>1847</ServerCapability>
  <ServerCodecModeSupport>3843</ServerCodecModeSupport>
  <ServerColorSpaceSupport>2</ServerColorSpaceSupport>
  <SupportedDisplayMode>
    <DisplayMode>
      <Height>2160</Height>
      <RefreshRate>60</RefreshRate>
      <Width>3840</Width>
    </DisplayMode>
    <DisplayMode>
      <Height>2160</Height>
      <RefreshRate>30</RefreshRate>
      <Width>3840</Width>
    </DisplayMode>
    <DisplayMode>
      <Height>1080</Height>
      <RefreshRate>60</RefreshRate>
      <Width>1920</Width>
    </DisplayMode>
    <DisplayMode>
      <Height>1080</Height>
      <RefreshRate>30</RefreshRate>
      <Width>1920</Width>
    </DisplayMode>
    <DisplayMode>
      <Height>720</Height>
      <RefreshRate>60</RefreshRate>
      <Width>1280</Width>
    </DisplayMode>
    <DisplayMode>
      <Height>720</Height>
      <RefreshRate>30</RefreshRate>
      <Width>1280</Width>
    </DisplayMode>
  </SupportedDisplayMode>
  <accountId>*****</accountId>
  <appversion>7.1.405.0</appversion>
  <currentgame>999999</currentgame>
  <gamelistid>f580c7e534224318530e44256d2ec5d5</gamelistid>
  <gputype>GeForce GTX 1060 6GB</gputype>
  <hostname>DESKTOP-SAOGNKN</hostname>
  <mac>00:00:00:00:00:00</mac>
  <numofapps>0</numofapps>
  <resyncSuccessful>0</resyncSuccessful>
  <state>MJOLNIR_STATE_SERVER_BUSY</state>
  <uniqueid>57a0ace9-e4d9-4262-9e7d-136b861778f6</uniqueid>
</root>

[cgutman]

@Meems33 It looks like your serverinfo is as expected. Current moonlight-common-c will detect your RTSP protocol properly, as will current Moonlight clients.

The issue here actually relates to RTSP traffic being filtered by a firewall after the move to TCP in GFE 3.12, not sending over UDP instead of TCP as was happening in your case.

[AdriftUrchin]

Sorry for ditching this post, the phone that I used to stream kinda soft bricked on me. I'm gonna be getting a new phone in a few days here so if the same problem still arises I would like to revive this post.

[lynx31]

Having the same issue both on Android and Chrome. A restart of the host PC sometimes helps, but often not

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[MagFlux]

I guess this isn't too common of a usage scenario but I can confirm that it's still a problem for me on AT&T. Just revisiting since this issue was recently marked as stale by the bot.

[AdriftUrchin]

Just started school again and got a new phone. When i get back home I will see if I still have the same problems.

[GManASG]

Definitely still have this issue

On Wed, Aug 29, 2018, 9:49 AM Morgan notifications@github.com wrote:

Just started school again and got a new phone. When i get back home I will see if I still have the same problems.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/moonlight-stream/moonlight-android/issues/528#issuecomment-416960395, or mute the thread https://github.com/notifications/unsubscribe-auth/AiyerxM97KUWjDYL08to3FD2ng0U5YkSks5uVpv9gaJpZM4R91yn .

[AdriftUrchin]

I should also note that when i do use moonlight i use it over wifi (not local as i'm at school duh :P) but when i'm at home i test it over a mobile connection to make sure everything works. Just thought that I should mention this I don't know if its important or not.

[redlinejoes]

If you're in your WiFi at school and not cellular then it's possible they are blocking the ports. You need to use it the same way you are testing it. That is from cell not WiFi networks

Cheers, Joe

On Wed, Aug 29, 2018, 9:56 AM Morgan notifications@github.com wrote:

I should also note that when i do use moonlight i use it over wifi (not local as im at school duh :P) but when im at home i test it over a mobile connection to make sure everything works.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/moonlight-stream/moonlight-android/issues/528#issuecomment-416962523, or mute the thread https://github.com/notifications/unsubscribe-auth/ADBhXt3JOi-aBM4rjO2l5iBQkl7q6Jjbks5uVp1wgaJpZM4R91yn .

[AdriftUrchin]

Just tested it on my mobile connection and it works but i have to have my firewall turned off.

[redlinejoes]

If a FW is blocking ports then you will have to disable the FW or a better solution is to simply open the required ports and not disable the FW entirely. All the required ports are documented.

Cheers, Joe

On Thu, Aug 30, 2018 at 8:11 AM AdriftUrchin notifications@github.com wrote:

Just tested it on my mobile connection and it works but i have to have my firewall turned off.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/moonlight-stream/moonlight-android/issues/528#issuecomment-417296982, or mute the thread https://github.com/notifications/unsubscribe-auth/ADBhXlCpHDDhpeRRiYRztEX3zOcWXAgfks5uV9ZogaJpZM4R91yn .

[AdriftUrchin]

Ok this is odd came back home enabled my FW then disabled it again to check if it still worked and im getting rtsp handshake fail yet again fml.

[cgutman]

Please try again with v5.10.3

[MagFlux]

@cgutman I can confirm it now works via AT&T. Nice work, thanks for the update!

[donkeyhigh]

I'm having a similar issue. Errorcode 10035. It's weird, because it works with 2 of my laptops on wifi and wired connections, and on my android over both wifi and cellular 4g. But my third laptop gets the error, even though it's connected with cable or wifi to the same local network. So I'm guessing it has something to do with this laptop in particular. I went to the windows run thingy and wrote firewall.cpl, added moonlight to my windows firewall whitelist, but still won't connect. Any ideas what it could be? The ports are forwarded correctly, or else it wouldn't have connected over cellular, so I'm kind of confused..

Edit : figured it out. I had only given moonlight.exe permission through my firewall when in "Private network", not Public. When I ticked off Public as well, it worked like a charm. Weird. But oh well..