The WebSocket handshake was not HTTP/1.1

Issue Summary

Whenever I try to launch one of my wordpress sites, I get this error immediately. This does not pop up for any of the other sites.

Troubleshooting Questions

How do I solve this issue? I have no idea how or why it happened, or even what it means. It worked perfectly fine until recently.

Hello @ethan - welcome to the Local community! :wave:

Thank you for your question. Can you please clarify - what do you mean by “launch one of your WordPress sites”?

Do you mean, when you start the site? Or using Live Links? Or when you are pushing it to your host?

I did a quick search of related error messages & I’m curious - do you have any issues with your SSL certificate for this site? It looks like that message could be related to http:// versus https:// requests.

Thank you!


Thank you for the welcome.

When I say launch I mean start the site, and click the “open admin”, and “start site” buttons, I assume that is pushing to my host, but I don’t know for sure. I’m new to all of this., but the site was working just fine for a week until that day it stopped.

The SSL doesn’t have any issues I’m aware of. I haven’t gotten it hosted yet online and thus haven’t felt the need to get an ssl yet. This is the same case for my other sites which work just fine when I launch via local.

the ssl on local is website-name.local.crt (I dont wanna say the name cause its a brand I am working with.

Hi @ethan

When you start site and open the admin that isn’t connecting the site to any web host, it’s all living on your Local app + your machine.

Would you be able to share your Local Logs with us? There are some different ways to access and share Local Logs. For us to be able to troubleshoot thoroughly, please click the Download Local Logs button from the Support tab in Local. This will generate a zip archive that contains the Local log along with some other diagnostic information to help quickly zero in on any issues that Local is encountering. (19.7 KB)

The website is knockout coffee, not ko coffee, that’s the remake of the website. At this point that website is already up to where the last website was so it isn’t exactly necessary to get the knockout coffee website back. But at the same time I wouldn’t want this to happen ever again, so it would be nice to know what caused it and how to fix it.

I appreciate your guys’ kindness

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.