I wanted to inspect the different Atlas blueprints, to see what I can learn from them.
But when I successfully install any of the blueprints, upon visiting the front-end I am immediately seeing errors with GraphQL in the output console. When trying to open up a single post, I am given a 404 error. This is without changing any settings in either Local, WordPress or the disk files.
The messages I’m seeing in the console are: [GQtyError: request to http://localhost:10490/graphql failed, reason: connect ECONNREFUSED ::1:10490] { type: 'system', errno: 'ECONNREFUSED', code: 'ECONNREFUSED' }
I am not seeing these same errors when creating an Atlas environment from scratch.
I just noticed that when I’m changing ‘web server’ in Local to Apache (instead of nginx), the errors are gone. When changing back to nginx, they return.
Hi @ProxxiM - thank you for bringing your question to the Local Community!
Can you describe your workflow for setting up a new site in Local with an Atlas blueprint?
Are you following the steps here?
Where are you changing the web server to Apache? A screenshot or screen-recording would be very helpful (you can use Loom to create a screen-recording for free).
Here’s a screen capture of how I create the environment.
You will see that after creation, I can’t see various images and I can’t open various pages.
After changing to Apache in Local, everything seems to work fine.
