502 Error on JS front end after Atlas install

I am trying to give the Atlas/Headless WP environment a spin but struggling to get it running on my machine (Windows 11).

Using a completely fresh installs with both the Scaffolding and Portfolio blueprint the JS front end just shows a 502 error.

The WP backend and the DB definitely work, but the server log on NGINX has the following:

[error] 25000#11692: *9 WSARecv() failed (10054: An existing connection was forcibly closed by the remote host) while reading response header from upstream, client: ::1, server: headless.local, request: “GET / HTTP/1.1”, upstream: “http://127.0.0.1:10129/”, host: “headless.local”
[error] 25000#11692: *9 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: headless.local, request: “GET /favicon.ico HTTP/1.1”, upstream: “http://127.0.0.1:10129/favicon.ico”, host: “headless.local”, referrer: “http://headless.local/

I’ve seen similar topics on here blame Windows Defender for this, but from what I can see local.exe is allowed through the firewall there.

I’ve also updated node and npm via the terminal, and this doesn’t seem to make any difference.

Any help would be appreciated.

Cheers
Jack

Hey @jackmach125

We would be happy to assist with your Local troubleshooting! Could you provide some more details to help us take a further look?

  • What version of Local are you on?

  • Please attach a copy of your Local Logs

Keep us posted and we’d be happy to help further!

Local Version 6.70+6347
local-logs.zip (130.2 KB)

Hi,
I have the exact same problem with my new install.
How did you resolve this?

I didn’t, just moved on as it’s clearly not ready for production.

Hi @Dennis-L

Can you try changing your router mode to see if that helps?

Preferences>Advanced>Router Mode

Thought I’d revive this thread since I’m having the same issue, and haven’t found a reliable answer in other threads so far.

I did try changing the router mode but I ended up with the browser not being able to connect to anything at all:

I am also noticing that while the Atlas site is running, two command prompt windows continually open and close, no text or logging or anything in them, just blank command prompt windows. I do see

I thought initially that maybe because I installed Local in a custom location, on a second drive, that it caused issues with Node or something, but I reinstalled Local at it’s default location and still encountered the problem.

Hoping someone has found a solution for this since the last time this thread was updated…

Hi @jenoble20! Could you share your details like the ones requested here for us?