Hello everyone! How we can determine the source of...
# announcements
w
Hello everyone! How we can determine the source of this error on our self-hosted docker? https://growth.digitalumsetzen.com/ The error texts is basically from Auth0 provider that Growthbook uses on its cloud, and Auth0 should not be used on self-hosted deployments, as the docs and code comments says. Thank you for any thoughts!
f
you are running the API backend on /backend?
what is your config? can you share?
w
Yes, API is running on the /backend, ports proxied with apache from 443 to 3000 & 3100
f
That error is not coming from Auth0, but from the self-hosted auth system. It likely has to do with how your proxying is set up. Is apache forwarding the auth header to the API?
w
Hi, Jeremy, I could not find that error text in constants and project files, so decided it’s related to auth0. Could you advice how to check is header forwarded to API?
f
It's been a while since I've worked with Apache. I found this on stack overflow though https://stackoverflow.com/questions/38057978/apache-proxypass-removes-authorization-header does that help?
w
Thanks! I’ve tried, no result. Swithed to nginx, still fighting with the same error