Connection error on fresh install when behind proxy - certificate issue
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12.5k
- Forks
- 998
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 10
Description
When trying any model I get:
Error: Connection error.
I'm behind a zscaler proxy/firewall, and there is a HTTPS certificate issue.
The uv package manager handles this situation well, by allowing use of the system's native certificate store through the --native-tls command.
Could a similar function be added to llm?
Thanks
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue concerns llm's command-line connection setup and requests an option analogous to uv's --native-tls; start by tracing how model requests configure HTTPS and read the linked uv HTTP authentication documentation. Done means model requests work behind a Zscaler proxy using the system certificate store without breaking normal certificate validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100