Deploying on Vercel gives 404 on /admin

[modulareverything]

Hey, brand new to Payload here so please bear with me

I've been testing it out locally and I've been enjoying it. I've managed to set up a database using Mongo Atlas and I'm now trying to deploy my little experiment to Vercel where I'd ultimately look to host sites like these.

The database connects, the site deploys without issue and I'm able to see the frontend (the Next.js part) of my site at this URL:

removed

However, when I try to go to the admin area, here:
removed

If I try the /admin URL locally, it works absolutely fine.

Am I missing a step here?

Edit: It might be useful to include my Vercel build log:

[16:46:06.058] Running build in Washington, D.C., USA (East) – iad1
[16:46:06.179] Cloning github.com/Modular-Everything/gardx-asset-library (Branch: main, Commit: dff45ad)
[16:46:06.189] Skipping build cache, deployment was triggered without cache.
[16:46:07.351] Cloning completed: 1.171s
[16:46:07.617] Running "vercel build"
[16:46:08.108] Vercel CLI 33.5.0
[16:46:08.446] Installing dependencies...
[16:46:08.794] yarn install v1.22.17
[16:46:08.871] [1/4] Resolving packages...
[16:46:09.293] [2/4] Fetching packages...
[16:46:43.780] [3/4] Linking dependencies...
[16:46:43.784] warning "@payloadcms/bundler-webpack > [email protected]" has unmet peer dependency "@swc/core@^1.2.147".
[16:46:43.785] warning "@payloadcms/bundler-webpack > [email protected]" has unmet peer dependency "@swc/core@^1.0.0".
[16:46:43.798] warning "payload > [email protected]" has unmet peer dependency "webpack@^5.20.0".
[16:46:43.800] warning "payload > [email protected]" has unmet peer dependency "webpack@^5.1.0".
[16:46:43.842] warning Workspaces can only be enabled in private projects.
[16:46:55.102] [4/4] Building fresh packages...
[16:46:59.884] Done in 51.09s.
[16:46:59.921] Detected Next.js version: 14.1.0
[16:46:59.922] Running "yarn build"
[16:47:00.117] yarn run v1.22.17
[16:47:00.138] $ cross-env NODE_ENV=production yarn build:payload && yarn build:server && yarn copyfiles && yarn build:next
[16:47:00.408] $ cross-env PAYLOAD_CONFIG_PATH=src/payload/payload.config.ts payload build
[16:47:22.480] $ tsc --project tsconfig.server.json
[16:47:25.515] $ copyfiles -u 1 "src/**/*.{html,css,scss,ttf,woff,woff2,eot,svg,jpg,png,js}" dist/
[16:47:25.876] $ cross-env PAYLOAD_CONFIG_PATH=dist/payload/payload.config.js NEXT_BUILD=true node dist/server.js
[16:47:28.714] Attention: Next.js now collects completely anonymous telemetry regarding usage.
[16:47:28.715] This information is used to shape Next.js' roadmap and prioritize features.
[16:47:28.715] You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
[16:47:28.715] https://nextjs.org/telemetry
[16:47:28.715] 
[16:47:28.817]    ▲ Next.js 14.1.0
[16:47:28.817] 
[16:47:28.864]    Creating an optimized production build ...
[16:47:29.164] [16:47:28] �[32mINFO�[39m (payload): �[36mConnected to MongoDB server successfully!�[39m
[16:47:29.166] [16:47:28] �[32mINFO�[39m (payload): �[36mStarting Payload...�[39m
[16:47:29.166] [16:47:28] �[32mINFO�[39m (payload): �[36mPayload Admin URL: /admin�[39m
[16:47:29.166] [16:47:28] �[32mINFO�[39m (payload): �[36mNext.js is now building...�[39m
[16:47:40.207]  ✓ Compiled successfully
[16:47:40.208]    Linting and checking validity of types ...
[16:47:40.573]  ⨯ ESLint: Failed to load config "@payloadcms" to extend from. Referenced from: /vercel/path0/.eslintrc.js
[16:47:44.521]    Collecting page data ...
[16:47:45.641]    Generating static pages (0/6) ...
[16:47:45.697] 
   Generating static pages (1/6) 
[16:47:45.881] 
   Generating static pages (2/6) 
[16:47:45.882] 
   Generating static pages (4/6) 
[16:47:46.055] 
 ✓ Generating static pages (6/6) 
[16:47:46.652]    Finalizing page optimization ...
[16:47:46.652]    Collecting build traces ...
[16:47:53.612] 
[16:47:53.615] Route (app)                              Size     First Load JS
[16:47:53.615] ┌ ○ /                                    19.6 kB         104 kB
[16:47:53.615] ├ ○ /_not-found                          885 B          85.1 kB
[16:47:53.616] └ λ /api/hello                           0 B                0 B
[16:47:53.616] + First Load JS shared by all            84.2 kB
[16:47:53.616]   ├ chunks/69-156889eed8cbb45e.js        28.9 kB
[16:47:53.616]   ├ chunks/fd9d1056-608fb00f5228e2fe.js  53.4 kB
[16:47:53.616]   └ other shared chunks (total)          1.9 kB
[16:47:53.616] 
[16:47:53.616] 
[16:47:53.616] ○  (Static)   prerendered as static content
[16:47:53.616] λ  (Dynamic)  server-rendered on demand using Node.js
[16:47:53.616] 
[16:47:54.286] Done in 54.17s.
[16:47:54.389] Traced Next.js server files in: 65.692ms
[16:47:55.580] Created all serverless functions in: 1.190s
[16:47:55.587] Collected static files (public/, static/, .next/static): 3.79ms
[16:47:55.616] Build Completed in /vercel/output [2m]
[16:47:55.746] Deploying outputs...
[16:48:11.124] 
[16:48:11.411] Deployment completed
[16:48:24.053] Uploading build cache [165.75 MB]...
[16:48:29.656] Build cache uploaded: 5.603s

[hasanshahriar32]

hi, did you resolved the admin path support at vercel?
i am getting 404 at vercel deployed /admin path

TIA

[modulareverything]

Have a look at this

[DanRibbens]

I know that some people have Payload running on Vercel, but until we have v3 this isn't officially supported.

You can try the alpha release of v3 right now. Here is the repo: https://github.com/payloadcms/payload-3.0-alpha-demo

We're working towards a beta release of 3 which should be pretty stable.

[rjdjohnston]

Any tips on how those people were able to get it deployed?

[modulareverything]

@rjdjohnston I was able to get it deployed using next-payload but it seems like that repo has been archived and the link it points to no longer exists.

I can only assume the suggestion is to now use the beta version of Payload 3.0 — I read somewhere that now it's out of alpha it should be stable enough to use, but I can't remember where I read this.

[6ui11em]

I just deployed the latest beta version of Payload to Vercel and I also have the 404 error problem when trying to access /admin.
Locally it works fine in both dev mode and build / start.
The Vercel deployment logs don't give any errors, it looks like everything is fine but when trying to access the application it returns 404.

[rajuNestfindr]

Hey Did you find the solution for this?

[6ui11em]

I got it to work by deploying directly from the vercel-postgres template:

https://github.com/payloadcms/payload/tree/beta/templates/with-vercel-postgres

You click on the deploy button and it works. I'm interested that it works with SQLlite, I haven't been able to test with that yet.

[rajuNestfindr]

Thank you. I have moved to payload v3 which is compatible with monogo-vercel. It is working good so far.
just for info They have launched the v3 stable version as well.