New Windows/GFE update breaks Moonlight? (RTSP: Failed to connect to UDP port 48010)

[Trinity92]

NVidia Geforce Experience version: 3.12.0.79
Moonlight Embedded version: 2.4.4
Moonlight Embedded source: included in Raspbian's package manager
Moonlight Embedded running on: Raspberry Pi 3
Moonlight Embedded running on distribution: Raspbian

Verbose output -verbose of Moonlight Embedded:
pi@raspberrypi:~ $ moonlight stream -1080 -fps 60 -app "Steam" -platform pi -verbose
Moonlight Embedded 2.4.4 (EMBEDDED;ALSA;PI)
Searching for server...
Connect to 192.168.178.104...
NVIDIA GeForce GTX 750 Ti, GFE 3.12.0.79 (gs_04_04_23287129, 7.1.404.0)
Platform Raspberry Pi (Broadcom)
Loading mappingfile /usr/share/moonlight/gamecontrollerdb.txt
Detected Logitech Logitech Dual Action (030000006d04000016c2000010010000) on /dev/input/event0 as Logitech Dual Action
Mapping for Logitech Logitech Dual Action (030000006d04000016c2000010010000) on /dev/input/event0 is incorrect
Stream 1920 x 1080, 60 fps, 20000 kbps
Initializing platform...done
Resolving host name...done
Starting RTSP handshake...RTSP: Failed to connect to UDP port 48010
failed: -1
Cleaning up platform...done
^Cpi@raspberrypi:~ $

What is the expected result?
I would like to stream my desktop PC Steam library to my Raspberry Pi 3 through Moonlight.

What happens instead of that?
Following a Windows 8.1 and Nvidia GFE update, Moonlight now hangs up at the "Cleaning up platform...done" line and I have to kill it manually with Ctrl+C. The game footage is not streamed to the Raspberry Pi 3 as a result, although I can still see the game's video on my host PC's screen (I can't hear any audio from either device though). The newest version of the Android Moonlight app also ceased working with my setup for the exact same reasons.

The weird thing is that it used to work before (even yesterday afternoon!) on the exact same setup and now, after updating Windows and Nvidia GFE to the newest versions, it suddenly stopped working and always gives me that error.
I followed the troubleshooting guide and tried disabling the Firewall or adding an exception, re-installing Nvidia GFE, but none of these solutions worked. Keep in mind that I am running Moonlight in my local network over a switch, so no port forwarding necessary (even though the ports are in fact forwarded correctly on my router, but that may not be relevant for this issue).

I may try to re-install Moonlight altogether and see if it works, altough I doubt that it might solve the issue. IMO, this could be due to the new updates for GFE and Windows 8.1 somehow breaking the current Moonlight implementations... or perhaps I am overlooking something? Anyone else having this same issue?

[goli333]

Same issue with new Windows 7 and GFE update... Tried Hamachi, port fowarding and reinstalling but none of them helped.

[cgutman]

Yes, I have pushed fixes to the moonlight-common-c repository. Once @irtimmer integrates these changes, it will work again.

[Trinity92]

Thank you very much for your quick fix! I will test it as soon as it has been integrated.

[davidoneacre]

Can confirm, got the exact same error after updating GFE on Windows 10. Downgraded to GFE 3.10.0.95 and everything works again.

[irtimmer]

The required changes for GFE 3.12 in moonlight-common-c are now integrated into the new release 2.4.5

[Silent-Hunter]

This seems to be happening again. I'm using Debian 9, moonlight-embedded 2.4.6, and GFE 3.12.0.84.
It might be my computer though, Dukto, a local network file sharing app is also not working. But I can't begin to imagine what the issue could be.

[Meems33]

edit Works on master dcda1a5. I got 2.4.6 working after uninstalling and then reinstalling.

Similar to moonlight-stream/moonlight-android#528, avtoneru/moonlight-SBS#1.

It also happens over LAN. GFE 3.13.1.30 moonlight-embedded 2.4.6 on debian pi 3. All relevant ports should be open.

Wireshark packet capture (for moonlight-embedded):
Incoming from pi UDP 48010 52 data bytes. There are 5 packets (retries maybe?):

0000 8f ff 14 1e 82 ff 00 01 00 00 ff ff 00 00 05 78
0010 00 01 00 00 00 00 00 01 00 00 00 00 00 00 00 00
0020 00 00 13 88 00 00 00 02 00 00 00 02 52 5c ab 1e
0030 00 00 00 00

0000 8f ff 16 12 82 ff 00 01 00 00 ff ff 00 00 05 78
0010 00 01 00 00 00 00 00 01 00 00 00 00 00 00 00 00
0020 00 00 13 88 00 00 00 02 00 00 00 02 52 5c ab 1e
0030 00 00 00 00

0000 8f ff 19 fc 82 ff 00 01 00 00 ff ff 00 00 05 78
0010 00 01 00 00 00 00 00 01 00 00 00 00 00 00 00 00
0020 00 00 13 88 00 00 00 02 00 00 00 02 52 5c ab 1e
0030 00 00 00 00

0000 8f ff 21 ce 82 ff 00 01 00 00 ff ff 00 00 05 78
0010 00 01 00 00 00 00 00 01 00 00 00 00 00 00 00 00
0020 00 00 13 88 00 00 00 02 00 00 00 02 52 5c ab 1e
0030 00 00 00 00

0000 8f ff 31 74 82 ff 00 01 00 00 ff ff 00 00 05 78
0010 00 01 00 00 00 00 00 01 00 00 00 00 00 00 00 00
0020 00 00 13 88 00 00 00 02 00 00 00 02 52 5c ab 1e
0030 00 00 00 00

PC does not send back any data. It does however enter big screen mode in steam.

edit Works on master dcda1a5. Was the 2.4.6 build missing something?

[Meems33]

I redact my statement. After uninstalling and reinstalling moonlight-embedded it works.

[cgutman]

Maybe stale .so libraries that the DEB didn't overwrite?

[Meems33]

I suspect that is the case. Either the uninstall + reinstall fixed it or the make install from master fixed it.

[Alevale]

I can confirm that 3.13 has a similar issue as this (wouldn't let me actually stream the game even locally) but 3.14 fixes the issue in which the computer is not online