A player connects to the server on its own once it's on Ethernet or Wi-Fi. If your network has no DHCP, set a static IP (step 2).
1. Check the welcome screen
When the player starts, it shows a welcome screen like this:
- Player IP addresses: there must be a real address. 169.254.x.x means no address was assigned.
-
Registered server: this must be your server, e.g. pisignage.com, or your self-hosted address with its port, like
:3000. Connection status must be Connected. -
Connectivity:
- Link: DOWN means the cable or Wi-Fi isn't connected.
- DNS: FAIL means the player can't look up pisignage.com, so check the DNS settings.
- PING: FAIL means there's no internet access.
- DHCP shows your router's address. NO means the player got no address.
- Ctrl N / F6: press this on a USB keyboard to change settings (step 2).
If everything under Connectivity is OK but the status is still Disconnected, like in the picture above, the network is fine and a firewall or proxy is blocking the server. Go to step 3.
If the screen says "There seems to be no Network Connection", the player has no network. See step 2.
2. Change network settings on the player
- With a keyboard: connect a USB keyboard and press Ctrl+N or F6. A menu opens where you can set DHCP or a static IP, Wi-Fi, DNS, the server address and the hotspot.
-
With a phone or laptop: if Wi-Fi isn't set up, the player broadcasts a Wi-Fi network called piplayer_XXXX. Connect to it and open
http://192.168.100.1:8000/settings.
If the router goes down or the Wi-Fi password changes, the player switches back to this hotspot so you can set it up again. It rejoins your Wi-Fi automatically when the network returns.
3. Check the firewall or proxy
- Allow outgoing https (port 443) and websocket traffic to your server.
- If 443 is blocked, the player tries http on port 80.
- For a self-hosted server, open its port (usually 3000).
See Secure communication (https) between player & server and Connectivity needs for the player (firewall).
4. Check from the player's terminal
Open a terminal (see this article), or in the new interface use Pi Terminal if the player is still online. Then run:
ip a # IP addresses nmcli dev status # Ethernet / Wi-Fi state ping -c 3 pisignage.com # Internet + DNS tail -200 ~/forever_out.log # player log
In the log, look for Websocket: connected to server, or note any error lines.
5. Still not working?
Email support@pisignage.com with your player ID, a photo of the welcome screen and the log output.
Older players (images before Bookworm)
Connecting to network is normally straight forward and player connects to server over Internet once plugged into Ethernet or wifi network is programmed.
If your network is not DHCP enabled, then you can program the Static IP parameters as provided by network/ISP administrator.
When the player is ready after bootup, a welcome screen is shown which displays network connectivity status as shown in the screenshot. Make sure
- The player IP address is properly assigned (not 169.254.177.128 which is USB tethering address)
- Make sure server name or address is correct and port number 3000 is mentioned in case of local server
- Firewall or proxy is correctly programmed to allow port 80 http traffic along with websocket traffic (on port 80 as well) from and to the player
- Note the server connectivity status should be "connected" (not waiting)
- Status of Network - Ethernet: UP, DNS:OK and DHCP: <proper ip address> are needed
Troubleshooting
- Connect to terminal of player using one of the methods mentioned in this article
- Issue commands ifconfig, iwconfig and other linux commands to see that addresses are available
- Look at /etc/network/interfaces and /etc/wpa_supplicant/wpa_supplicant.conf to make sure settings are correctly programmed (look for help from the Internet on Linux networking like https://www.tecmint.com/linux-network-configuration-and-troubleshooting-commands/)
- Look at the log using command tail -200 /home/pi/forever_out.log. There will be lines like the following. Note the error messages if any.
2 Mar 15:03:02 - info: starting socketio to pisignage.com
2 Mar 15:03:02 - info: socket.io: connected to server 3y2pPLWkRsnDaVtHNEGH
- Contact us at support@pisignage.com with the necessary logs for further help.
Comments
0 comments
Please sign in to leave a comment.