#I m still getting `CERT HAS EXPIRED` and
glad rampart
@upbeat thicket if it was just my machine I'd understand, but it's on GH as well https://github.com/tanepiper/Stochastic-Parrot/actions/runs/4508784415/jobs/7937813762
and if I use NODE_TLS_REJECT_UNAUTHORIZED=0 it gives 404 not found :/
upbeat thicket
Does the website work for you
?
can you try another endpoint with axios?
like you can even use https://api.elevenlabs.io/v1/voices in your browser and see it works
and cert is valid
until june
glad rampart
Yes that's the odd thing - I can access it fine via browser. If it was just not working on my cli I'd understand, but it's the CI too.
ChatGPT API also used Axios, and that runs first in the pipeline so doesn't seem to be a network issue 🤷♂️
Ahh but also why it's breaking locally no idea
https://github.blog/2023-03-23-we-updated-our-rsa-ssh-host-key/
upbeat thicket
weird
glad rampart
Is your certificate signed somewhere by the GitHub root CA? When this stuff happens Chrome will get the latest root, but for node I guess they are shipped 🤷♂️
upbeat thicket
It is signed by google
glad rampart
Yea, I'm going to give it an bit of time to see if it ripples out and fixes itself - this is black magic areas of the internet 😄
because really, no response status being returned, only a code CERT_HAS_EXPIRED 🤷♂️
No response status from server: CERT_HAS_EXPIRED
URL: https://api.eleven-labs.com/text-to-speech/MF3mGyEYCl7XYWbV9V6O/stream
Retrying... (1/10)
No response status from server: CERT_HAS_EXPIRED
URL: https://api.eleven-labs.com/text-to-speech/MF3mGyEYCl7XYWbV9V6O/stream
Retrying... (2/10)
(if I check axios's response.statusCode and statusText they don't exist so it's really happening at the http layer)
Ohhhhhh now it's been copied here I see it 😄
I bet some stupid find and replace changed it to eleven-labs