squarecat / doc-buddy Goto Github PK

Trying to get this to run locally instead of on DO since I prefer to selfhost. However am running into this error:

$ node index.js
[server]: started on 1333
[server]: Bot listening...
Error: write EPROTO 139860701919168:error:14094458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1565:SSL alert number 112

    at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:94:16) {
  errno: -71,
  code: 'EPROTO',
  syscall: 'write',
  '$metadata': { attempts: 1, totalRetryDelay: 0 }
}
null

Any ideas? It looks like it's complaining about my S3 config, but as far as I'm able to tell, my s3 config is correct. I'm using minio to back it with a Let's encrypt cert.

STORAGE_NAME="docbuddy-bucket-name"
STORAGE_URL="https://s3.my.domain/"
STORAGE_KEY="my_access_key"
STORAGE_SECRET="my_secret_key"

What am I missing here? I have several other applications using this s3 endpoint, so I know it works, and I've confirmed the bucket manually via commandline too.

Based on the error it looks like its trying to use TLSv1? How can I configure it to use TLSv1.2?

First. Is it possible to upload PDFs in bulk, and then direct the bot to digest the repository? Loading one at a time via chat may take a while.

Second. I’m leaning toward trying this on Discord rather than Telegram. Any tips/advice?

Hope you’re well.

Hey,

I want to play a little bit with your telegram bot, but the Digital Ocean deploy is not working properly. I receive the following error message when I click on the create resource button: GitHub user does not have access to squarecat/documentation-buddyClose

Thanks,
Csaba

Any hints on why the telegram bot is telling me "I had some trouble with that: Failed to save embeddings" I've double and triple checked my Pinecone API Key, seems like it's getting hung up there, as it's not making it to my S3 bucket.