Skip to content

Raspberry Pi player setup and recovery

The Pi image is the reference unattended browser player: kiosk Chromium, persistent profile, and restart behavior around player.canvasrelay.app.

What you may be seeing

  • A CanvasRelay Raspberry Pi does not reach the pairing/player screen or stops checking in.

What usually causes it

  • Power/network problem.
  • Wi-Fi was not configured correctly when the image was prepared.
  • Chromium/player service is recovering after a crash/reboot.
  • Storage/image corruption after hardware or SD-card failure.

Do this

  1. Confirm stable power, HDMI, and network first; Ethernet is the simplest reliability check.
  2. If using Wi-Fi, confirm the credentials/network are still valid and do not require a captive portal.
  3. Allow the image's kiosk/service restart behavior to relaunch the player rather than manually creating duplicate startup scripts.
  4. If the device reaches a pairing code, reconnect it from Screens and assign the board.

You know it is fixed when

  • The Pi reaches the player automatically after reboot and Screens reports fresh heartbeats.

When this is probably a real support issue

  • The Pi has working network/power but repeatedly cannot start the player service or its storage/image is damaged.

Search phrases this guide covers

Pi screen · Raspberry Pi menu board · Pi won't boot · Pi player offline