Helicone Community Page

Updated 7 months ago

Ssl error proxying requests through helicone

At a glance

The community member is experiencing an SSL error when proxying requests through Helicone (using the OpenAI client). The issue is either related to the failure to get the new certificate or only working with TLSv1.2. The community member has tried debugging the issue with devops for over an hour but without success. The community member has also noticed that the https://oai.hconeai.com URL loads on Chrome but not on Safari, and the issue started happening on Sunday.

In the comments, another community member asks the original poster to share where they found the documentation to use hconeai.com, as the community is trying to push everyone to use helicone.ai for the proxy moving forward. The original poster acknowledges the time spent debugging and mentions that the issue was related to .env vars, where the OAI base URL was kept as an environment variable, which they inherited from other engineers for two separate projects they work with. The original poster did not actually check the documentation to get the updated base URL.

There is no explicitly marked answer in the post or comments.

Useful resources
I'm getting an SSL error proxying my requests through Helicone (using openAI client). It's either failing to get the new certificate and/or only working with TLSv1.2

Any ideas? https://oai.hconeai.com loading on Chrome, but not on Safari. Started happening Sunday. Spent > 1 hour trying to debug w/ devops but no success. Anyone else?



EDIT: Replace base URL
Workaround: https://discordapp.com/channels/1020597994703310878/1248050543361003560/1248050543361003560
J
R
3 comments
HI @radu can you share where you found the docs to use hconeai.com? We are trying to push everyone to use helicone.ai for proxy moving forward
Sorry you had to spend 1hour+ debugging.
All good!

It was .env vars (we keep the OAI base URL as an env var) that I inherited from other engineers (for 2 separate projects I work with). I didn't actually check documentation to get the updated Base URL.
Add a reply
Sign up and join the conversation on Discord