⨯ TypeError: fetch failed
at node:internal/deps/undici/undici:12502:13
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async postJSON (file:///D:/earn/node_modules/.pnpm/@[email protected]/node_modules/@planetscale/database/dist/index.js:125:22)
at async Connection.execute (file:///D:/earn/node_modules/.pnpm/@[email protected]/node_modules/@planetscale/database/dist/index.js:81:23)
at async PrismaPlanetScale.performIO (file:///D:/earn/node_modules/.pnpm/@[email protected]_@[email protected]/node_modules/@prisma/adapter-planetscale/dist/index.mjs:151:22)
at async PrismaPlanetScale.queryRaw (file:///D:/earn/node_modules/.pnpm/@[email protected]_@[email protected]/node_modules/@prisma/adapter-planetscale/dist/index.mjs:122:22)
at async D:earnnode_modules.pnpm@[email protected][email protected]node_modules@prismaclientruntimelibrary.js:29:14083 {
clientVersion: '5.22.0',
page: '/',
[cause]: [Error: 141C0000:error:0A00010B:SSL routines:ssl3_get_record:wrong version number:c:wsdepsopensslopensslsslrecordssl3_record.c:355:
] {
library: 'SSL routines',
reason: 'wrong version number',
code: 'ERR_SSL_WRONG_VERSION_NUMBER'
}
}
Getting this error when trying to visit localhost on a Next.js app.
The above error comes when visiting the http://localhost:3000
Feeling a bit lost here, not sure what exactly the issue could be, this is the app which I’m trying to run: https://github.com/SuperteamDAO/earn
Just a guess but maybe it seems to be related to the src/prisma.ts
file (You can check on GitHub), since the planet scale which error mentions only seems to be used in that fine.
To reproduce the error, simply try running the app in https://github.com/SuperteamDAO/earn this repository and it shows that error when you try opening the app on localhost.
In any case, any help is appreciated, thanks!
- Tried running the app with flag
--experimental-https
- Tried from different devices
- Tried with both a locally hosted MySQL database and one hosted online on a service in case it’s related
Lahn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.