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 Canvas Relay Raspberry Pi 5 does not reach the account/screen chooser or stops checking in.

What usually causes it

  • Power, HDMI, Ethernet, or upstream network problem.
  • The image was written to the wrong or failing storage device.
  • Chromium/player service is recovering after a crash/reboot.
  • Storage/image corruption after hardware, card, or power failure.

Do this

  1. Confirm a Raspberry Pi 5, suitable power, HDMI, flashed storage, and Ethernet first.
  2. If first boot shows sign-in, use an existing Canvas Relay email/password and choose a published screen directly on the Pi.
  3. Allow the image's kiosk/service restart behavior to relaunch the player rather than manually creating duplicate startup scripts.
  4. Press Esc during playback to return to the screen chooser or sign out. Reflash only after hardware and storage checks point to image corruption.

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