I know we’ve seen this before many times and it is over in github issues as well, it seems to have happened more often with recent releases than before.
I wanted to move the topic here so that we can troubleshoot and once and for all find a permanent solution if possible.
I thought the viewer would skip the URL/asset if it encountered this problem, is that feature only in the developer or experimental version and not on stable version?
Just wondering, is some sort of email alert feature active on the Pro version of screenly when the viewer is down or experiences this error?
This happened overnight with that brand new setup from scratch of screenly with new Pi and new SD card.
The environment was set up so that I can rule out the causes that dont affect the device itself, such as placing the Pi connected to this TV right next to the access point, the device is still connected and online so it is not an issue of connectivity.
The URL/asset works at first, so what causes it to get this error at some random time later ? if the cause was hard-coded then it would always happen right after adding the asset/URL.