Ive updated Local to the latest version and none of my sites function anymore, all returning a 502 Request error. No matter how many times I restart Local or refresh I can no longer access my sites and I have quite a few set up. I was going to try downgrading local but there are only mac instructions on how to do this without losing all of my sites etc.
What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc
System Details
Local Version:
Local Version 9.1.1+6738
Operating System (OS) and OS version:
Windows 11 23H2
Local Logs
Attach your Local Logs here (Help Doc - Retrieving Local’s Log)
Looking into the logs I see the same error anytime I try to access a site:
024/12/04 12:41:13 [error] 26052#27680: *1 upstream sent “Content-Length” and “Transfer-Encoding” headers at the same time while reading response header from upstream, client: ::1, server: xyz.local, request: “GET / HTTP/1.1”, upstream: “http://[::1]:3000/”, host: “xyz.local”
2024/12/04 12:41:13 [warn] 26052#27680: *1 upstream server temporarily disabled while reading response header from upstream, client: ::1, server: xyz.local, request: “GET / HTTP/1.1”, upstream: “http://[::1]:3000/”, host: “xyz.local”
Security Reminder
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.
Are you using Instant Reload? If so that could be the source of the issue and you’ll want to make sure you also update that Add On to the latest release as well.
Welp, Im feeling pretty dumb because sure enough, removing that extension fixed the problem. I guess I didn’t understand that part of the ecosystem.
I did not see an easy way to “update” the extension so I just deleted it and all my sites are working now. This issue is resolved with that suggestion. Thanks Nick.
We actually had a recent bug with Instant Reload that was causing that issue and the fix was included in the recent release. So, if you want to use it again, you should be good to do so. You’ll just want to make sure you update that add-on as well. Or if you’ve removed it completely when you reinstall it should be up to date, but you can find more info here:
