[Bug]: 500 Internal server error about quivr HOT 3 CLOSED

Hey there, @atulgrover! I'm a bot designed to help you with bugs, questions, and becoming a contributor. I'm here to assist you while you wait for a human maintainer.

To resolve the 500 Internal Server Error and the ERR_INVALID_URL issues, you should ensure that the URLs being accessed are valid. Use the isValidUrl function to validate the URLs before making any requests.

Here is the isValidUrl function:

export const isValidUrl = (url: string): boolean => {
  try {
    new URL(url);
    return true;
  } catch (err) {
    return false;
  }
};

Additionally, check the middleware configuration in your server setup, as it might be affecting URL handling. The middleware configuration includes several middleware functions such as 'strapi::errors', 'strapi::security', 'strapi::cors', 'strapi::poweredBy', 'strapi::logger', 'strapi::query', 'strapi::body', 'strapi::session', 'strapi::favicon', and 'strapi::public'. Any of these could potentially influence URL handling ^[1].

Ensure your environment-specific configurations are correctly set up, as they could also influence URL handling. Key environment variables include NEXT_PUBLIC_BACKEND_URL, NEXT_PUBLIC_FRONTEND_URL, NEXT_PUBLIC_SUPABASE_URL, and NEXT_PUBLIC_CMS_URL ^{[2][3][4][5][6]}.

By validating URLs and checking your middleware and environment configurations, you can address the 500 Internal Server Error and ERR_INVALID_URL issues.

To continue talking to Dosu, mention @dosu.

from quivr.

TICK-36 [Bug]: 500 Internal server error

from quivr.

1.The "http://localhost:54321/" throws up {"message":"no Route matched with those values"}
2. I can access the "http://localhost:54323/project/default" supabase dashboard

from quivr.