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

Can't use a runtime in HTTPS mode #433

Closed
trustmaster opened this issue Jan 30, 2015 · 3 comments
Closed

Can't use a runtime in HTTPS mode #433

trustmaster opened this issue Jan 30, 2015 · 3 comments
Labels

Comments

@trustmaster
Copy link
Member

If I log into https://app.flowhub.io and try to access a local runtime I get:

[blocked] The page at 'https://app.flowhub.io/#runtime/' was loaded over HTTPS, but ran insecure content from 'ws://localhost:3569/': this content should also be loaded over HTTPS.
Uncaught SecurityError: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS.

Looks like noflo-nodejs and other runtimes need HTTPS implementation in order to work with Flowhub over HTTPS. There should be some kind of secure flag upon runtime registration and Flowhub should check it before opening a runtime and raise a warning if current connection doesn't match the runtime's secure flag.

@forresto
Copy link
Member

That's a good idea. Related PR for setting up ssl for node noflo: noflo/noflo-nodejs#11

@bergie
Copy link
Member

bergie commented Jan 12, 2017

See also noflo/noflo-nodejs#54

@bergie
Copy link
Member

bergie commented Mar 20, 2018

noflo-nodejs supports wss in the next release noflo/noflo-nodejs#54 (comment)

@bergie bergie closed this as completed Nov 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants