Request failed with status code 404

[alexbsi]

Hi there,

It bugs me that, the first time always works. The second time I am getting: Request failed with status code 404, always.

Got same results with gpt-3.5-turbo and got-4.

Any ideas?

[dosubot[bot]]

Hey there, @alexbsi! Back for more adventures with our not-so-cooperative bots, I see. Let's see what we can do about this pesky 404 this time.

Based on the information provided, the "Request failed with status code 404" error indicates that the requested resource could not be found on the server. This error is not directly generated by the code within the pages/api/chat.ts file itself. Instead, it typically arises under the following circumstances:

1. Incorrect API Endpoint: The client-side code might be making a request to an API endpoint that does not exist. For example, if the client tries to fetch data from /api/chat but there's a typo in the URL or the server does not have a route handler defined for the requested path, it would result in a 404 error.

2. Server Configuration or Deployment Issue: If the server is not correctly configured or there's an issue with the deployment environment, requests to valid endpoints might still result in a 404 error. This could happen if the server is not properly routing requests to the Next.js application or if there's a misconfiguration in the deployment settings.

3. Dynamic Routes Misconfiguration: If the API route is supposed to handle dynamic segments (not applicable in the provided code but possible in general Next.js usage), and there's a misconfiguration in how these dynamic segments are handled or defined, it could lead to a 404 error when the expected route does not match any defined handlers.

The client-side code making the request to the /api/chat endpoint is located within the handleSubmit function in the pages/index.tsx file. Here's the relevant code snippet:

const response = await fetch('/api/chat', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    question,
    history,
  }),
});

If the error is consistently happening on the second attempt, it might be related to some state or data that is being changed or consumed during the first request. Without more information, it's hard to pinpoint the exact cause.

Could you provide more details about the exact error message or response body returned when the "Request failed with status code 404" error occurs? Also, is there any pattern or specific sequence of actions that triggers the "Request failed with status code 404" error on the second attempt? This information could help in identifying the root cause of the issue.

For reference, here are the sources:

• pages/api/chat.ts
• pages/index.tsx
• Request failed with status code 404

Sources

• Request failed with status code 404
• pages/api/chat.ts
• pages/index.tsx

About Dosu

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.