[bug]: Environment variable CORS_ALLOWED_ORIGINS is not used
Open
@akshat5302 is already working on this.
Since Jan 2, 2026.
🐛bug
plane
- Dominant language
- TypeScript
- Stars
- 59.6k
- Forks
- 5.8k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 49
Description
Is there an existing issue for this?
- I have searched the existing issues
Current behavior
No matter what is set in the CORS_ALLOWED_ORIGINS variable, it seems that the application host is always used as the value. I tried setting "*" and got an appropriate error. I tried "" but the response header still hat the application host in it. I also tried a list with the two domains I need but still got only the application fqdn back.
I found the issue while figuring out another CORS issue which was related to missing CORS config on my S3 backend.
Steps to reproduce
- Set CORS_ALLOWED_ORIGINS to empty string or mutliple domains
- Try to upload an avatar
- Watch browser request to
https://<my-plane-instance>/api/assets/v2/user-assets/withaccess-control-allow-origin: https://<my-plane-instance>/with the other URI missing
Environment
Production
Browser
Google Chrome
Variant
Self-hosted
Version
v1.2.1
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.
Assessment
This issue has not been assessed yet.