Closed chriswk closed 10 months ago
Hi @jaiswalshikha - Reading over your error report. It seems like you've set UNLEASH_URL to just /unleash
. UNLEASH_URL needs to be the full valid URL (as in https://my.domain.com/unleash)
BASE_URI_PATH needs to be the path of the URL. (in this example it would need to be /unleash).
The last error message seems to point towards UNLEASH_URL not being a valid URL and then this will fail the way you're seeing in your logs.
Closed due to lack of feedback.
Describe the bug
Okay so I was able to get Unleash up and running. However, when I am setting a context path as / in ingress rule, it is accessible but not when it is set to /unleash.
This works: ` hosts:
But not this
`hosts:
My UNLEASH_URL is set to/unleash
When I set the context path to /unleash I get 404 error for/static/style-770afaee.css net::ERR_ABORTED 404 (Not Found) and /static/index-17d74ac9.js net::ERR_ABORTED 404 (Not Found)
So I tried setting BASE_URI_PATH in the env variable. But then I am getting below error in pod logs and it goes into CrashLoopBackOff state.
Steps to reproduce the bug
No response
Expected behavior
Unleash should start and serve on /unleash
Logs, error output, etc.
Screenshots
No response
Additional context
No response
Unleash version
No response
Subscription type
None
Hosting type
None
SDK information (language and version)
No response