Advanced

Two switches on ScreenlyOS screens: certificate verification, and exposing device metrics for your own monitoring.

Both appear on ScreenlyOS screens, on Raspberry Pi based players and the Player Max.

Verify SSL certificates

Off by default. When on, the player refuses to load a web page whose certificate does not validate.

Turn it on if your policy demands it and every page in your playlists has a valid certificate. Leave it off if a page you need is served with a self-signed or internal certificate, which is common on an intranet.

The trade-off is real either way, so make it deliberately rather than by accident.

Node Exporter

Off by default. When on, the player exposes hardware and system metrics in Prometheus format, so your own monitoring can scrape them alongside everything else you run.

From ScreenlyOS 26.9.0, the player serves the metrics over HTTPS on port 9100 and identifies itself with its own device certificate. Point your monitoring at https on that port, verify the certificate against the Screenly certificate authority, and set the expected server name to the player's hostname, the one that starts with srly-. Download CA certificate on the screen's Actions tab gives you the CA certificate (see Device certificates). Older releases serve the metrics over plain HTTP. The firewall side is in Hostnames and ports.

Turn it on if you already run Prometheus and want screens in the same dashboards as your servers. If you do not, leave it off. The Details tab shows a screen's connection, network, and hardware with no setup.

For developers

For a Prometheus scrape job, use scheme: https with a tls_config whose ca_file points at the Screenly CA certificate and whose server_name is the player's hostname. The port stays 9100, and the metrics themselves are unchanged.