haoqian

I was experiencing this error too. The issue was that the correct order is to yarn chain before yarn start. So when the frontend starts if finds the node already...