You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Generated with create-llama@0.0.13 an express, streaming, postgresSQL example. Using TimescaleDB as DB.
Directly using the connection string from TimescaleDB as PG_CONNECTION_STRING and calling npm run generate leads to the following error:
> my-app@0.1.0 generate
> node src/controllers/engine/generate.mjs
Start creating embeddings...
Error: self-signed certificate in certificate chain
at TLSSocket.onConnectSecure (node:_tls_wrap:1659:34)
at TLSSocket.emit (node:events:517:28)
at TLSSocket._finishInit (node:_tls_wrap:1070:8)
at ssl.onhandshakedone (node:_tls_wrap:856:12) {
code: 'SELF_SIGNED_CERT_IN_CHAIN'
}
node:internal/process/promises:288
triggerUncaughtException(err, true /* fromPromise */);
^
Error: self-signed certificate in certificate chain
at TLSSocket.onConnectSecure (node:_tls_wrap:1659:34)
at TLSSocket.emit (node:events:517:28)
at TLSSocket._finishInit (node:_tls_wrap:1070:8)
at ssl.onhandshakedone (node:_tls_wrap:856:12) {
code: 'SELF_SIGNED_CERT_IN_CHAIN'
}
I had to remove sslmode=require from the connection string, and then the generation worked as intended. It wasn't reproducible on Windows, only on MacOS.
The text was updated successfully, but these errors were encountered:
Generated with
create-llama@0.0.13
an express, streaming, postgresSQL example. Using TimescaleDB as DB.Directly using the connection string from TimescaleDB as
PG_CONNECTION_STRING
and callingnpm run generate
leads to the following error:I had to remove
sslmode=require
from the connection string, and then the generation worked as intended. It wasn't reproducible on Windows, only on MacOS.The text was updated successfully, but these errors were encountered: