sorry was busy for a while…
regarding the delay for the viewer, this might need some service tuning, which means you would go into /etc/systemd/system/screenly-viewer.service and tweak it only if you know what you’re doing with services…
can you tell me again how the browser found dead, restarting error is affecting you? this usually goes away on it’s own when all the required services are fully started…
hmm… that wifi connect service is taking so long, but then this is on a pi zero w right? because i am testing on one now and its almost the exact time you have there from the systemd-analyze blame…
so… as you can see, this could simply be that screenly-web.service is started after the screenly-viewer.service, even though on the service file it is saying that it should start after the web one (but Requires is more strict than After), but if the viewer starts first, thats pretty much as far as i know why you would get an error because the viewer is starting and trying to access that URL which is serviced from the screenly-web.service thus until that service starts fully you will always see that…
I tested by changing that file i mentioned above (screenly-viewer.service), within the contents of the file, moving the screenly-web.service from the same line as matchbox.service and making its own line with Requires=screenly-web.service, as seen on this screenshot:
I am still seeing the analyzed time though show that viewer starts up within 1-2 seconds and web service takes about 6-7 seconds so it is still starting before the web service which i explicitly said required the web service… its late so i’ll mess with this more another time.