@fenno Is it necessary for you to start the server separately? You can provide a https://figwheel.org/docs/ring-handler.html to figwheel-main.edn so figwheel embed a server for you which is very convenient. Also I notice on your error resources\public\public which looks odd, is your path correct?

Hi @loic, thanks for pointing out the public\public - now corrected! I’ve tried :ring-handler; my only middleware is wrap-defaults. Keeping secure-site-defaults gives ERR_SSL_PROTOCOL_ERROR; downgrading to site-defaults allows the page to load, but then Sente (the library I’m using for websocket comms) fails to connect. https://figwheel.org/docs/your_own_server suggests it’s easy to outgrow :ring-handler, so I’d assumed this was a limitation and that it was time to run a server alongside figwheel-main, but the doc doesn’t provide a lot of detail on how to do so. I think I’m close to the solution as client-server communication works via both Sente and figwheel-main when I run the two separate servers; the only issue I have seems to be the wrap-resource inside of wrap-defaults seems to have exclusive access to the files figwheel-main is trying to rebuild. Of course, I’m open to having misinterpreted everything and being in a coincidentally-nearly-working situation that will never quite fly ☺️