We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I get this error when connecting to a Supabase Postgres database using Postgres.js on Deno 1.36.3+c9223bc:
1.36.3+c9223bc
import postgres from "https://deno.land/x/postgresjs@v3.3.5/mod.js"; // For Deno // import postgres from "postgres"; // For Node const sql = postgres(databaseUrl, { ssl: "require" }); await sql`SELECT 1`; // Result: error: Uncaught (in promise) InvalidData: invalid peer certificate: UnknownIssuer while ((result = socket.readyState === 'open' && await raw.read(b))) { ^ at async TlsConn.read (ext:deno_net/01_net.js:107:15)
However, the code above works fine on Node.js v18.17.1
v18.17.1
The text was updated successfully, but these errors were encountered:
I was able to solve this error by setting DENO_CERT=./certs/supabase.crt env variable
DENO_CERT=./certs/supabase.crt
However, is the error intentional? Or do we expect the code above to pass, like on Node?
Sorry, something went wrong.
I encountered the same error message when I tried to use a client certificate.
nodejs/node#48977
const { Agent } = require('undici'); fetch(url, { dispatcher: new Agent({ connect: { cert: cert, key: key, ca: ca } }) });
No branches or pull requests
I get this error when connecting to a Supabase Postgres database using Postgres.js on Deno
1.36.3+c9223bc
:However, the code above works fine on Node.js
v18.17.1
The text was updated successfully, but these errors were encountered: