Error validating datasource db : the URL must start with the protocol postgresql:// or postgres://

[mabdullahadeel]

I am trying to run simple migration using prisma migrate dev. I have my .env file set up in the root directory of my application.

DATABASE_URL="postgresql://<postgres>:<postgres>@localhost:5432/<databasename>?schema=public"

I have defined the DATABASE_URL in my .env file. But when I try to run migrations, I am getting the following logs.

Environment variables loaded from .env
Prisma schema loaded from prisma\schema.prisma
Error: Get config: Schema Parsing P1012

error: Error validating datasource `db`: the URL must start with the protocol `postgresql://` or `postgres://`.
  -->  schema.prisma:10
   | 
 9 |   provider = "postgresql"
10 |   url      = env("DATABASE_URL")
   | 

Validation Error Count: 1

I have tried:

• Downgrading the versions to @prisma/cli@3.8.1 prisma@3.8.1
• moving .env file to ./prisma/.env

[isNan909]

I also faced the same issue. I rechecked the connection string generated from free Postgres instance of Heroku, did not help.

I rechecked on changing it to local DB nothing helped. I do have repo of this.

But I really don't know how to reproduce this issue.

[DavidEGonsalves]

I'm running into this exact error. Can you tell me where you placed your workaround? In schema.prisma?

Thanks!

[Anupkp19]

this worked
Thanks

[jarrodmedrano]

This won't work for me because I need to generate.

[meAasifAli]

i did this but server is throwing me another error the URL must start with the protocol prisma:// then when i added this then it is throwing me another error url must have a valid api key

[rakshittt]

can you tell me , where to add this line of code. I am facing the same error

[juanitoddd]

I was having the same issue, having prisma inside a Docker Container.
I realize I had set env variable DATABASE_URL inside my docker-compose.yml so, the .env was being override.
I know is kind of stupid, but maybe your DATABASE_URL env variable is being override without you noticing it.

[mabdullahadeel]

But the thing in my case was if I set DATABASE_URL to a mysql db, everything worked. I was just facing the problem with postgres

[hkrhasan]

I also face the same issue 😞

[zisra]

Still doesn't fix it for me

[MuksithMRA]

Thanks bro it worked

[ajfahim]

this worked for me.

[ayoubshah2720]

This also worked for me.

[subrotoice]

DATABASE_URL = "mysql://root:@localhost:3306/issue-tracker"; - Not Working
DATABASE_URL = "mysql://root:@localhost:3306/issue-tracker" - Working

[rhinodavid]

I had this problem while working with the next-auth demo repo. The problem ended up being a second declaration of DATABASE_URL at the very bottom of the .env file.

[seanlowe]

My issue was, like this, being caused by a second declaration of DATABASE_URL.. except mine was in my .env.example file.

[joeydotdev]

Ran into this similar error but only in the context of a production box and not local.

My issue was that my environment variable was in the format of DATABASE_URL='connectionstring' instead of DATABASE_URL=connectionstring. After I changed to the latter, connections were succeeding.

[Fritiof]

This solved it for me! THANKS. Can't believe that's a problem tbh

[lorenzocesconetto]

THANK YOU! Omg this bug is so annoying

[sorenowy]

This is gold. Many thanks!
I had stuck multiple times on providing data via ' ' - but i simply didn't noticed that in docs.

[maag070208]

THANK YOU!!!!!!!!!

[teetangh]

This solved it for me as well. Sometimes(like in my case) special characters in username/password could also be posing a threat. So try to keep things simple and get project working. Once the prototype is working, you can make the creds harder.

[raverecursion]

If you recently swapped your DATABASE_URL, make sure you run npx prisma generate then try it again

[d3r3nic]

I simply re-ran my pipeline and since the pipeline runs npx prisma generate when building, it fixed my issue.
very odd error! a very simple solution that no one would think about!
thank you

[theborowski]

Thanks! This helped me out as well. At first I thought it was also related to the answers above with using quotes but I just had to regenerate.

[safwansamsudeen]

Insane, man. Thanks so much!

[RobsonTorres]

Obrigato. Isso resolveu o meu problema, ótima dica.

[oota-bear]

※I'm sorry if it's a strange English because I'm translating it into English with google translate.

I had the same error, but I resolved it, so I'll post it here.

①There are two prisma.schema files, and the prisma described was wrong
→Project created in ”furourio”.
because 「server/prisma/prisma.schema」「prisma/prisma.shema」two prisma.schema file exist.
i was fixing 「server/prisma/prisma.schema」 but 「prisma/prisma.shema」

Also, prisma/prisma.shema」 did not have 「.env」, so it was created and migrated successfully

[DavidEGonsalves]

This is very similar to what happened to me. I'd created my project in the same folder as a school project I was using as an example. Prisma's smart enough to search up through the directory tree & find the .env file from the school project (which was using PostGresSQL & not MySQL). My clue came in the error message when it said that it was reading two .env files, one in the local \prisma\ directory, and another in the ../ directory. That's when I figured out that the actual error was two conflicting .env files. The Prisma error message could have been better, it just kept telling me that "mysql" had to be the database string, not that there were two database strings it was trying to resolve. Anyway, I've figured out my problem, and hopefully this (and your solution) will help someone down the road.

Thanks for the reply, I appreciate it, and Google translate did a pretty good job.

[oota-bear]

Thanks for your reply.
It's hard to understand which .env is related to which...
I'm happy to be of some help！

[michaelwell23]

Importing the 'dotenv-safe/config inside the jest.config file is what worked for me.

`require('dotenv-safe/config')
const { exec } = require('child_process')

process.env.DB_URL = ${process.env.DB_URL}_testdb?schema=test_schema

exec('yarn db:migrate')
`

[theodore-zd]

I had this exact issue today, in a nextjs project using next-auth and postgres as my db after double checking it wasn't something silly like a spelling error, removed my .next folder and all contents, ran next dev and it starting working no problem.

Hope this helps 👍🏻

[ELORCHI]

I had the same problem today. what i found is that prisma tried to read the env variable from the os exported env variables, because i added the .env to my docker-compose.yml. the solution i found is unseting the env DATABSE_URL after an exec into the container.
the weird thing here is that the two env variables either from the .env or from the os env variables are identical

[adimaralimuddin]

i'd solved it! in my case, i remove the semicolmn on at .env file. probably my linter does that. but it's true. when i put any semicoln in the .env, it will show the unrelevant error.

[LeviMichalski]

This was my issue! IntelliJ used a semicolon to comment some code out, but then I added a .env extension and it used a # instead! I guess I never deleted the semicolon and once I did, it started working again.

[yahya-aghdam]

Just delete ' or " from value of env when you entering this enviroment to Vercel :)

[noraa-july-stoke]

just fyi for sequelite it should be this: DATABASE_URL=file:./db.sqlite
works for me just fine.

[ullaskunder3]

I got this issue

• Next.js 13 beta, supabase & prisma

[dxlord.🐼.007] final_portfolio (db_int)$ npx prisma db push
Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database

Error: Prisma schema validation - (get-config wasm)
Error code: P1012
error: Environment variable not found: DATABASE_URL.
  -->  schema.prisma:10
   | 
 9 |   provider = "postgresql"
10 |   url      = env("DATABASE_URL")
   | 

Validation Error Count: 1
[Context: getConfig]

Prisma CLI Version : 4.13.0

Then I just simply renamed the file .env.local to .env worked fine

[dxlord.🐼.007] final_portfolio (db_int)$ npx prisma db push
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "postgres", schema "public" at "localhost:54322"

🚀  Your database is now in sync with your Prisma schema. Done in 289ms

✔ Generated Prisma Client (4.13.0 | library) to ./node_modules/@prisma/
client in 356ms

[ullaskunder3]

Any tricks so we can use local and deploy.env

[Nicolius888]

just moving .env file to ./prisma/.env worked for me.

-Docker version 20.10.24, build 297e128
-Docker Compose version v2.18.1
-prisma/client: 4.12.0

[imjotaefe]

Take attention when you're configuring your PrismaService. I was importing like this
import { PrismaClient } from '@prisma/client/edge';

and I've changed for
import { PrismaClient } from '@prisma/client';

This simple change worked for me. Hope help you!

[nikolasburk]

Thanks for sharing!

[Jeffr-K]

In my environment I resolved this issue

• MySQL / Prisma 2 / node.js(express) v16

  1. git add > git commit -am "blah" > git push heroku master
  2. In Terminal: heroku config:set DATABASE_URL="mysql://<your_prisma_url>" --app <your_heroku_app>

[ordinz]

My issue is that my package.json I had prisma generate --no-engine. Changing it to prisma generate resolved everything.

[xyspg]

I solved it by changing import { PrismaClient } from '@prisma/client/edge'to import { PrismaClient } from '@prisma/client', and remove export const runtime = "edge"; so it uses Node.js runtime instead. Might be problem related to edge runtime

[jbcazaux]

i fixed it the same way.
For running next build on localhost with a localhost postgres, we cannot use the edge client in edge functions (seems fair since prisma cannot access our localhost)

[ytimocin]

This also solved my problem. Thanks @xyspg!

[temrb]

like others in the comment, I had tried prisma edge related products thus had

"build": "prisma generate --no-engine && next build",

in my scripts for build. Remove --no-engine as this is for edge.

[mudasirpandith]

I got this error while deploying to vercel. i need help

[safwansamsudeen]

Redeploying works for me. IDK why I have to do it everytime, though. You sure you running generate after push? You have to do that too.

[Abdullahijazvu]

I encountered an error saying that

error: Error validating datasource db: the URL must start with the protocol postgresql:// or postgres://.
--> schema.prisma:18

But after updating anything on schema.prisma or in env file

You must have to restart the application and prisma studio

Then error will be resolved

[martinslae]

My issue was I already has a key in the OS Environment Variable, so instead get from my .env it was getting from OS Variable, I deleted the OS Variable and works fine. The priority is OS then .env Em ter., 16 de jan. de 2024 às 04:39, Abdullah Ijaz < ***@***.***> escreveu:

…

I encountered an error saying that error: Error validating datasource db: the URL must start with the protocol postgresql:// or postgres://. --> schema.prisma:18 But after updating anything on schema.prisma or in env file You must have to restart the application and prisma studio Then error will be resolved — Reply to this email directly, view it on GitHub <#12170 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZQYNFJF6Q34HD7VLE6PMTYOYVB7AVCNFSM5QAFQG6KU5DIOJSWCZC7NNSXTOKENFZWG5LTONUW63SDN5WW2ZLOOQ5TQMJUGA3TCMI> . You are receiving this because you commented.Message ID: ***@***.***>

[icemagno]

Same in Blockscout backend .env file. Solved by removing double quotes. Use single quotes or no quotes at all.

[sashin123]

Issues occurred when there is an env.example, removing that file fixed my issues. No need to remove quotes. Also be sure the connection string has no errors after copying from db provider, i.e planetscale.

[jonaburg]

a very herculean effort to find that there was a whitespace at the end of the line ;)

[sashin123]

happens to the best of us 😂😂. it's the effort that counts right ?

[adamward459]

Just remote quotes in your connection, it will work

[George713]

I tried everything listed here. What solved it for me was the follwing:

// schema.prisma
datasource db {
  provider  = "postgresql"
  url       = env("NEWNAME_DATABASE_URL")
}

// .env
NEWNAME_DATABASE_URL=postgres://postgres....

After this I ran npx prisma generate to bring it to effect and started my app.

I conclude, that another environment variable named DATABASE_URL was present somewhere.

[johanguse]

Insane, this works for me!

[Dipak200]

I have done the above changes.
But now I am getting new error:
Error:
Invalid prisma.user.findFirst() invocation:
The table public.User does not exist in the current database.
Source
src\lib\stripe.ts (24:17) @ async getUserSubscriptionPlan

22 | }
23 |

24 | const dbUser = await db.user.findFirst({
| ^
25 | where: {
26 | id: user.id,
27 | },

Do you know how to resolve it?

[johanguse]

@Dipak200, please read the error message before asking! This is the error in your case: The table public.User does not exist in the current database. Did you run the command prisma db push ?

[matheusgondra]

I had the same problem. The solution was that there was already a DATABASE_URL variable defined in my OS. I had defined it for a java application. That's why prism gave an error, because the string started with "jdbc:" and not "postgresql://". Try checking in your terminal if the variable exists

Linux
echo $DATABASE_URL

Windows
echo %DATABASE_URL%

[gijsroge]

Removing node_modules did the trick for me. Prisma probably caches some stuff.