@wishmaster270 I used to try the forced armv7l approach, but had failures in other areas as the versions of node increased. u can see the code commented out in the script. I finally gave up and implemented the script to launch chromium over the server as the only reliable approach.

I figured this out. the new router uses a different IP structure. 192.168.0.1 where my old router used 192.168.1.1. For some reason the pi connected to the new router but saved the old default gateway. I was able to correct it with the below command. sudo route add default gw 192.168.0.1 dev wlan0

Really nice. I like how you can’t see wires as well.

@ByronJames never seen this happen What OS is this?? Technically a second instance should fail as the port is in use by the first instance.