Ok, we got half an error telling us absolutely nothing except that a server-side error occurred on what ever server you are trying to send a request to. What should we do now?

Context?

I use API With Open Ai

Alright. We need to see the code for /app/api/conversation/ then

Give me another error

No, the code that handles the /api/conversation route

404

What?

i think he got 404 error code

You weren't supposed to change it

Look

Give me another error

@torquiii can we see /api/conversation route's code?

You have a Next.js app. This app consists of code. The route you are trying to request (/api/conversation) has code as well to handle the request you make to it. I want to see that code

Wait

I can't really ready any of that

Can you just copy and paste the code?

its really? please use discord on desktop...

that camera photo...

Okii

and we really cant see the routes

import { auth } from '@clerk/nextjs';
import { NextResponse } from 'next/server';
import { Configuration, OpenAIApi } from 'openai'


const configuration = new Configuration({
apiKey: process.env.OPENAI_API_KEY,
})

const openai = new OpenAIApi(configuration)

export async function POST(
req: Request
) {
try {
const { userId } = auth()
const body = await req.json()
const { messages } = body


if (!userId) {
return new NextResponse('Unauthorized', { status: 401 })
}

if (!configuration.apiKey) {
return new NextResponse('OpenAI API Key not configured', { status:
500 })
}

if (!messages) {
return new NextResponse('Messages are required', { status: 400
})
}

const response = await openai.createChatCompletion({
model: 'gpt-3.5-turbo',
messages
})

return NextResponse.json(response.data.choices[0].message)
} catch (error) {
console.log('[conversation_ERROR]', error)
return new NextResponse('Internal error', { status: 500 })
}
}

What does your console say? (Not the browser one)

** Page 2**

you need use /api/conversation. if you get error code then openai not configured , or you got internal error. (see the code)

Wait a second

/app/api/conversation replace to /api/conversation

Not the browser one

Okii

Okii bro

Gave the same error as the first 500

We know

yes , see the code.

if the code got error you get error code 500

what the console says?

in browser

we need more information

Show us the console output of the console you started the Next.js app with. So the one you typed npm run dev into

I use yarn

Then that

Man.

But there should be something inside your non-browser console

Its.

I see the problem in axios

Most likely starting with "[conversation_ERROR]"

The problem is not axios

axios is working fine

I went on the hunt to find your console. Looks like you are rate limited form the API

So you made too many requests in a short time

you have try catch. In the try part have a bad code. We cant know wheres the problem. Its not problem of routing. We need to know what the output the response.data.choices[0].message.

yape.

its the try failed to running jumped to catch and you got response data to error code 500.

Look AxiosError

No, you have another console open. Show that one

So what is the solution now

On the right side of your console, there are two windows. The top one is your actual console and it probably says "429"

ohh man..

my soul is broken now

first of all check in part of "try" check all variable, wheres is the error

wheres wrong

if you put the code github

i will help you

Yes

...

Wait a minute, what's your name in github

You are rate limited from the OpenAI API. Case closed, someone close this thread please

go to the dm manxd

What do you mean

What do you mean

You made too many requests to their API

So they temporarily locked you out

You have to wait until they let you make requests again

There's no fix you can do from your side besides waiting

Because of this there is a 500 error

Yes

Because your try catch fails and therefore returns a 500 error

As you told it to

yes

I think yes now I used a lot of API

Then try again later

If you use an account gmail new And I got a new API Will the problem open?

No, because your API key stays the same and that's the thing the API identifies you with

+1

Just wait. Eat something, watch a movie, whatever and then try again

+ 1

and have to chance you flooding the request to the api

I mean, this is the solution

pretty good solution if you ask me

what is true /api/conversation or /app/api/conversation

First one

/api/conversation

Thank you my friend for you and your time zorty💪👌

you're welcome man. have a nice day.