WesleyVanNeck
commented
1 week ago Works fine for me on windows 11 ltsc
Open WhiteByeBye opened 1 week ago
WesleyVanNeck
commented
1 week ago Works fine for me on windows 11 ltsc
WhiteByeBye
commented
1 week ago 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.
ReenigneArcher
commented
1 week ago 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.
WhiteByeBye
commented
1 week ago 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:
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.
ReenigneArcher
commented
1 week ago I would try removing the certificates and restart sunshine, forcing them to be re-generated.
WhiteByeBye
commented
1 week ago 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.
taitaitai1777
commented
1 week ago Users are reporting difficulties accessing the WebUI and establishing connections via Moonlight on Windows 24H2. These issues may stem from network configurations or security policies introduced in the latest Windows update. By diagnosing and applying precise modifications, we aim to restore full functionality.
Check Network Configurations:
Firewall and Antivirus Checks:
Service Status Verification:
Check Firewall Rules:
# Allowing WebUI Port (example: 47989)
New-NetFirewallRule -DisplayName "Sunshine WebUI" -Direction Inbound -Protocol TCP -LocalPort 47989 -Action Allow
# Allowing Moonlight Port (example: 47984)
New-NetFirewallRule -DisplayName "Sunshine Moonlight" -Direction Inbound -Protocol TCP -LocalPort 47984 -Action AllowAdjust Sunshine Configuration:
config.yml or a similar file) to check for appropriate IP binding and port settings.# Example Sunshine Config
webui:
port: 47989
bind: 0.0.0.0 # Ensure binding to all interfaces
moonlight:
port: 47984
bind: 0.0.0.0 # Ensure binding to all interfacesRestart the Sunshine Service:
# Restart Sunshine Service
Restart-Service -Name SunshineServiceReview and update the repository to ensure Sunshine binds to the correct IP and listens on the required ports.
Make sure that Sunshine binds to the correct IP and listens on required ports.
// Example of binding code
listener, err := net.Listen("tcp", "localhost:47989")
if err != nil {
log.Fatal("Failed to bind to localhost:47989", err)
}Update the binding to allow access from all required interfaces.
// Modified binding to ensure proper connection
listener, err := net.Listen("tcp", "0.0.0.0:47989")
if err != nil {
log.Fatal("Failed to bind to 0.0.0.0:47989", err)
}Fork the Repository:
Clone the Repository:
git clone https://github.com/yourusername/Sunshine.git
cd SunshineModify the Code:
Open the necessary files using your preferred editor.
vim path/to/sunshine/server.goImplement the necessary changes to ensure proper binding.
Testing:
Commit and Push Changes:
git add path/to/modified/files
git commit -m "Fix: Ensure proper binding for WebUI and Moonlight on Windows 24H2"
git push origin mainCreate a Pull Request:
By following these diagnostic steps and applying the proposed code changes, we aim to resolve the accessibility issues of the WebUI and Moonlight connections on the Windows 24H2 environment. This approach targets potential network and configuration issues that may arise from the recent Windows update.
ReenigneArcher
commented
1 week ago @taitaitai1777 do not post ai generated answers here
Is there an existing issue for this?
Is your issue described in 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
Apps
Relevant log output