control stream establishment error 2

rngunknown commented 5 months ago

Hi all! Version 6.0 does not want to connect, control stream establishment error 2 Check your firewall and port forwarding settings for the following ports: UDP 47999 But I run it on a local network, all ports are open on the Sunshine server.

My latest working version is 5.0.0, everything works on it. 123

log: 2024:06:06:18:03:39: Info: Encoder reenumeration is required 2024:06:06:18:03:39: Info: // Testing for available encoders, this may generate errors. You can safely ignore those errors. // 2024:06:06:18:03:39: Info: Trying encoder [nvenc]

Device Description : NVIDIA GeForce RTX 3060 Device Vendor ID : 0x000010DE Device Device ID : 0x00002504 Device Video Mem : 12115 MiB Device Sys Mem : 0 MiB Share Sys Mem : 8172 MiB Feature Level : 0x0000B100 Capture size : 1920x1080 Offset : 0x0 Virtual Desktop : 1920x1080 2024:06:06:18:03:39: Info: Active GPU has HAGS disabled 2024:06:06:18:03:39: Info: Using realtime GPU priority 2024:06:06:18:03:39: Info: Desktop resolution 1920x1080: Info: Desktop format DXGI_FORMAT_B8G8R8A8_UNORM: Info: Display refresh rate 144Hz: Info: Requested frame rate [60fps]

Colorspace : DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709 Bits Per Color : 8 Red Primary : [0.639648,0.330078] Green Primary : [0.299805,0.599609] Blue Primary : [0.149414,0.0595703] White Point : [0.3125,0.329102] Min Luminance : 0.5 nits Max Luminance : 270 nits Max Full Luminance : 270 nits 2024:06:06:18:03:39: Info: SDR color coding Rec. 601: Info: Color depth: 8-bit 2024:06:06:18:03:39: Info: Color range: JPEG: Info: NvEnc: created encoder P1 two-pass rfi 2024:06:06:18:03:39: Info: SDR color coding Rec. 601: Info: Color depth: 8-bit 2024:06:06:18:03:39: Info: Color range: JPEG: Info: NvEnc: created encoder P1 two-pass rfi 2024:06:06:18:03:39: Info: SDR color coding Rec. 601: Info: Color depth: 8-bit 2024:06:06:18:03:39: Info: Color range: JPEG: Error: NvEnc: encoding format is not supported by the gpu

Device Description : NVIDIA GeForce RTX 3060 Device Vendor ID : 0x000010DE Device Device ID : 0x00002504 Device Video Mem : 12115 MiB Device Sys Mem : 0 MiB Share Sys Mem : 8172 MiB Feature Level : 0x0000B100 Capture size : 1920x1080 Offset : 0x0 Virtual Desktop : 1920x1080 2024:06:06:18:03:40: Info: Active GPU has HAGS disabled 2024:06:06:18:03:40: Info: Using realtime GPU priority 2024:06:06:18:03:40: Info: Desktop resolution 1920x1080: Info: Desktop format DXGI_FORMAT_B8G8R8A8_UNORM: Info: Display refresh rate 144Hz: Info: Requested frame rate [60fps]

Colorspace : DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709 Bits Per Color : 8 Red Primary : [0.639648,0.330078] Green Primary : [0.299805,0.599609] Blue Primary : [0.149414,0.0595703] White Point : [0.3125,0.329102] Min Luminance : 0.5 nits Max Luminance : 270 nits Max Full Luminance : 270 nits 2024:06:06:18:03:40: Info: SDR color coding Rec. 709: Info: Color depth: 10-bit 2024:06:06:18:03:40: Info: Color range: JPEG: Info: NvEnc: created encoder P1 10-bit two-pass rfi

2024:06:06:18:03:40: Info: // Ignore any errors mentioned above, they are not relevant. //

2024:06:06:18:03:40: Info: Found H.264 encoder: h264_nvenc nvenc: Info: Found HEVC encoder: hevc_nvenc nvenc: Info: Executing [Desktop] [2024:06:06:18:03:41]: Info: nvprefs: No need to modify application profile settings [2024:06:06:18:03:41]: Info: nvprefs: No need to modify global profile settings

cgutman commented 5 months ago

Please post logs from Moonlight after the error occurs:

On Windows, Moonlight-###.log files can be found in %TEMP%. Simply type that into the File Explorer path field to navigate there.
On macOS, Moonlight-###.log files can be found in /tmp. In Finder, press Cmd+Shift+G, then type /tmp to navigate there.
On Linux with the Flatpak, logs print to the terminal when running with the command: flatpak run com.moonlight_stream.Moonlight

rngunknown commented 5 months ago

Moonlight-1717971270.log okey, here is the log file

rngunknown commented 5 months ago

Moonlight-1717971891.log for comparison, the log from version 5.0.0, on which everything works

cgutman commented 5 months ago

There seems to be something quite strange about your network configuration on the client PC, and I suspect that's what's breaking Moonlight.

For example:

00:00:07 - Qt Info: Found matching interface: "Loopback Pseudo-Interface 1" "" QFlags<QNetworkInterface::InterfaceFlag>(IsUp|IsRunning|CanBroadcast|IsLoopBack|CanMulticast)
00:00:07 - Qt Info: Interface Type: QNetworkInterface::Loopback

It seems to think that your host PC is accessible over the loopback interface, which doesn't make any sense. I wonder if you somehow have 2 network interfaces with the same IP address and Windows is binding the wrong one. Can you open ncpa.cpl and post a screenshot of your network connections shown there?

You posted logs from v6.0.0 and v5.0.0, but v5.0.1 was the previous release. Did v5.0.1 also not work?

rngunknown commented 5 months ago

ncpa here screenshot ncpa, OpenVPN is a working interface, it does not belong to the local network.

yes, 5.0.1 didn’t work either.

rngunknown commented 5 months ago

ips here is ips

rngunknown commented 4 months ago

Nothing has changed in 6.0.1, it still won’t connect((

Legachin commented 1 week ago

Nothing has changed in 6.0.1, it still won’t connect((

In my case this error was caused by antivirus, adding moonlight to exceptions without checking network traffic helped, maybe it will help someone.

rngunknown commented 6 days ago

Nothing has changed in 6.0.1, it still won’t connect((

In my case this error was caused by antivirus, adding moonlight to exceptions without checking network traffic helped, maybe it will help someone.

no, this not working

moonlight-stream / moonlight-qt

control stream establishment error 2 #1300