Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] CORS_ORIGINS=* --IFRAME_ORIGINS=* #3942

Closed
Gallisatyricon opened this issue Jan 29, 2025 · 1 comment
Closed

[BUG] CORS_ORIGINS=* --IFRAME_ORIGINS=* #3942

Gallisatyricon opened this issue Jan 29, 2025 · 1 comment

Comments

@Gallisatyricon
Copy link

Describe the bug
On my local installation of flowise, I cannot open the popup intefaces to write text in nodes.
I have a console error : 6[Deprecation]-ms-high-constrast is in the process of being deprecated. Please see < URL > for tips on updating to the new Forced Colors Mode standard.
This happen on all my browsers.
I don't have the issue on a Azure installation, so it has to do with my local setup, but I don(t know where to start...
I'm on 2.2.4, but this started before I updated to the last version.
It happens on all my flows, and the tools with a text pop-up interface.

I did a screen capture of the event.

Enregistrement.2025-01-29.101736.mp4

Can someone help me ?

Many thanks

@Gallisatyricon
Copy link
Author

Quick update :
Thanks to ChatGpt, I found a solution. Here it is in case someone face the sae issue:

To configure CORS headers in Flowise:

When running Flowise locally, browser security policies (CORS) may prevent pop-up windows from loading correctly. To address this, ensure that CORS headers are properly configured to allow requests from your local environment. According to Flowise's documentation, you can set the following environment variables:

CORS_ORIGINS=*
IFRAME_ORIGINS=*

If you're starting Flowise with the command npx flowise start, use:

npx flowise start --CORS_ORIGINS=* --IFRAME_ORIGINS=*

@Gallisatyricon Gallisatyricon changed the title [BUG] [BUG] CORS_ORIGINS=* --IFRAME_ORIGINS=* Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants