I’m currently attempting to deploy my Next.js SSG application to the same droplet that my backend graphql api is hosted on. The api sits at /graphql while the app sits at /app but when I navigate to /app I get a loading… page with console showing the server is "404"ing the page.
I’m not getting any errors on the Next.js side of
npm run build and
npm start or with pm2 in actually starting the website. It’s clearly pulling from the next.js app as some of the resources its failing to grab are _app.js which is the root file for my next.js app.
I thought it might be an environmental variable thing but I have the same next.config.js file as my local version on the server and my local version works in both dev and production mode.
Any help on this would be greatly appreciated.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Solved the problem it turns out that I hadn’t properly set up the express server to operate on the correct root it was / and it should’ve been replaced with /api
Hi there @milorue,
Can you share the exact Nginx Server block that you are using for your setup? I could then try to advise you further.
Also what I could suggest is checking your Nginx error log for any errors that could provide you with more information:
Want to learn more? Join the DigitalOcean Community!
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
Sign up now