Documentsplayer-not-showing-in-the-server-or-not-reporting---troubleshooting-checklist

Player not showing in the server or not reporting - troubleshooting checklist

Go through these checks in order. Most can be read from the welcome screen of the player.

Checklist

  1. Network. The welcome screen shows Link, DHCP, DNS and PING. All should show OK.
  2. Server address. The "Registered server" on the welcome screen must be your server. To change it, connect a keyboard and press Ctrl+N or F6, or open the player's settings page in a browser. For an open-source server, add the port :3000 to the address.
http://<player ip address>:8000/settings
  1. Registration. The player ID on the welcome screen must be registered in your account. Go to Screens and click + Add Screen. See Screens.
  2. Firewall or proxy. Allow WebSocket connections to the server on port 443 (pisignage.com) or port 3000 (open-source server). The Windows firewall sometimes blocks port 3000, so open it. See Connectivity needs for the player (firewall).
  3. Date and time. A wrong date on the player breaks the secure connection to the server. Make sure NTP (UDP port 123) is not blocked. See Pi time is lagging, playlists are not scheduled in time.
  4. Enrollment key (player 5.5.2 and later). After re-imaging or cloning an SD card, the server rejects the player and emails the account owner. Use Reset Enrollment Key in the player's Settings, on the Advanced tab.

A player that stops reporting is shown as offline after 15 minutes. See Player-server communication to know how reporting works.

Still stuck? Send the Player logs to support@pisignage.com.