Orbit Play

Fix Chiaki “registration failed” on a PS5

You entered the PIN and account ID, but registering the PS5 in Chiaki or chiaki-ng fails. Neither app shows a separate error message: the reason is in the log in the Register Console window, which ends with lines such as Regist eventually failed or Regist timed out waiting for search response.

This page matches each message to its cause and the fixes people report, on standard and jailbroken consoles. It was checked against both apps’ source code and issue trackers on 24 October 2026. We haven’t tested these tools ourselves.

Find your error

Codes appear in the log after Reported Application Reason:.

Message What it means What to try
Regist timed out waiting for search response or Regist search failed The PS5 never answered the registration search on UDP port 9295. Make sure the PS5 can be reached.
Regist failed to send search: Invalid argument Reported with Broadcast turned on. Enter the PS5’s IP address and turn off Broadcast.
0x80108b09 (Regist failed, probably invalid PIN) Chiaki’s own label: the PIN was probably wrong. Use a fresh PIN.
0x80108b02 (Invalid PSN ID) The account ID wasn’t accepted. Check the account ID.
0x80108bff (unknown) Reported when PS4 Firmware < 7.0 was selected for a newer console. Choose the right console type and use the account ID.
0x80108b11 (RP-Version mismatch) Reported after console system updates. Look for a newer Chiaki or chiaki-ng release.
Invalid Account-ID The ID isn’t 8 bytes in base64. Check the account ID.
CE-110032-7 on the PS5 Sony: online ID information does not match. Use the account ID of the user logged in on the PS5.

The codes 0x80108b09, 0x80108b02, 0x80108b10 (“Remote is already in use”), 0x80108b11 and 0x80108b15 (“Remote Play on Console crashed”) are the ones both apps name in their source. If pairing works but the stream is then refused with 0x80108b12, see the “Remote Play is disabled” 403 page.

Check the account ID

  • It must be the logged-in user’s. The get-pin README says “only the displayed account id will be accepted when pairing, which is the currently logged in user”. Log into the PS5 user you’re registering before you get the PIN.
  • Use the account ID, not the online ID. Chiaki’s README says PS4 system software 7.0 and later need the account ID, and the PS5 uses it too. In chiaki-ng, picking PS4 Firmware < 7.0 on a newer console gave 0x80108bff.
  • The format is base64 of 8 bytes in little-endian order: 12 characters ending in one =. chiaki-ng shows “The PSN Account-ID must be exactly 8 bytes encoded as base64” otherwise. The account ID converter turns a decimal or hex ID into this format and checks a base64 one.
  • An ID ending in == has an extra character. LinkDev’s standalone source writes two =, making 13 characters, and etaHEN fixed the same extra = in version 2.0b. Delete one = and check the result in the converter.
  • Check for typos such as 1 and l: one user had the wrong ID for that reason. A child account gave 0x80108b02 in one report.

Use a fresh PIN

  • Get a new PIN for each attempt. get-pin, LinkDev and etaHEN all cancel the previous PIN when they create a new one, for example get-pin’s “invalidate previous pin”.
  • Register before it times out. Sony doesn’t publish how long a PIN lasts. LinkDev counts down 300 seconds, and get-pin waits 120 seconds by default.
  • Type all eight digits. LinkDev shows the PIN as two groups of four, but Chiaki’s PIN field takes the eight digits on their own.
  • On a standard PS5, the PIN appears when you choose Pair Device under Remote Play settings. Chiaki’s documentation calls it Link Device.

Make sure the PS5 can be reached

  • Registration uses port 9295. Chiaki first sends a search over UDP port 9295 and then the registration request over TCP port 9295 (source). A search timeout means that first step got no answer.
  • Turn off Broadcast and enter the PS5’s IP address. This is the most common fix in chiaki-ng’s issue tracker: “can you try with broadcast unchecked?” “That fixed it”. Its maintainer wrote that registration “doesn’t work many times with broadcast enabled”. The original Chiaki ticks Broadcast when the host field is empty.
  • Choose PS5 as the console type. It changes both the search and the registration request.
  • Check the firewall and VPN. Chiaki’s author said a search timeout means the console didn’t answer, and asked whether it was in registration mode, adding that “it can also be caused by a firewall”. Registering over a WireGuard VPN gave the same timeout.
  • Keep the PS5 on the PIN screen, or the PIN tool running, until registration finishes.

Jailbroken PS5s: activate the account first

  • An offline account needs activating before it can pair. As Wololo reported, getting the PIN used to need a PSN connection. Tools such as OffAct activate the account, and LinkDev, get-pin, ActRemoteLink or etaHEN’s Remote Play menu then show the PIN and the base64 account ID.
  • Restart after activating. LinkDev’s README says to reboot after activating the account with OffAct. get-pin’s README says the restart wasn’t needed in its own test, but “others reported this as being a required step”.
  • The generated ID is fine for Chiaki. get-pin’s README says you only need your real PSN account ID for the official Remote Play app.
  • Second users on 10.00 and later can register but then see a 403 error when the stream starts. See the 403 page and Remote Play methods by firmware.

With Orbit Play

Orbit Play doesn’t use Chiaki’s registration window. It reads the account ID of the profile logged in on the PS5 and exchanges the Remote Play PIN itself while pairing, so there’s no base64 ID or PIN to type. If a profile needs a local account ID or Remote Play enabled, its account setup does that after you review the changes. Orbit Play has been tested on 13.60. If pairing fails there, see troubleshooting.

Sources

Updated 2026-10-24