I’ve been running into SSL certificate problems while trying to connect to the Langsmith service. The error message I’m getting suggests that the certificate has expired and verification is failing.
Here’s the specific error I’m seeing:
langsmith.utils.LangSmithConnectionError: Connection error caused failure to POST https://api.smith.langchain.com/runs/batch in LangSmith API. Please confirm your internet connection. SSLError(MaxRetryError("HTTPSConnectionPool(host='api.smith.langchain.com', port=443): Max retries exceeded with url: /runs/batch (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1028)'))"))
I’ve also tried accessing the main website directly through different browsers and I’m getting similar certificate warnings. This issue just started happening recently and my code was working fine before. Has anyone else encountered this problem? Is this something on Langsmith’s end or could it be a configuration issue on my side?
Same thing happened to me three weeks ago with a different service. Companies get blindsided by cert expirations because they don’t monitor them properly. While waiting for the fix, I temporarily disabled SSL verification in my dev environment - don’t do this in production though. Hit up their support team directly since they might not know about it yet. Most companies jump on SSL renewals once someone tells them, so it’ll probably get fixed fast. Just keep checking their API endpoint - they usually fix these things without saying anything.
yup, i’m in the same boat. thought it was just me but looks like langsmith’s cert is the issue. tried on different browsers and got the same expired cert warning. they should sort this out asap.
This looks like a server-side certificate issue, not your local setup. I hit something similar last month with another API - their SSL cert had expired on their end. Since you’re getting the same warnings across multiple browsers, it’s definitely not a client-side problem. I temporarily used verify=False in my requests for testing, but don’t do that in production. Check their status page or GitHub issues to see if they’ve posted about it. These cert renewals usually get fixed within 24-48 hours once they notice.