Playback error codes

When playback fails, the player shows a code such as PB-1007. Use this page to see what it means and what usually fixes it.

PB-1001

Stream preparation failed

The server could not prepare this title for playback.

Resolve / prepare

Underlying issue: Resolve request failed (network, auth, upstream offline, or FFmpeg session could not start).
What to do: Check connection, sign in again, wait a minute, then retry. If it persists, note the error code for support.

PB-1002

No playback URL

Resolve completed but returned no stream address.

Resolve / prepare

Underlying issue: Server routing bug or upstream returned an empty/incompatible response.
What to do: Close the player and try again. Report PB-1002 if it repeats for the same title.

PB-1003

Decode error

The browser could not decode the video or audio.

Browser playback

Underlying issue: Bad HLS segment format (e.g. fMP4 with MPEG-TS bitstream filters), corrupt segment, codec mismatch, or server transcode cache full.
What to do: Retry after server restart. MKV copy should use MPEG-TS HLS on mobile — if this persists with PB-1003, report the title and code.

PB-1004

Network error

The browser lost the stream while loading.

Browser playback

Underlying issue: Connection drop, upstream timeout, or proxy closed the HTTP connection.
What to do: Check Wi‑Fi or cellular signal and retry.

PB-1005

Playback aborted

Loading was cancelled before the stream could start.

Browser playback

Underlying issue: User navigated away, player was torn down mid-load, or a new stream replaced the current one.
What to do: Open the title again and press Watch Now once.

PB-1006

Format not supported

This browser cannot play the stream format served.

Browser playback

Underlying issue: MIME/codec not supported — common when Safari receives malformed fMP4 HLS, progressive remux pipes, or bad init segments.
What to do: Mobile MKV should use MPEG-TS HLS copy (not remux pipe or fMP4 copy). Retry; if it persists, note the code.

PB-1007

Playback failed

The video element reported an unknown error.

Browser playback

Underlying issue: Generic MediaError not classified — often CORS, empty response, or MIME type mismatch.
What to do: Retry. Note PB-1007 and the title ID for support.

PB-1008

HLS not supported

This browser cannot run hls.js (MSE unavailable).

HLS

Underlying issue: Very old browser or restricted WebView without Media Source Extensions.
What to do: Use Safari/Chrome on a supported device, or enable MSE in the browser.

PB-1009

HLS stream error

The HLS manifest or a segment could not be loaded.

HLS

Underlying issue: Segment 404 while encoding, manifest timeout, CDN/upstream failure, or session expired.
What to do: Wait for encoding buffer, then retry. Long waits may mean server FFmpeg is stuck.

PB-1010

Live TV not supported

This browser cannot play MPEG-TS live streams.

Live TV

Underlying issue: mpegts.js MSE live playback feature missing.
What to do: Use Chrome/Edge/Firefox on desktop or a supported Android browser.

PB-1011

Live channel error

The live transcode or TS feed failed.

Live TV

Underlying issue: Channel offline or upstream stream outage.
What to do: Try another channel or retry in a few minutes.

PB-1012

Remux pipe unsupported on mobile

Server sent a progressive remux stream that mobile Safari rejects.

Server routing

Underlying issue: MKV/Matroska sources were routed to /remux (fragmented MP4 pipe) instead of HLS copy on mobile.
What to do: Server should route mobile MKV to HLS copy sessions. Update resolve routing.

PB-1013

Autoplay blocked

Playback could not start automatically.

Browser playback

Underlying issue: Browser blocked unmuted autoplay and buffer was not ready within the gesture window.
What to do: Press Watch Now again or use player controls to start.