Closed anderspitman closed 5 years ago
I have no idea what I did but somewhere along the way it started working.
Ok so it was working with my self-signed local certificate, but now I'm getting the same error as before when hosted publicly with my Let's Encrypt cert. Any ideas?
FWIW the setup for HTTPS/wasm isn't too special, everything's just typically served over HTTPS! For example all wasm-bindgen examples are served over HTTPS, and they're not configured specially one way or another.
Does the exception in the console have a stack trace? Could that be pinpointed as to which JS operation is happening to caues the exception?
Thanks @alexcrichton.
Chrome gave more details. I'm opening a websocket connection which was using ws:// and needed to be changed to wss://.
When modifying the webpack-dev-server config to add https, I'm getting the following error:
Error importing `index.js`: DOMException: "The operation is insecure."
.Apparently it has something to do with the way the async import works. Is there a way around this?