LizardByte / LizardByte/Sunshine
Cant pair on the SteamDeck
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 41.3k
- Forks
- 2.1k
- Avg merge
- 23h 47m
- Merged PRs (30d)
- 124
Description
### 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
Every other device can pair with Moonlight, however my Steam Deck refuses to pair. I get the Pair pin pop up and after a few seconds I then get a "Connection closed (error 2)". I do not get the usual pin popup on my host machine like I normally would when a pair request is sent and also when the pin that is briefly showed is used it is refused.
### Expected Behavior
I would normally expect the pin to work, and the connection to not be closed.
### Additional Context
_No response_
### Host Operating System
Windows
### Operating System Version
Windows 11 Home 25H2
### Architecture
amd64/x86_64
### Package
Windows - exe installer
### GPU Type
NVIDIA
### GPU Model
Acer KA240H on NVIDIA GeForce GTX 1080
### GPU Driver/Mesa Version
32.0.15.8266
### Capture Method
None
### Apps
```json
```
### Log output
```shell
```
### Online logs
https://gist.github.com/SimonPhilpott/38995a6e992f12a907c50a4b8936eb97
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the online log linked in the issue and reproducing pairing from a Steam Deck to the Windows 11 host described. Trace the pairing failure indicated by "Connection closed (error 2)" and verify the PIN request reaches the host; done means the host shows the PIN prompt and accepts the Steam Deck pairing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- authentication, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100