vercel / platforms

A full-stack Next.js app with multi-tenancy and custom domain support. Built with Next.js App Router and the Vercel Domains API.
https://app.vercel.pub
5.58k stars 725 forks source link

404 error on all three sites with custom domains applied #421

Open joshualinog opened 1 month ago

joshualinog commented 1 month ago

the problem

image with the ID: xxxxxxxxxxxxxxxxxxxx,etc.

the domain has the suggested A record

image

and the suggested cname record

image

Rudrakaniya commented 1 month ago

I am getting this same issue, Following the guide Next.js Platforms Starter Kit guide resulted in 404 for me. Cannot even see any error, Can someone please help?

joshualinog commented 1 month ago

i now have mine working the way i want, although i don't think its what the repo is intended to do. @Rudrakaniya could you provide some more specifics about where you are in setting it up? what is the state of your repo? what step are you on in the guide?

Rudrakaniya commented 1 month ago

I have deployed this repo using Vercel's deployment template. I set up all the required environment variables, but I am unable to open any page; all the pages are giving a 404 error. I tried running it locally as well, and I am able to open the login page at 'http://app.localhost:3000/login,' but it doesn't authenticate the user or allow access to the app. I am not sure what is wrong, trying to debug..

joshualinog commented 1 month ago

I have deployed this repo using Vercel's deployment template. I set up all the required environment variables, but I am unable to open any page; all the pages are giving a 404 error.

I tried deploying this repo with vercel's deploy this template functionality and it broke and did not work properly. I then started from scratch with the guide and was able to get it working.

I tried running it locally as well, and I am able to open the login page at 'http://app.localhost:3000/login,' but it doesn't authenticate the user or allow access to the app. I am not sure what is wrong, trying to debug..

  1. have you done this part?:
  1. what is the state of your .env file locally?