Errors

The feed runs on Centrifugo v6, so you see standard Centrifugo codes plus one of ours. Official client libraries reconnect by themselves for every non-terminal code.

Our code

Code	Reason	Meaning	What to do
4501	invalid api key	Key or token is wrong, expired or revoked (deliberately indistinguishable)	Check the key; for browser tokens, mint a fresh one. Do not retry in a tight loop
4501	no api key	No Authorization header and no data.key in the connect payload	Send the key (see Authentication)
4501	bad request	The connect request could not be parsed	Use an official client library

Common Centrifugo disconnect codes

Code	Name	Reconnects?	Meaning
3000	Connection closed	yes	Normal close
3001	Shutdown	yes	Server restarting; reconnect and re-fetch the snapshot
3004	Server error	yes	Transient server problem
3008	Slow	yes	Your client was not reading fast enough and its queue overflowed. Process messages faster or off the read loop
3010	Insufficient state	yes	Recovery could not continue; re-fetch the snapshot
3012	No pong	yes	Heartbeat missed, usually a network drop
3501	Bad request	no	Protocol violation from the client
3503	Force no reconnect	no	Disconnected on purpose (for example a revoked key)
3504	Connection limit	no	Too many connections

Full list: Centrifugo codes.

Command errors

Code	Where	Meaning
103	subscribe / publish	Permission denied: client subscribes and publishes are disabled; you are already subscribed server-side
108	history	Not available
1404	rpc	Unknown RPC method (only snapshot exists)
1503	rpc snapshot	Upstream catalogue unavailable right now; retry in a few seconds or use history