404 on the other routes I created in my Node.js express app

[davepaurillo]

I followed the documentation about deploying express on vercel and was able to deploy the app successfully. However, when I added some other routes, I cannot access it.

This is my current folder structure.

The “/” route inside the index.js is fine. The problem occurs when I use express Routers.
I’ve created a route in index.js (“/api”) to look up to main.route.js that looks up to the controllers.

I am getting a 404 Not Found when accessing the supposed route (“/api/auth/register”). Is there something I need to add on my vercel.json? I only added what I saw on one of the answers here:

{ "version": 2, "rewrites": [{ "source": "/(.*)", "destination": "/api" }] }

or is there anything else I am missing?

[system]

There’s another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes.

Debugging 404 Errors

Sometimes things don’t go as expected when deploying a website. If you see a 404 on your site, that means the page or resource couldn’t be found. There are many possible causes, and the absence of something can be tricky debug if you don’t know where to look. Here are some things you can do to find the cause and fix it. Debugging Tips Check the error code If you see a mostly white screen with 404: NOT_FOUND along with a Code and and ID then you can click the blue info box below the error deta…

A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

If you’re having trouble deploying an Express app, this guide can help.

How to Deploy an Express.js Application to Vercel

You can also ask v0 for suggestions tailored to your own project setup.