mikejw

Closed as per comment this comment https://github.com/gatsbyjs/gatsby-starter-shopify/issues/57#issuecomment-1004145877, which states the code should be run with a node process (npm run serve) on a VPS.

I'm reopening this ticket as I'm noticing these errors still appear when using `gatsby serve` behind a proxy. i.e. nginx. There are errors that prevent the search page from loading...

My understanding is that '/search' is now server-side rendered. I'm curious to know how this should be deployed on a manual deployment and not using Gatsby cloud!

Maybe `gatsby serve`

I'm not having this issue with the back button (when using `gatsby serve`). However I've noticed that I can't use a frontend proxy (like nginx) it always returns a 404...

If I do a `gatsby build` and deploy those files then `/search` still 404s.

> > If I do a `gatsby build` and deploy those files then `/search` still 404s. > > Keep in mind, if you aren't deploying to Gatsby Cloud, you are...

I managed to get the stock status by using the client object with the product listing component and looping through each product. Happy to share the code if anyone is...

By the way we are using a custom token provider as outlined here (even though the token comes from Cognito): https://docs.amplify.aws/javascript/build-a-backend/auth/advanced-workflows/#custom-token-providers

I'm still getting this kind of response from the `graphql` endpoint. NB: This is for path syncUsers, createUser and updateUser. ``` { "data": { "syncUsers": null }, "errors": [ {...