Hi @eben-bealcoza!

Welcome to the Vercel community! It's great to have you here and we're glad that you're enjoying using Next.js and Vercel

Usually the 308 Permanent Redirect indicates that the request is being redirected, likely due to misconfiguration of the domain settings or the Next.js API routes. To help troubleshoot, here are some things to try:

• Verify your domain settings - how have you set it up?
• Do you have a next.config.js configured? Make sure it's properly configured handle API routes. A good example:

1
module.exports = {
2
  async redirects() {
3
    return [
4
      {
5
        source: '/api/:path*',
6
        destination: '/api/:path*', 
7
        permanent: false,
8
      },
9
    ];
10
  },
11
};

• Do you have any rewrites configured that could be causing this?
• You can use tools like cURL or Postman to test your API endpoint directly. This can help you verify if the issue is with the endpoint itself or with the way the request is being made from the client-side.

Those are just starter points to try out! I'll also leave this open for any community members who may be able to help.

Hi @pawlean , Thank you for the response. I have an next.config.mjs file and will configure it there. Assuming this is the correct place.

Hi @pawlean,

There should not be a redirect. I am making use of the route handlers. I make use of the following structure:

src/app/api/bookings/route.ts which should give me the endpoint domain/api/bookings according to the nextjs docs > https://nextjs.org/docs/app/building-your-application/routing/route-handlers

This works locally but not on the server.

I am making use of paw to test the endpoints locally and on vercel. Locally they return as expected but on vercel they are redirected and then eventually time out. I've updated the timeout to be 20s.

What else could I be missing?

Some update here...

1. The redirect came from me making a post to the http endpoint instead of the https one.. FML
2. I am now running into a timeout which is expected as the hobby default is 10s. Will update it to 60s now and likely get the pro subscription.

Issues have been resolved. I updated the timeout to be longer and making posts now to the https endpoints and it all works.

Thanks for coming back here and sharing your solution, @eben-bealcoza!

Would love to see what you're building, feel free to come back here and share it with the rest of the community if you want.