whats your trouble? I only see 500 from the api?

maybe it reading orther file but that file isn't loading data from lib. you can check infor more about error.

/api/callpredict or /api.callpredict ?

No, the api works fine....just doing page refresh, everything works


I am guessing this could be cache issue, but already added force-dynamic to api, still same issue

for me all apis are working with / only, havn't tried .

what is this TCP fetch failed error for?

No I mean you said on your post /api.callpredict/ but on the console its /api/callpredict/

so just double checking first if it's the correct route

ahh, that's typo

I have corrected it. It was typo here

https://github.com/vercel/next.js/issues/56005


I found this, but no solution

Does the samething happen locally or just prod/deployed?

Have you used a try catch in the route and logged the error?

What version of Next are you running, if it's the cache then it's enabled by default on fetch on versions prev 15.

It happens both locally (attached local screenshot) and prod.

This happens when opening the website, refreshing the page works fine.

That route is different issue, yes there is try catch but not error, it's actually not reaching to the route itself. This one happens in prod only.


Next version, 13.4.19

That api route issue happened again just now on production website on another route

same logs

Same....on prod with no logs

refreshing solves it

I'm getting the issue on endpoint https://cloth2life.ai/webapp/product/create

It's expecting JSON, but it's returning a 500 page. Thats why you get this error in particular

That's probably as far as I can go for diagnosing this issue without seeing code.

can you try refreshing the page and try the api again

it will work

that's where it is becoming difficult for me to diagnose

Have you any middleware

The error could be thrown in there

have logs in aws and just added sentry too

nothing else apart from these

Try removing the middleware in local - keep refreshing etc to see if the bug occurs again.

I have a feeling it might be middleware

can you help?

I can share screen 🙏🏻

Unfortunately, I cannot 😦

I don't have much time availablee

okay

let me keep trying

if you find something of interest

or maybe post here snippets of the route and any middleware

yeah

Here's the code for one of the api route:

import { NextResponse } from "next/server";

async function generateA() {
    const letters = "ABC"

    return letters;
}

export async function POST(request) {

    try {
        const formData = await request.formData();
        // console.log("----149 formData", formData);

        const WordA= await generateA();

       
        let body = {
            id: formData.get('id'),
            WordA: WordA,
        };

        const requestBody = {
            "body": body
        }

        const resp = await fetch(process.env.NEXT_PUBLIC_API, {
            method: 'POST',
            headers: {
                'Content-Type': 'application/json',
            },
            body: JSON.stringify(requestBody),
        });

        const responseData = await resp.json();

        return NextResponse.json({
            resp: responseData,
            success: true,
        }, { status: 200 })


    } catch (error) {
        console.log("---error in api", error);
        return NextResponse.json({
            error: "Error t api " + error
        },
            { status: 500 })
    }
}


export const dynamic = "force-dynamic";

could it be because

export const dynamic = "force-dynamic";

should be on top?

Next dynamic doesn't have to be at the top it's fine.

First, you need to check if ID is correctly received (non-error related):
id: formData.get('id')

Without nit picking but you could refactor it quite a bit:

  
        let body = {
            id: formData.get('id'),
            WordA: WordA,
        };

        const requestBody = {
            "body": body
        }

But I just tried to do GET on your route, then got the 500.

Then after I got the 405 (which is your route is POST).

Which means, the error has to occur before the function is called.
You need to look at your middleware.

Exclude the api route from the middleware: /((?!api|login|_next/static|_next/image).*) and then see if you still get the issue.

We don't have any middleware.js file at all in our project

You need to see what is being called or what is breaking it, it's something either Global server side, or executing before the routes.