Helicone Community Page

Updated 2 months ago

Troubleshooting self-hosted helicone with openai proxy

Hey folks, I've gotten self-hosted Helicone up and running. I've used Postman to send a test request via the OpenAI proxy but am not seeing anything popping up in the dashboard. Any guidance? I'm using docker-compose FWIW.
p
J
9 comments
Also when I logged in, during the onboarding process, I noticed that the baseUrl being suggested was empty. May be related?
Executing queries in the playground works but also doesn't show up in the request/dashboard.
Logs for the OpenAI proxy show:
Plain Text
✘ [ERROR] Uncaught (async) Error: supabaseUrl is required.

      at new SupabaseClient (file:///worker/.wrangler/tmp/dev-fbGIxn/index.js:12170:13)
      at createClient (file:///worker/.wrangler/tmp/dev-fbGIxn/index.js:12358:10)
      at log (file:///worker/.wrangler/tmp/dev-fbGIxn/index.js:30131:22)
The proxy container does have this configured though:
"SUPABASE_URL=http://kong:8000"
Hi! Is this on a single host?
Hey folks, can anyone weigh in here? We can't really use the Cloud offering since we're a HIPAA covered entity.
cc: @Cole would love any insights you have here.
Add a reply
Sign up and join the conversation on Discord