Skip to content

Pairing reports success but Moonlight remains unauthorized until all paired clients are cleared (v2026.906.222525) #5696

Description

@CaiKerman

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

  1. Sunshine already had one or more paired clients.
  2. Start pairing from a new Moonlight client.
  3. Moonlight displays a PIN.
  4. Enter that PIN in the Sunshine Web UI.
  5. Sunshine Web UI reports the pairing as successful.
  6. Moonlight still fails with The client is not authorized / certificate verification error.
  7. 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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    aiPR has signs of heavy ai usage (either indicated by user or assumed)

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions