Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x" error on deployment

i want to add the working approach. above comment also a working approach. but it was not described enough with resources.

so, here it goes. in my case, this is how i solved vercel prisma rhel issue.

• prisma version 6.7.0 (6.6.0 may works too)
• you can not use new prisma client generator (prisma-client)

here i provide all the code step by step.

in schema.prisma

generator client {
  provider      = "prisma-client-js" // here do not use the new client (prisma-client)
  binaryTargets = ["native", "linux-musl", "rhel-openssl-3.0.x"]  // first one is for cross-platform, second one for docker, last one for serverless environment. safe to include all
  output        = "../src/generated/client" // it is better to include the generator inside `src/` or `app/` if `src/` not available.
}

install this package. go to npm repo and update next.config.mjs like above docs. but here is my full code of next.config.mjs

import { PrismaPlugin } from "@prisma/nextjs-monorepo-workaround-plugin";

/** @type {import('next').NextConfig} */
const nextConfig = {
    devIndicators: false,
    experimental: {
        authInterrupts: true,
    },
    webpack: (config, { isServer }) => {
        if (isServer) {
            config.plugins = [...config.plugins, new PrismaPlugin()];
        }
        return config;
    },
};

export default nextConfig;

then run bunx prisma generate or npx prisma generate

my package.json scripts used on vercel build

"scripts": {
    "dev": "next dev --turbopack",
    "vercel-build": "bunx prisma generate && bun run build",
    "build": "next build",
    "postinstall": "bunx prisma generate"
  }

then vercel build command was bun run vercel-build

I made some progress. So I created another page at /prisma-check and it has

import prisma from "@/lib/prisma";
import React from "react";

const PrismaCheckPage = async () => {
  const user = await prisma.user.findMany();
  return (
    <div>
      <h1 className="text-3xl font-bold">Prisma Check</h1>
      <p className="text-lg">User Count: {user.length}</p>
      <ul className="list-disc pl-5">
        {user.map((u) => (
          <li key={u.id}>{u.email}</li>
        ))}
      </ul>
    </div>
  );
};

export default PrismaCheckPage;

and suddenly it works. But without this page, the form at the /contact route does not work

export async function addContactFormToDB(
  values: z.infer<typeof contactFormSchema>
) {
  try {
    // --- Rate Limiting Check ---
    const ip = await getIP(); // Get the user's IP address
    const rateLimitResult = await rateLimitContact(ip);

    if (!rateLimitResult.success) {
      return rateLimitResult; // Return the rate limit error message
    }
    // --- End Rate Limiting Check ---

    // Proceed with validation and database operation if rate limit not exceeded
    const zodResult = contactFormSchema.safeParse(values);
    if (!zodResult.success) {
      // Log validation errors for debugging if needed
      console.error("Form validation failed:", zodResult.error.flatten());
      return {
        success: false,
        // It's often better to give a generic message unless you map errors
        message: "Invalid form data. Please check your entries.",
      };
    }

    // Use the validated data from zodResult.data
    const validatedData = zodResult.data;

    await prisma.contactForm.create({
      data: {
        name: validatedData.name,
        email: validatedData.email,
        phoneNumber: validatedData.phone ?? "", // Ensure 'phone' exists in your validated data
        message: validatedData.message,
      },
    });
    return {
      success: true,
      message: "We've received your request and will get back to you soon.",
    };
  } catch (error) {
    // Log the actual error on the server for debugging
    console.error("Contact form submission error:", error);

    // Return a generic error message to the client
    return {
      success: false,
      message:
        "Failed to submit the form due to a server error. Please try again later.",
    };
  }
}

this is contact form submission action that does not work without the prisma check page. I have no idea why it is resulting in an error without prisma check page, and works with the prisma check page that has no relation to the action whatsoever.

I was trying to deploy a monorepo to Vercel, I got this error. I tried adding

binaryTargets = ["native", "linux-musl", "rhel-openssl-3.0.x"]

in the generator section of the prisma schema file but no luck.

Here's what worked for me: https://www.answeroverflow.com/m/1366677484229230622

It involves using the @prisma/nextjs-monorepo-workaround-plugin package.

I ran cd apps/web then i ran pnpm install @prisma/nextjs-monorepo-workaround-plugin then when it was done, i edited my next.config.mjs file.

Here's my next.config.mjs file:

import { PrismaPlugin } from '@prisma/nextjs-monorepo-workaround-plugin'
/** @type {import('next').NextConfig} */

const nextConfig = {
  transpilePackages: ["@workspace/ui"],
  webpack: (config, { isServer }) => {
    if (isServer) {
      config.plugins = [...config.plugins, new PrismaPlugin()]
    }
    return config
  },
}

export default nextConfig