fix: [ISSUE] Local Docker Compose install fails in browser with CSP unsafe-eval / Ajv schema compilation error
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 718
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 23
Description
Describe the bug
Fresh local self-hosted install fails in the browser UI. The console shows a Content Security Policy error blocking unsafe-eval, followed by an Ajv-generated schema compilation failure. This appears to break the frontend in a local Docker Compose setup.
To reproduce
1. Start Unstract with ./run-platform.sh script
2. Open the local UI in the browser
3. Go to http://frontend.unstract.localhost/mock_org/onboard
4. Select any of the 4 oboarding steps
5. Click test connection green button
6. Observe CSP error and schema compilation failure
Expected behavior
The test connection to pass or fail with a user feedback message
Environment details
- Version: v0.161.2 (latest tag in docker as of 3/24/26)
Screenshots
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
Start by running ./run-platform.sh and reproducing the failure at the local onboarding URL while inspecting the browser console for the CSP and Ajv errors. Trace the frontend path triggered by the test connection button and identify why local Docker Compose blocks the request. Done means the connection reports a success or failure message without breaking on schema compilation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, javascript
- Domain
- devops, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100