Fix ‘Console Available But Session Fails to Start’ in Chiaki-ng
If your console appears in chiaki-ng but the session dies the moment you connect — or registration keeps failing — the cause is usually a stale PIN, a discovery problem, or outdated console firmware. Newer builds fixed several of these edge cases (including sessions failing while waiting for the login PIN), so updating to v1.10.0 is step zero. The checklist below covers the rest.
Step 0: Update Everything
- Chiaki-ng → v1.10.0. Recent v1.9.x builds fixed real session-start bugs: consoles that became available right after clicking but never started a session, and sessions failing while waiting for the login PIN. If you are on an older build, update before changing anything else — downloads on GitHub.
- Console firmware → latest. PS5: Settings → System → System Software Update. PS4: Settings → System Software Update. Firmware updates regularly fix Remote Play handshake issues.
Step 1: Fix Registration (PIN Problems)
- Generate a fresh PIN on the console.
PS5: Settings → System → Remote Play → Link Device. PS4: Settings → Remote Play Connection Settings → Add Device. PINs expire quickly — enter it in chiaki-ng immediately. - Or skip the PIN entirely.
Since v1.9.4, chiaki-ng supports automatic pinless registration for locally discovered consoles. On your home network, just double-click the discovered console and register without a PIN. - Double-check your PSN Account ID.
It must be the Base64-encoded Account ID (fetch it via the in-app PlayStation login added in v1.6.0), not your username or email. A wrong ID fails registration silently.
Step 2: Fix Discovery (Console Visible, Session Dies)
- Enter the console’s IP manually. In the registration dialog, type the console’s local IP address (find it in the console’s network settings) instead of relying on auto-discovery.
- Same subnet, no VPN. Both devices must be on the same local network branch; disable VPNs on the streaming device and turn off router AP/client isolation.
- Restart chiaki-ng after registering. Since v1.9.x, PSN-registered hosts appear immediately — but if a console was registered long ago on an old version, re-registering fresh clears stale entries.
Step 3: Remote (Away-from-Home) Session Failures
If sessions start at home but fail remotely, the issue is the internet path, not registration: complete the
Remote Play over the internet setup (PSN registration + NAT/port forwarding 9295–9297). Carrier-grade NAT on some mobile networks cannot be punched through by any settings.
Frequently Asked Questions
Why does chiaki-ng show my console as available but the session fails to start?
This exact bug was fixed in recent v1.9.x builds (consoles becoming available right after clicking, sessions dying while waiting for the login PIN). Update to v1.10.0 first. If it persists, update console firmware, then try manual IP entry in the registration dialog.
My 8-digit PIN is always rejected. What am I doing wrong?
PINs expire within minutes — generate a fresh one on the console and enter it immediately. Or skip PINs entirely: v1.9.4+ supports automatic pinless registration for locally discovered consoles on your home network.
Do I need the PSN Account ID or my PSN password to register?
The Account ID — a Base64-encoded token, not your password or username. Get it through the in-app PlayStation login (v1.6.0+) or the open-source lookup script. Entering your username instead of the Account ID is a common silent-failure cause.
Session works at home but not when I'm away. Is registration broken?
Registration is fine — the internet path is the problem. You need PSN-based registration plus a working NAT/port path (see our remote-over-internet guide). Some mobile carriers use carrier-grade NAT that no client setting can traverse.
Chiaki-ng.com is an independent, unofficial resource site. Chiaki-ng is free and open-source software (GNU AGPLv3) built by its community contributors. This site is not affiliated with, endorsed by, or connected to Sony Interactive Entertainment.