search

ClassicOldSong / Apollo

Sunshine fork
GNU General Public License v3.0
520 stars 13 forks source link

Connectivity issues using Moonlight clients #55

Closed pantherale0 closed 3 weeks ago

pantherale0 commented 1 month ago

Hi,

First of all, this is a fantastic project and can see this improving big time on sunshine. I've noticed a number of weird issues though. I thought I'd log a "list" here of what I've found.

  1. Unable to initiate a connection from moonlight to apollo without using moonlight-noir first. It seems either the connection is successful, however the client is left staring at a "blank" screen, as if the virtual display is not connected. I have VNC setup which also shows a blank screen at this point.

  2. Linked to above, if I try and connect without using your Moonlight Android app, any app used (desktop, mobile) hangs at "Starting Virtual Display", nothing appears in the Apollo logs at this point and I'm yet to try and find where I can debug.

  3. Attempting to pair the desktop moonlight app with apollo while a session is in progress results in a number of weird errors, either way it never pairs. Errors are:

    • Connection timed out (Error: 4) (Most common)
    • Connection Closed
    • I've also had a HTTP 203 "error" when trying to pair without a device name. Unfortunately closed this before I had a chance to make a note of what it was.

Spec:

Networking:

Host is wired at full GbE

Most clients with this problem are hard wired into the local network via the same switch, no VLANs or anything else going on between clients. Firewall on the host is open too. Also at GbE

Only exception to this is an android tablet / smartphone I've used to initiate the session first which are wireless.

Logs:

apollo.log

s6tiger commented 1 month ago

Have you tried to allocate a permission in PIN section? Original moonlight client should show up in the device section below, try edit it and allocate a Start App permission.

pantherale0 commented 1 month ago

Yep, granted all permissions just in case but no luck

ClassicOldSong commented 1 month ago

That's weird, Apollo doesn't treat og Moonlight clients differently from Artemis. Are you really sure that the blank screen issue is tightly corresponded to type of clients?

Can you confirm this is still happening with Headless Mode enabled or have the app you're starting configured with "Always use virtual display"?

IIRC there's no http 203 return from Apollo/Sunshine, are you sure that there's no other applications/services listening to the same port?

s6tiger commented 1 month ago

the only difference of the first device is that it is granted full permissions by default while others normally only have the permission to join an existing streaming session. I would say probably a permission issue, that why I suggest you check again the PIN section. I just updated from 0.13 alpha got similar issue at first, but ok after permission granted. And permission system is a new function with recent version a good place to start to check the issue.

pantherale0 commented 1 month ago

That's weird, Apollo doesn't treat og Moonlight clients differently from Artemis. Are you really sure that the blank screen issue is tightly corresponded to type of clients?

100% and able to consistently replicate, og moonlight always ends up either not connecting at all, or connecting but resulting in a blank screen. If Artemis launches the app however, the connection from the og clients works fine.

Can you confirm this is still happening with Headless Mode enabled or have the app you're starting configured with "Always use virtual display"?

Yep, can confirm both of these. Happens in headless mode and the app is configured with always use virtual display (but I actually have a couple of clients configured to launch the "Virtual Desktop" app anyway)

IIRC there's no http 203 return from Apollo/Sunshine, are you sure that there's no other applications/services listening to the same port?

No other applications running on that port, the build itself is fairly basic, it's connected to my own domain controller but that is just to remove the Microsoft account requirements than anything else. Nothing deployed via group policy.

ClassicOldSong commented 1 month ago

According to the log, the only difference I can notice is that the first client connected has HDR enabled, and the stream was then never quit, only disconnected and reconnected.

RX480 is a bit old tbh, the oldest AMD card I can test with is a RX580 2048sp but it starts just fine, regardless of clients.

pantherale0 commented 1 month ago

According to the log, the only difference I can notice is that the first client connected has HDR enabled, and the stream was then never quit, only disconnected and reconnected.

Yes, this is right, first client is the Artemis client, second client is moonlight embedded (no HDR on the monitor)

RX480 is a bit old tbh, the oldest AMD card I can test with is a RX580 2048sp but it starts just fine, regardless of clients.

Yeah, it's a old card thats for sure, I've had it for years but with the system it's in there is no point buying a more modern card because the CPU will then become the bottleneck. I don't play PC games enough to justify a whole new build. The 480 and 580 are nearly identical. 580 pretty much just has a factory overclock on it.

pantherale0 commented 1 month ago

Some logs from the desktop client:

jordan@fedora:~$ flatpak run com.moonlight_stream.Moonlight
00:00:00 - SDL Info (0): Compiled with SDL 2.31.0
00:00:00 - SDL Info (0): Running with SDL 2.31.0
00:00:00 - Qt Info: No translation available for "en_GB"
00:00:00 - SDL Info (0): Detected Wayland
00:00:00 - Qt Warning: QGuiApplication::setDesktopFileName: the specified desktop file name ends with .desktop. For compatibility reasons, the .desktop suffix will be removed. Please specify a desktop file name without .desktop suffix
00:00:00 - Qt Warning: qrc:/gui/main.qml:13:1: QML ApplicationWindow: ToolTip must be attached to an Item
00:00:00 - Qt Info: Found "gamecontrollerdb.txt" at "/home/jordan/.var/app/com.moonlight_stream.Moonlight/cache/Moonlight Game Streaming Project/Moonlight/gamecontrollerdb.txt"
00:00:00 - SDL Info (0): Loaded 337 new gamepad mappings
00:00:00 - SDL Info (0): V-sync disabled
libva info: VA-API version 1.19.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/intel-vaapi-driver/radeonsi_drv_video.so
libva info: Trying to open /usr/lib/x86_64-linux-gnu/GL/lib/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_19
libva info: va_openDriver() returns 0
00:00:00 - SDL Info (0): Initialized VAAPI 1.19
00:00:00 - SDL Info (0): Driver: Mesa Gallium driver 24.2.1 for AMD Radeon Graphics (radeonsi, renoir, LLVM 17.0.6, DRM 3.57, 6.10.10-200.fc40.x86_64)
00:00:00 - FFmpeg: [AVHWDeviceContext @ 0x7f857400b940] Format 0x3231564e -> nv12.
00:00:00 - FFmpeg: [AVHWDeviceContext @ 0x7f857400b940] Format 0x30313050 -> p010le.
00:00:00 - FFmpeg: [AVHWDeviceContext @ 0x7f857400b940] Format 0x36313050 -> unknown.
00:00:00 - FFmpeg: [AVHWDeviceContext @ 0x7f857400b940] Format 0x30323449 -> yuv420p.
00:00:00 - FFmpeg: [AVHWDeviceContext @ 0x7f857400b940] Format 0x32315659 -> yuv420p.
00:00:00 - FFmpeg: [AVHWDeviceContext @ 0x7f857400b940] Format 0x56595559 -> unknown.
00:00:00 - FFmpeg: [AVHWDeviceContext @ 0x7f857400b940] Format 0x32595559 -> yuyv422.
00:00:00 - FFmpeg: [AVHWDeviceContext @ 0x7f857400b940] Format 0x59565955 -> uyvy422.
00:00:00 - FFmpeg: [AVHWDeviceContext @ 0x7f857400b940] Format 0x30303859 -> gray.
00:00:00 - FFmpeg: [AVHWDeviceContext @ 0x7f857400b940] Format 0x50343434 -> yuv444p.
00:00:00 - FFmpeg: [AVHWDeviceContext @ 0x7f857400b940] Format 0x56323234 -> yuv440p.
00:00:00 - FFmpeg: [AVHWDeviceContext @ 0x7f857400b940] Format 0x50424752 -> unknown.
00:00:00 - FFmpeg: [AVHWDeviceContext @ 0x7f857400b940] Format 0x41524742 -> bgra.
00:00:00 - FFmpeg: [AVHWDeviceContext @ 0x7f857400b940] Format 0x41424752 -> rgba.
00:00:00 - FFmpeg: [AVHWDeviceContext @ 0x7f857400b940] Format 0x42475241 -> argb.
00:00:00 - FFmpeg: [AVHWDeviceContext @ 0x7f857400b940] Format 0x58524742 -> bgr0.
00:00:00 - FFmpeg: [AVHWDeviceContext @ 0x7f857400b940] Format 0x58424752 -> rgb0.
00:00:00 - FFmpeg: [AVHWDeviceContext @ 0x7f857400b940] Format 0x30335241 -> unknown.
00:00:00 - FFmpeg: [AVHWDeviceContext @ 0x7f857400b940] Format 0x30334241 -> unknown.
00:00:00 - FFmpeg: [AVHWDeviceContext @ 0x7f857400b940] Format 0x30335258 -> x2rgb10le.
00:00:00 - FFmpeg: [AVHWDeviceContext @ 0x7f857400b940] Format 0x30334258 -> unknown.
00:00:00 - FFmpeg: [AVHWDeviceContext @ 0x7f857400b940] VAAPI driver: Mesa Gallium driver 24.2.1 for AMD Radeon Graphics (radeonsi, renoir, LLVM 17.0.6, DRM 3.57, 6.10.10-200.fc40.x86_64).
00:00:00 - FFmpeg: [AVHWDeviceContext @ 0x7f857400b940] Driver not found in known nonstandard list, using standard behaviour.
00:00:00 - SDL Info (0): Selected overlay subpicture format: BGRA8888
00:00:00 - SDL Warn (0): Vulkan device 'AMD Radeon Graphics (RADV RENOIR)' does not support HDR10 (ST.2084 PQ)
00:00:00 - SDL Warn (0): Vulkan device 'llvmpipe (LLVM 17.0.6, 256 bits)' does not support HDR10 (ST.2084 PQ)
00:00:00 - SDL Error (0): No suitable HDR-capable Vulkan devices found!
00:00:00 - SDL Info (0): Vulkan rendering device chosen: AMD Radeon Graphics (RADV RENOIR)
00:00:00 - SDL Info (0): Using Immediate present mode with V-Sync disabled
00:00:00 - SDL Info (0): Using VAAPI accelerated renderer on wayland
00:00:00 - FFmpeg: [hevc @ 0x7f857412c280] nal_unit_type: 32(VPS), nuh_layer_id: 0, temporal_id: 0
00:00:00 - FFmpeg: [hevc @ 0x7f857412c280] nal_unit_type: 33(SPS), nuh_layer_id: 0, temporal_id: 0
00:00:00 - FFmpeg: [hevc @ 0x7f857412c280] nal_unit_type: 34(PPS), nuh_layer_id: 0, temporal_id: 0
00:00:00 - FFmpeg: [hevc @ 0x7f857412c280] nal_unit_type: 21(CRA_NUT), nuh_layer_id: 0, temporal_id: 0
00:00:00 - FFmpeg: [hevc @ 0x7f857412c280] nal_unit_type: 21(CRA_NUT), nuh_layer_id: 0, temporal_id: 0
00:00:00 - FFmpeg: [hevc @ 0x7f857412c280] nal_unit_type: 21(CRA_NUT), nuh_layer_id: 0, temporal_id: 0
00:00:00 - FFmpeg: [hevc @ 0x7f857412c280] nal_unit_type: 21(CRA_NUT), nuh_layer_id: 0, temporal_id: 0
00:00:00 - FFmpeg: [hevc @ 0x7f857412c280] Decoding VPS
00:00:00 - FFmpeg: [hevc @ 0x7f857412c280] Main 10 profile bitstream
00:00:00 - FFmpeg: [hevc @ 0x7f857412c280] Decoding SPS
00:00:00 - FFmpeg: [hevc @ 0x7f857412c280] Main 10 profile bitstream
00:00:00 - FFmpeg: [hevc @ 0x7f857412c280] Decoding VUI
00:00:00 - FFmpeg: [hevc @ 0x7f857412c280] Decoding PPS
00:00:00 - FFmpeg: [hevc @ 0x7f857412c280] Format vaapi chosen by get_format().
00:00:00 - FFmpeg: [hevc @ 0x7f857412c280] Format vaapi requires hwaccel hevc_vaapi initialisation.
00:00:00 - FFmpeg: [hevc @ 0x7f857412c280] Considering format 0x3231564e -> nv12.
00:00:00 - FFmpeg: [hevc @ 0x7f857412c280] Considering format 0x30313050 -> p010le.
00:00:00 - FFmpeg: [hevc @ 0x7f857412c280] Ignoring unknown format 0x36313050.
00:00:00 - FFmpeg: [hevc @ 0x7f857412c280] Picked p010le (0x30313050) as best match for yuv420p10le.
00:00:00 - FFmpeg: [AVHWFramesContext @ 0x7f857478d6c0] Created surface 0x1.
00:00:00 - FFmpeg: [AVHWFramesContext @ 0x7f857478d6c0] Direct mapping possible.
00:00:00 - FFmpeg: [AVHWFramesContext @ 0x7f857478d6c0] Created surface 0x2.
00:00:00 - FFmpeg: [AVHWFramesContext @ 0x7f857478d6c0] Created surface 0x3.
00:00:00 - FFmpeg: [AVHWFramesContext @ 0x7f857478d6c0] Created surface 0x4.
00:00:00 - FFmpeg: [AVHWFramesContext @ 0x7f857478d6c0] Created surface 0x5.
00:00:00 - FFmpeg: [AVHWFramesContext @ 0x7f857478d6c0] Created surface 0x6.
00:00:00 - FFmpeg: [AVHWFramesContext @ 0x7f857478d6c0] Created surface 0x7.
00:00:00 - FFmpeg: [AVHWFramesContext @ 0x7f857478d6c0] Created surface 0x8.
00:00:00 - FFmpeg: [AVHWFramesContext @ 0x7f857478d6c0] Created surface 0x9.
00:00:00 - FFmpeg: [AVHWFramesContext @ 0x7f857478d6c0] Created surface 0xa.
00:00:00 - FFmpeg: [AVHWFramesContext @ 0x7f857478d6c0] Created surface 0xb.
00:00:00 - FFmpeg: [AVHWFramesContext @ 0x7f857478d6c0] Created surface 0xc.
00:00:00 - FFmpeg: [AVHWFramesContext @ 0x7f857478d6c0] Created surface 0xd.
00:00:00 - FFmpeg: [AVHWFramesContext @ 0x7f857478d6c0] Created surface 0xe.
00:00:00 - FFmpeg: [AVHWFramesContext @ 0x7f857478d6c0] Created surface 0xf.
00:00:00 - FFmpeg: [AVHWFramesContext @ 0x7f857478d6c0] Created surface 0x10.
00:00:00 - FFmpeg: [AVHWFramesContext @ 0x7f857478d6c0] Created surface 0x11.
00:00:00 - FFmpeg: [AVHWFramesContext @ 0x7f857478d6c0] Created surface 0x12.
00:00:00 - FFmpeg: [AVHWFramesContext @ 0x7f857478d6c0] Created surface 0x13.
00:00:00 - FFmpeg: [AVHWFramesContext @ 0x7f857478d6c0] Created surface 0x14.
00:00:00 - FFmpeg: [hevc @ 0x7f857412c280] Decode context initialised: 0x15/0x16.
00:00:00 - FFmpeg: [hevc @ 0x7f857412c280] Output frame with POC 3.
00:00:00 - FFmpeg: [hevc @ 0x7f857412c280] Param buffer (type 0, 604 bytes) is 0x17.
00:00:00 - FFmpeg: [hevc @ 0x7f857412c280] Slice 0 param buffer (264 bytes) is 0x18.
00:00:00 - FFmpeg: [hevc @ 0x7f857412c280] Slice 0 data buffer (77 bytes) is 0x19.
00:00:00 - FFmpeg: [hevc @ 0x7f857412c280] Slice 1 param buffer (264 bytes) is 0x1a.
00:00:00 - FFmpeg: [hevc @ 0x7f857412c280] Slice 1 data buffer (87 bytes) is 0x1b.
00:00:00 - FFmpeg: [hevc @ 0x7f857412c280] Slice 2 param buffer (264 bytes) is 0x1c.
00:00:00 - FFmpeg: [hevc @ 0x7f857412c280] Slice 2 data buffer (96 bytes) is 0x1d.
00:00:00 - FFmpeg: [hevc @ 0x7f857412c280] Slice 3 param buffer (264 bytes) is 0x1e.
00:00:00 - FFmpeg: [hevc @ 0x7f857412c280] Slice 3 data buffer (77 bytes) is 0x1f.
00:00:00 - FFmpeg: [hevc @ 0x7f857412c280] Decode to surface 0x14.
00:00:00 - SDL Info (0): FFmpeg-based video decoder chosen
00:00:00 - Qt Info: Found "gamecontrollerdb.txt" at "/home/jordan/.var/app/com.moonlight_stream.Moonlight/cache/Moonlight Game Streaming Project/Moonlight/gamecontrollerdb.txt"
00:00:00 - SDL Info (0): Loaded 337 new gamepad mappings
00:00:00 - Qt Debug: Current Moonlight version: "6.0.1"
00:00:00 - Qt Info: Gamepad mappings are up to date
00:00:00 - Qt Info: Latest supported GFE server: "99.99.99.99"
00:00:00 - Qt Info: "GAMES" is now online at "10.10.50.54:47989"
00:00:00 - Qt Info: Discovered mDNS host: "DZ7QW02.local."
00:00:00 - Qt Info: Resolved "DZ7QW02.local." to QHostAddress("10.10.50.54")
00:00:02 - Qt Info: Processing new PC at "10.10.50.54:47989" from mDNS with IPv6 address "[2a01:4b00:bc1b:be00::1e17]:47989"
00:00:02 - Qt Info: Executing request: "http://10.10.50.54:47989/serverinfo?uniqueid=0123456789ABCDEF&uuid=2e7c2f85c7d64e77a9401f8422bef0c7"
00:00:02 - Qt Info: Executing request: "https://10.10.50.54:47984/serverinfo?uniqueid=0123456789ABCDEF&uuid=255777eb72e442ed9b157a8f963f11c6"
00:00:02 - Qt Info: Executing request: "http://10.10.50.54:47989/serverinfo?uniqueid=0123456789ABCDEF&uuid=fca85ed81139451f98b0aebca060c9b0"
00:00:06 - Qt Info: Pairing with server generation: 7
00:00:06 - Qt Info: Executing request: "http://10.10.50.54:47989/pair?uniqueid=0123456789ABCDEF&uuid=4f44d9bcb3d14c8aac7556a9099b3a7c&devicename=roth&updateState=1&phrase=getservercert&salt=c11ad5c2cbe316f9bba753e19df2a4f5&clientcert=2d2d2d2d2d424547494e2043455254494649434154452d2d2d2d2d0a4d494943767a43434161656741774942416749424144414e42676b71686b694739773042415173464144416a4d53457748775944565151444442684f566b6c450a53554567523246745a564e30636d56686253424462476c6c626e51774868634e4d6a4d784d6a49354d5467304d544d7a5768634e4e444d784d6a49304d5467300a4d544d7a576a416a4d53457748775944565151444442684f566b6c4553554567523246745a564e30636d56686253424462476c6c626e5177676745694d4130470a4353714753496233445145424151554141344942447741776767454b416f4942415144494b724e534e5a6b6f39622f444250484f4e474257654b6a7046352b650a494a39302f777a526434615343507277596e71645652796f757a507753682f35572b58616579414f43506d706a704c72694f4839374d53554376627169714b590a33785854413649797968763445754a69362f7933574e6770667065304f30476f7964476e76384159794d6338353949784b5136326b7466753663456c416264320a62326e6d523755797774475a7463526c6b584b716e71654b455439512b4f6b32415556716d32392b376e71397456567a616a3767446f782f43597834757066480a4c732b6b366938306d48304575457059646b424f5774426d734a786463664562574e3475674d50466a44336752493463576f456468356f514e764a773751464b0a59654733535664385552364b673150316b6a75646542525a6764494475706742694649446452386a576e445077763933312f7a7a492b4a4a41674d42414145770a4451594a4b6f5a496876634e4151454c425141446767454241432b6774777264676648397a52716c78757375766e7451623745535a324c306e6c2b35637642730a4e637278742f43326d2f6f4179747a72776b7150416346507a55567438646f7967692f423373446252324446796d516c63467065596d4c5976596f69385963370a556b737a4274533672594a7671422b42556c556f6a53737162525841463973523965416a567777354d723573714b44674143694271787a67554f74674b444e570a7a465a55794b3249484242635875326a71612f46746a45354f7851482b69636a5a4868672f7564616f573366524e36565336763542526f73675252364c7537300a50754a463478584a774477323046613271714f4859506557457a734a6f63573844504d576c4e542f4b4c424359684e6a514a55573361395870567059384d67670a6b4865434439506b3745414457444f2f7163476471467a6a2b6838546a387654466f6e4d2b786b7a655a75327963383d0a2d2d2d2d2d454e442043455254494649434154452d2d2d2d2d0a"
00:00:12 - Qt Info: Executing request: "http://10.10.50.54:47989/pair?uniqueid=0123456789ABCDEF&uuid=aaa21aaf0b304da187988c9f95ad7f35&devicename=roth&updateState=1&clientchallenge=a900bb1e4718fc72bcc57f6cc5169101"
00:00:12 - Qt Info: Executing request: "http://10.10.50.54:47989/pair?uniqueid=0123456789ABCDEF&uuid=bdb63aba3b8e4d6e897aed57ff068dac&devicename=roth&updateState=1&serverchallengeresp=42f63eabf94c624091d06e950ebb3ea3a077f335106cbaa8cba3146efb62eb9b"
00:00:12 - Qt Info: Executing request: "http://10.10.50.54:47989/pair?uniqueid=0123456789ABCDEF&uuid=06a04cc52c3948f1ad5bad5176c9d293&devicename=roth&updateState=1&clientpairingsecret=5dc4f9f10430ddd584fe966b7f69e6498631cd6d51fd52df6611db39e7ca497504e680c3ee827e77b4f25c5ac4cd3c3d656f050d8711cfdc575f4f52e2aada859a830237c3ef2aaccfd3ec930b26ab26cea89a3f35fca51a7148eb7b0e7a6379d6c1047bd2a6730a0a6fafed39c47d84fda1ff3f48d0cd4a0d2f3c86eef9ed0cd81f1e048ffeff8ef82ca2f30a589b159968e62e04a93d17a9064f445162e1e346d13800b88678827b115de56aa4c0b039db6d73078bf36b9c411b45016002265bdd471eabc070f38243dd2f89ff461332c3deaac6af212e3902419c916df5ee982aacbe20a2d33c7616b2843e4f111b3de0fdbb29b374aa9374a629e255b2468a44763fddb1b2aafe91b2ba7cee344b"
00:00:12 - Qt Info: Executing request: "https://10.10.50.54:47984/pair?uniqueid=0123456789ABCDEF&uuid=8196852c85a949ed9bd7cbd62ff6af93&devicename=roth&updateState=1&phrase=pairchallenge"
00:00:22 - Qt Info: Found "ModeSeven.ttf" at ":/data/ModeSeven.ttf"
00:00:22 - Qt Info: Server GPU: ""
00:00:22 - Qt Info: Server GFE version: "3.23.0.74"
00:00:22 - SDL Info (0): Video bitrate: 20000 kbps
00:00:22 - SDL Info (0): Desired audio buffer: 720 samples (2880 bytes)
00:00:22 - SDL Info (0): Obtained audio buffer: 720 samples (2880 bytes)
00:00:22 - SDL Info (0): SDL audio driver: pulseaudio
^C

The ctrl+C is where I've forced the client to end after a couple of minutes of Starting <insert app here>... Like below:

image

Nothing entered into the server side logs. Although it does appear that when a client does connect, a service seems to restart as you can see by the logs below:

00:01:10 - Qt Info: "GAMES" is now offline
00:01:13 - Qt Info: "GAMES" is now online at "10.10.50.54:47989"

I have spotted this in the Windows Event Viewer:

Faulting application name: Sunshine.exe, version: 0.0.0.0, time stamp: 0x66f7266d
Faulting module name: Sunshine.exe, version: 0.0.0.0, time stamp: 0x66f7266d
Exception code: 0xc0000005
Fault offset: 0x000000000191c2fd
Faulting process id: 0x0x4704
Faulting application start time: 0x0x1DB129CE57542B9
Faulting application path: C:\Program Files\Apollo\Sunshine.exe
Faulting module path: C:\Program Files\Apollo\Sunshine.exe
Report Id: 833a34f6-2e65-4786-8510-86e4c1ccfdc3
Faulting package full name: 
Faulting package-relative application ID:

image

ClassicOldSong commented 1 month ago

Tired back and forth, totally no issue launching and pairing from a Windows Qt client, and iOS clients, Moonlight Switch client...

Is your installation clean or migrated from Sunshine? Can you try removing the credentials, sunshine.conf, apps.json and sunshine_state.json from your install location to start over and try again?

ClassicOldSong commented 1 month ago

Another possibility, could you try disabling IPv6 and see if it works?

ClassicOldSong commented 1 month ago

Any updates?

pantherale0 commented 1 month ago

Computer hasn't been on for a couple of days sorry. I'll try disabling IPv6 because I have no firewall rules configured on the router for v6 which could be causing an issue (but it shouldn't be with all devices on the same local LAN/subnet).

This is a completely clean install. I opted to not migrate Sunshine config and start a fresh when switching over.

ClassicOldSong commented 1 month ago

Any updates?

ClassicOldSong commented 3 weeks ago

As this is very likely to be an user specific environment issue that is impossible to debug remotely, and no other people are reporting similar issues, I'm closing this issue for now.