Sunshine version
v2026.906.222525
Host environment
Windows host running Sunshine.
Client
Moonlight on a phone.
Problem
After upgrading Sunshine to v2026.906.222525, pairing a new Moonlight device could appear to succeed in the Sunshine Web UI, but the Moonlight client would still fail immediately afterward with an authorization / certificate verification error similar to:
Host PC returned error: The client is not authorized. Certificate verification ...
The Sunshine PIN page reported success, so from the host side the pairing looked completed, but the client was not actually authorized.
Steps that reproduced the issue
- Sunshine already had one or more paired clients.
- Start pairing from a new Moonlight client.
- Moonlight displays a PIN.
- Enter that PIN in the Sunshine Web UI.
- Sunshine Web UI reports the pairing as successful.
- Moonlight still fails with
The client is not authorized / certificate verification error.
- Restarting Sunshine and forgetting/re-adding the host in Moonlight did not resolve it.
Workaround that fixed it
In Sunshine:
Troubleshooting -> Unpair Clients -> Unpair All
After clearing all existing paired clients, pairing the same Moonlight device again succeeded normally.
Expected behavior
A new client should be able to pair successfully without requiring all existing paired clients to be deleted. If the final certificate authorization fails, the Web UI also should not report the pairing as successful.
Additional observation
The fact that Unpair All immediately fixes the problem suggests that stale, duplicate, or otherwise conflicting client certificate/authorization records may be involved. It may be worth checking how existing named_devices / authorized client certificates are matched and updated during a new pairing operation.
I can provide additional logs or inspect sunshine_state.json if that would help narrow this down.
Sunshine version
v2026.906.222525Host environment
Windows host running Sunshine.
Client
Moonlight on a phone.
Problem
After upgrading Sunshine to
v2026.906.222525, pairing a new Moonlight device could appear to succeed in the Sunshine Web UI, but the Moonlight client would still fail immediately afterward with an authorization / certificate verification error similar to:The Sunshine PIN page reported success, so from the host side the pairing looked completed, but the client was not actually authorized.
Steps that reproduced the issue
The client is not authorized/ certificate verification error.Workaround that fixed it
In Sunshine:
Troubleshooting -> Unpair Clients -> Unpair AllAfter clearing all existing paired clients, pairing the same Moonlight device again succeeded normally.
Expected behavior
A new client should be able to pair successfully without requiring all existing paired clients to be deleted. If the final certificate authorization fails, the Web UI also should not report the pairing as successful.
Additional observation
The fact that
Unpair Allimmediately fixes the problem suggests that stale, duplicate, or otherwise conflicting client certificate/authorization records may be involved. It may be worth checking how existingnamed_devices/ authorized client certificates are matched and updated during a new pairing operation.I can provide additional logs or inspect
sunshine_state.jsonif that would help narrow this down.