Thanks for the info and logs, @DavidG. These lines from your nginx logs point to a possible add-on issue:
upstream prematurely closed connection while reading response header from upstream, client: ::1, server: [redacted].local, request: "GET /browser-sync/socket.io/?EIO=3&transport=polling&t=P2V7hqB&sid=qNh83Y1Q4333Rj57AAAc HTTP/2.0", upstream: "http://127.0.0.1:3003/browser-sync/socket.io/?
upstream sent "Content-Length" and "Transfer-Encoding" headers at the same time while reading response header from upstream
Are you using Local’s Instant Reload add-on? If so, please could you check it’s the latest version (1.1.4)? We fixed an issue in 1.1.4 that could result in 502 responses accompanied by those errors in nginx logs. (Note that the current version is displayed on the “installed” tab, not the “library” tab: Instant Reload 502 error - #34 by nickc )
If you’re using a lower version than 1.1.4 and don’t see an update notice, you could try removing the add-on and re-installing it. (You could also try disabling it if you no longer need it.)
I reset all my local and modem DHCP DNS to Cloudfare’s 1.1.1.2/1.0.0.2…
I also tried turning Bitdefender off.
After doing the above I was able to run the auto update for Local. I’m guessing changing my DHCP DNS helped here.
That’s good to hear! It sounds like either Bitdefender or your DNS configuration were blocking Local’s update server.