Hi Team there is a question from a customer on Intercom Does Nixtla Community #support

Hi Team, there is a question from a customer on In...

Nikhil Gupta

05/21/2025, 6:57 PM

Hi Team, there is a question from a customer on Intercom. Does anyone know the answer to this? Thanks!

Copy code

We're currently using TimeGPT within an Azure AI instance. On Monday, we noticed that we were receiving SSL Cert expiration warnings whenever we attempt to call out to the instance. It looks like the SSL Cert is something that is handled on the Nixtla side of things. Would you mind taking a look into this for us?

Max

05/23/2025, 1:15 AM

Which customer is this?

Max

05/23/2025, 1:16 AM

And are they using the SDK or the API directly ?

Max

05/23/2025, 1:23 AM

Regarding your question, I think the SSL cert for

<http://api.nixtla.io|api.nixtla.io>

is valid (issued Mar 31, 2025, expires Jun 29, 2025), so it's unlikely the issue is on Nixtla’s end. The warnings are probably due to an outdated CA bundle on the customer's Azure instance. You can check by running this command in bash:

Copy code

echo | openssl s_client -connect <http://api.nixtla.io:443|api.nixtla.io:443> -servername <http://api.nixtla.io|api.nixtla.io> 2>/dev/null | openssl x509 -noout -dates

Max

05/23/2025, 1:25 AM

That being said it seems that certs are about to expire. @Edu or @Han Wang: do you know how and where to update the certs?

Copy code

(base) ➜  ~ echo | openssl s_client -connect <http://api.nixtla.io:443|api.nixtla.io:443> -servername <http://api.nixtla.io|api.nixtla.io> 2>/dev/null | openssl x509 -noout -dates

notBefore=Mar 31 03:15:33 2025 GMT
notAfter=Jun 29 03:15:32 2025 GMT

Edu

05/23/2025, 4:16 AM

no idea, current API was built by Jose afaik but I would expect the SSL to be handled automatically by our infra provider

Open in Slack

Previous Next