litellm
litellm copied to clipboard
Use litellm.client_session for ollama and ollama_chat
Fixes https://github.com/BerriAI/litellm/issues/6499.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| litellm | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Dec 4, 2024 6:17pm |
Checking back on this. Does it look like a reasonable solution?
Just confirming that this fix works - making these modifications allows me to connect to an ollama instance that would otherwise fail from the self signed certificate
Upd: there's still some path that fails - via Aider:
- asking for changes works: valid suggestion received
- when aider starts applying the changes:
litellm.APIConnectionError: Ollama_chatException - HTTPSConnectionPool(host='myollama.org', port=443): Max retries exceeded with url: /ollama/api/chat (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1000)')))
Retry in 0.9 seconds.
hope this gets accepted soon: every enterprise environment who uses self certified TLS for their employees will have this problem.
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.