sam detweiler

aha.. something is already using that port... do this ``` pm2 stop all pm2 flush ps -ef | grep node ```

aha, the server side stuck sudo kill -9 32740 then npm start

cool, thanks do which chromium-browser and which chromium need a browser, was installed by default

when u click, nothing happens.. well that's a problem. I haven't tried legacy yet. will do shortly

no, that's been flaky too and I don't think recommended for pi0w.

I don't know at this time. pi0w2 is out, same size and footprint. like pi3 speed

because there is an electron for armv7l, all is ok. don't need to do the server with chromium over to fake it

I have confirmed that chromium on legacy is broken. uninstall/reinstall does not fix.. I have started discussion with pi os team

firefox also fails

you need to use the legacy, buster image for pi0w, (and pi1) using armv6l