That’s really strange. I haven’t seen that error before. Thanks for flagging it! I’ll dig into that 403 on main.js and give it a try in Firefox (and other browsers). Appreciate your help!
