-
I chatted a bit about this in the discord and was unable to make any progress. I'd love to start a discussion here incase anyone has had similar issues. The Setup
We have an https://fakedomain.dev reverse proxy on local that's being reverse proxied with generated SSLs with Caddy server. Our Caddy file looks like
The issueWhen visiting fakedomain.dev, the site inifinite loops with logs saying
What I've tried already
Changing server.hmr Forced http1.1 in our reverse proxy. Noteslocalhost:3000 works fine, but we'd prefer to have https & our reverse proxy as Safari refuses localhost httpOnly, secure cookies. Not a dealbreaker, but we'd really like to be able to reliably test Safari in dev. I've been reading issues all morning, but nothing seems to do the trick. #1653, #1926, #1925 This same setup works in Snowpack with no special config. Not saying that to diss Vite, just as a note that something in the differences in how Vite handles wss in reverse proxies seems to be the issue. I'll make a reproduction and an issue, but wanted to get this out there in case anyone else is having this issue. Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
Small update. I checked my Snowpack setup with the same and it's websocket connects to Notice how |
Beta Was this translation helpful? Give feedback.
-
Another update here... |
Beta Was this translation helpful? Give feedback.
-
OK! Here's the fix. Thank you to @matias-capeletto for helping me in the discord and sending me #1757
Was the config that did the trick. 443 with Caddy SSL will passthrough allowing the wss path to connect. |
Beta Was this translation helpful? Give feedback.
OK! Here's the fix.
Thank you to @matias-capeletto for helping me in the discord and sending me #1757
Was the config that did the trick. 443 with Caddy SSL will passthrough allowing the wss path to connect.