LizardByte
Cannot access the WebUI or use Moonlight to connect in the Windows 24H2 version
Is there an existing issue for this?
- [X] I have searched the existing issues
Is your issue described in the documentation?
- [X] I have read the documentation
Is your issue present in the latest beta/pre-release?
This issue is present in the latest pre-release
Describe the Bug
I updated the Windows build to 24H2 yesterday, and I find that my PC with Sunshine server installed became offline when I try to connect it through Moonlight client on my Android phone. So I back to PC side to check the status of Sunshine server (ver. 0.23.1), however, I can't access the Web UI, specificly, the address https://localhost:47990/ are loading and show a blank page forever, i.e. the screenshot shown below.
Even after rebooting, re-installing ver 0.23.1, or installing the pre-release version ([v2024.629.13903] https://github.com/LizardByte/Sunshine/releases/tag/v2024.629.13903)), the problem presents.
Expected Behavior
No response
Additional Context
No response
Host Operating System
Windows
Operating System Version
Windows 11 Pro for Workstation, 24H2, Build 26100.1000
Architecture
64 bit
Sunshine commit or version
0.23.1
Package
Windows - installer
GPU Type
Nvidia
GPU Model
RTX 4090
GPU Driver/Mesa Version
556.12
Capture Method
None
Config
fps = [10,30,60,90,120,144,180]
nvenc_preset = 7
nvenc_twopass = full_res
resolutions = [
352x240,
480x360,
858x480,
1280x720,
1920x1080,
2560x1080,
3440x1440,
1920x1200,
3840x2160,
3840x1600,
2560x1440,
3200x1440
]
upnp = enabled
origin_web_ui_allowed = wan
qsv_preset = slowest
sw_preset = veryslow
address_family = both
hevc_mode = 3
av1_mode = 3
qsv_coder = cabac
qp = 0
locale = zh
Apps
{
"env": {
"PATH": "$(PATH);$(ProgramFiles(x86))\\Steam"
},
"apps": [
{
"name": "Desktop",
"image-path": "desktop.png"
},
{
"name": "Steam Big Picture",
"detached": [
"steam steam://open/bigpicture"
],
"image-path": "steam.png"
}
]
}
Relevant log output
[2024:07:02:12:02:00]: Info: Sunshine version: v2024.629.13903
[2024:07:02:12:02:01]: Info: nvprefs: No need to modify application profile settings
[2024:07:02:12:02:01]: Info: nvprefs: Changed OGL_CPL_PREFER_DXPRESENT to OGL_CPL_PREFER_DXPRESENT_PREFER_ENABLED for base profile
[2024:07:02:12:02:01]: Info: Compiling shaders...
[2024:07:02:12:02:01]: Info: System tray created
[2024:07:02:12:02:01]: Info: Compiled shaders
[2024:07:02:12:02:01]: Warning: Gamepad x360 is disabled due to gamepads.vigem-not-available
[2024:07:02:12:02:01]: Warning: Gamepad ds4 is disabled due to gamepads.vigem-not-available
[2024:07:02:12:02:01]: Warning: No gamepad input is available
[2024:07:02:12:02:01]: Info: // Testing for available encoders, this may generate errors. You can safely ignore those errors. //
[2024:07:02:12:02:01]: Info: Trying encoder [nvenc]
[2024:07:02:12:02:01]: Info: ddprobe.exe [1] [] returned: 0x00000000
[2024:07:02:12:02:01]: Info: Set GPU preference: 1
[2024:07:02:12:02:01]: Info:
Device Description : NVIDIA GeForce RTX 4090
Device Vendor ID : 0x000010DE
Device Device ID : 0x00002684
Device Video Mem : 22612 MiB
Device Sys Mem : 0 MiB
Share Sys Mem : 32674 MiB
Feature Level : 0x0000B100
Capture size : 2560x1440
Offset : 0x0
Virtual Desktop : 2560x1440
[2024:07:02:12:02:01]: Info: Active GPU has HAGS enabled
[2024:07:02:12:02:01]: Info: Using realtime GPU priority
[2024:07:02:12:02:01]: Info:
Colorspace : DXGI_COLOR_SPACE_RGB_FULL_G2084_NONE_P2020
Bits Per Color : 10
Red Primary : [0.685547,0.308594]
Green Primary : [0.264648,0.667969]
Blue Primary : [0.150391,0.0576172]
White Point : [0.313477,0.329102]
Min Luminance : 0.3915 nits
Max Luminance : 408.76 nits
Max Full Luminance : 408.76 nits
[2024:07:02:12:02:01]: Info: Desktop resolution [2560x1440]
[2024:07:02:12:02:01]: Info: Desktop format [DXGI_FORMAT_R16G16B16A16_FLOAT]
[2024:07:02:12:02:01]: Info: Display refresh rate [179.96Hz]
[2024:07:02:12:02:01]: Info: Requested frame rate [60fps]
[2024:07:02:12:02:01]: Info: SDR color coding [Rec. 601]
[2024:07:02:12:02:01]: Info: Color depth: 8-bit
[2024:07:02:12:02:01]: Info: Color range: [JPEG]
[2024:07:02:12:02:01]: Info: NvEnc: created encoder P7 two-pass rfi
[2024:07:02:12:02:01]: Info: SDR color coding [Rec. 601]
[2024:07:02:12:02:01]: Info: Color depth: 8-bit
[2024:07:02:12:02:01]: Info: Color range: [JPEG]
[2024:07:02:12:02:01]: Info: NvEnc: created encoder P7 two-pass rfi
[2024:07:02:12:02:01]: Info: SDR color coding [Rec. 601]
[2024:07:02:12:02:01]: Info: Color depth: 8-bit
[2024:07:02:12:02:01]: Info: Color range: [JPEG]
[2024:07:02:12:02:01]: Info: NvEnc: created encoder P7 two-pass rfi
[2024:07:02:12:02:02]: Info:
Device Description : NVIDIA GeForce RTX 4090
Device Vendor ID : 0x000010DE
Device Device ID : 0x00002684
Device Video Mem : 22612 MiB
Device Sys Mem : 0 MiB
Share Sys Mem : 32674 MiB
Feature Level : 0x0000B100
Capture size : 2560x1440
Offset : 0x0
Virtual Desktop : 2560x1440
[2024:07:02:12:02:02]: Info: Active GPU has HAGS enabled
[2024:07:02:12:02:02]: Info: Using realtime GPU priority
[2024:07:02:12:02:02]: Info:
Colorspace : DXGI_COLOR_SPACE_RGB_FULL_G2084_NONE_P2020
Bits Per Color : 10
Red Primary : [0.685547,0.308594]
Green Primary : [0.264648,0.667969]
Blue Primary : [0.150391,0.0576172]
White Point : [0.313477,0.329102]
Min Luminance : 0.3915 nits
Max Luminance : 408.76 nits
Max Full Luminance : 408.76 nits
[2024:07:02:12:02:02]: Info: Desktop resolution [2560x1440]
[2024:07:02:12:02:02]: Info: Desktop format [DXGI_FORMAT_R16G16B16A16_FLOAT]
[2024:07:02:12:02:02]: Info: Display refresh rate [179.96Hz]
[2024:07:02:12:02:02]: Info: Requested frame rate [60fps]
[2024:07:02:12:02:02]: Info: HDR color coding [Rec. 2020 + SMPTE 2084 PQ]
[2024:07:02:12:02:02]: Info: Color depth: 10-bit
[2024:07:02:12:02:02]: Info: Color range: [JPEG]
[2024:07:02:12:02:02]: Info: NvEnc: created encoder P7 10-bit two-pass rfi
[2024:07:02:12:02:02]: Info: HDR color coding [Rec. 2020 + SMPTE 2084 PQ]
[2024:07:02:12:02:02]: Info: Color depth: 10-bit
[2024:07:02:12:02:02]: Info: Color range: [JPEG]
[2024:07:02:12:02:02]: Info: NvEnc: created encoder P7 10-bit two-pass rfi
[2024:07:02:12:02:02]: Info:
[2024:07:02:12:02:02]: Info: // Ignore any errors mentioned above, they are not relevant. //
[2024:07:02:12:02:02]: Info:
[2024:07:02:12:02:02]: Info: Found H.264 encoder: h264_nvenc [nvenc]
[2024:07:02:12:02:02]: Info: Found HEVC encoder: hevc_nvenc [nvenc]
[2024:07:02:12:02:02]: Info: Found AV1 encoder: av1_nvenc [nvenc]
[2024:07:02:12:02:02]: Info: Configuration UI available at [https://localhost:47990]
[2024:07:02:12:02:03]: Info: Registered Sunshine mDNS service
[2024:07:02:12:02:04]: Info: Completed UPnP port mappings to 192.168.0.155 via http://192.168.0.1:5000/rootDesc.xml
[2024:07:02:12:02:15]: Info: Opening UI from system tray
[2024:07:02:12:02:15]: Info: Resolved user-provided command 'https://localhost:47990' to '"C:\Program Files\Google\Chrome Beta\Application\chrome.exe" --single-argument https://localhost:47990'
[2024:07:02:12:02:15]: Info: https://localhost:47990 running with PID 27700
[2024:07:02:12:02:15]: Info: Opened url [https://localhost:47990]
[2024:07:02:12:02:15]: Info: Web UI: [::1] -- not authorized
Works fine for me on windows 11 ltsc
Now, I foud that I can succesfully connect to PC, but the Web UI is still not accessable. Also, I found a detail in the log:
[2024:07:02:12:02:15]: Info: Opened url [https://localhost:47990] [2024:07:02:12:02:15]: Info: Web UI: [::1] -- not authorized
It seems the Web UI is using ipv6? But when I use https://[::1]:47990/config#, it shows unsafe reminder, when I click access anyway, the webpage remain unchange. And I try access Web UI by modify hosts file that state 127.0.0.1 localhost, it is not working. Also, I try to accesee Web UI by upnp, that is, ``https://192.168.0.155:47990`, not working again.
the webpage remain unchange
Please clarify your statement. Does this mean it's working as expected, or it is still in a broken state?
The unsafe reminder is unavoidable, since we use a self signed certificate.
Please clarify your statement. Does this mean it's working as expected, or it is still in a broken state?
Thanks for asking. To be clear, now I can stream the PC screen normally on the Android device (no need to enter the PIN in the Sunshine server because the connection has been saved before), and I use the browser on the Android device through UPNP mapping (https://192.168. 0.155:47990, of which 192.168.0.155 is the PC with Sunshine Server installed) can access the Web UI normally.
However, on the PC side, I still can't access the Web UI through any of the addresses below:
- https://localhost:47990
- https://127.0.0.1:47990
- https://[::1]:47990
Regarding the unsafe reminder, I mean that sometimes when accessing the aforementioned address on the PC, the browser displays an insecure connection page. However, as you know, the browser usually provides a "Continue" button, and typically, clicking this button allows the browser to proceed to the desired webpage (in this case, the Web UI). But this time, nothing happens; it just stays on the insecure connection page without any changes.
To summarize, so far, streaming is possible, and the Web UI can be successfully accessed via port mapping through UPNP and the local network address of the PC from other devices on the same local network. The only issue is that the Web UI cannot be accessed on the PC where the Sunshine Server is installed. This is a peculiar problem.
I would try removing the certificates and restart sunshine, forcing them to be re-generated.
I would try removing the certificates and restart sunshine, forcing them to be re-generated.
I tried but still not working.
Thanks for this! I'm not sure if it's a problem with some configuration of my PC, such as a firewall, or with Windows Build 24H2. But in any case I can stream now. But we can leave this Issue for now and see if the same thing happens when the 24H2 update is pushed out massively.
Hi everyone, I have located the problem. A long time ago I changed the network control algorithm of Windows from cubic to bbrv2, and everything was fine at that time. When I updated to Windows 24H2, the problem occurred.
Today, when I rolled back the Windows network control algorithm to cubic, I could immediately access the Web UI smoothly.
So I can only guess that some kind of compatibility change with the new build for bbrv2 is causing some anomalies with the LAN.
Bbrv2, yep. Same issue here, ipfs did not work either... And proxies and Maplsoft Maple... LOL
Adding onto this ticket with the same issue. I have been experiencing this for many months now, but have been ignoring it by bypassing via the browser ignore certificate prompt. However now I want to fix it for another reason, and I am not sure what to do next.
I'm using Chrome and I get this whenever I try to access the Sunshine server installed on my Windows 24H2 machine.
Adding onto this ticket with the same issue. I have been experiencing this for many months now, but have been ignoring it by bypassing via the browser ignore certificate prompt. However now I want to fix it for another reason, and I am not sure what to do next.
I'm using Chrome and I get this whenever I try to access the Sunshine server installed on my Windows 24H2 machine.
Same issue for me, is there already a solution for it?
i have the same problem too! install / uninstall / repair fix. nothing is working, just can't get on web UI via "https://localhost:47990/". this is really frustrating! wasted hours!!!
I had the same issue and I realize that you need to run the application from the proper location for example in my case I installed the applicaiton in this location: /home/geo/development/geosp/sunshine/squashfs-root so I created the shell script run_sunshine like this to run sunshine:
#!/bin/bash
# Set the working directory
cd /home/geo/development/geosp/sunshine/squashfs-root
# Launch Sunshine with the correct display
DISPLAY=:1 ./usr/bin/sunshine
In this way the executable starts from the it's root location, and is able to find the correct paths to everything it needs. I hope this helps.
It seems this issue hasn't had any activity in the past 90 days. If it's still something you'd like addressed, please let us know by leaving a comment. Otherwise, to help keep our backlog tidy, we'll be closing this issue in 10 days. Thanks!
Original issue is still present for me. I worked around it by allowing insecure connections in my browser, however this is not a permanent solution and I think it should still be resolved.
I worked around it by allowing insecure connections in my browser
That's the only solution, as Sunshine uses a self signed certificate; therefore you will always get a warning about that.
I had the same issue. In Chrome open the site, press F12, go to application, storage and clear site data.
