[BUG] Unable to connect to any Chat APIs

[Covalent0714]

Environment

🪟 Windows

System

Windows 10

Version

1.11.8 'staging' (d636385)

Desktop Information

NovelAI and Cohere APIs

Describe the problem

Attempts to connect to any chat APIs (Cohere and NovelAI shown as examples yield a FetchError and says "No connection..."

FetchError: request to https://api.cohere.ai/v1/models failed, reason: unable to verify the first certificate
at ClientRequest. (C:\Users[REDACTED]\Documents\GitHub\SillyTavern\node_modules\node-fetch\lib\index.js:1505:11)
at ClientRequest.emit (node:events:513:28)
at TLSSocket.socketErrorListener (node:_http_client:502:9)
at TLSSocket.emit (node:events:513:28)
at emitErrorNT (node:internal/streams/destroy:151:8)
at emitErrorCloseNT (node:internal/streams/destroy:116:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
type: 'system',
errno: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE',
code: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE'

FetchError: request to https://api.novelai.net/user/subscription failed, reason: unable to verify the first certificate
at ClientRequest. (C:\Users[REDACTED]\Documents\GitHub\SillyTavern\node_modules\node-fetch\lib\index.js:1505:11)
at ClientRequest.emit (node:events:513:28)
at TLSSocket.socketErrorListener (node:_http_client:502:9)
at TLSSocket.emit (node:events:513:28)
at emitErrorNT (node:internal/streams/destroy:151:8)
at emitErrorCloseNT (node:internal/streams/destroy:116:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
type: 'system',
errno: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE',
code: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE'

This is a new problem that arose today. Nothing was changed with regards to API keys.

Additional info

No response

Please tick the boxes

• I have explained the issue clearly, and I included all relevant info
• I have checked that this issue hasn't already been raised
• I have checked the docs

[Cohee1207]

What's your node version?

[Covalent0714]

v18.16.1

[Cohee1207]

Try updating to the latest LTS version (20)

[Covalent0714]

Updated node.js to v20.12.2

Still getting the same error.

[sorrowhead]

currently having exactly the same problem with NovelAi. everything was ok, this error started appearing few hours ago. maybe it's something about servers, idk.

[Cohee1207]

@sorrowhead do you perhaps have a ESET antivirus software installed?
@Covalent0714 and another person in ST Discord confirmed they use antivirus from this vendor.

[Petero48]

I have the same or similar problem with OpenRouter, it worked couple of hours ago but now it doesnt, i get this error msg:
Instantiated the tokenizer for gpt-3.5-turbo
FetchError: request to https://openrouter.ai/api/v1/models failed, reason: unable to verify the first certificate
at ClientRequest. (E:\SillyTavern-1.11.7\node_modules\node-fetch\lib\index.js:1505:11)
at ClientRequest.emit (node:events:518:28)
at TLSSocket.socketErrorListener (node:_http_client:500:9)
at TLSSocket.emit (node:events:518:28)
at emitErrorNT (node:internal/streams/destroy:169:8)
at emitErrorCloseNT (node:internal/streams/destroy:128:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
type: 'system',
errno: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE',
code: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE'

[Cohee1207]

This was found to be a problem with ESET antivirus. Adding an exception for Node in SSL protection rules seems to help.

Thanks @Covalent0714 for the image.

[Petero48]

This was found to be a problem with ESET antivirus. Adding an exception for Node in SSL protection rules seems to help.

Thanks @Covalent0714 for the image.

It worked! Thank you.

[sorrowhead]

This was found to be a problem with ESET antivirus. Adding an exception for Node in SSL protection rules seems to help.

Thanks @Covalent0714 for the image.

that worked, thank you very much! <3

[NoCopy]

@Cohee1207 Through a round-a-bout journey today I found this by going from Stack Overflow > ESET > here.

Just wanted to extend a massive thanks for posting about this on the ESET forums so it could be recognized. That helped myself and a bunch of co-workers today.

Again, seriously, respect. We owe you a beer.... or lots of beers.

[sorrowhead]

not sure if i should make separate issue post, for some hours everything worked okay after adding the exception in ESET, but now i'm having this problem:
it happens when i try to run sillytavern.

[Cohee1207]

@sorrowhead it looks like your node install is not in the PATH variable anymore. Try reinstalling it.

I'm closing this issue as we currently have a workaround solution and ESET is working on a fix.