You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While logged-in, Beet exposes a websocket API LOCALLY that can only be accessed by applications running on your computer ...
I think the default should be localhost, i am not sure why the fallback is there and why beet will expose to that url.
At least some docs for clarification about this should be needed, hosts should be maybe in a config file among other variables if we really need them(for me it should just need to try to connect to ws://localhost:60555)
The text was updated successfully, but these errors were encountered:
It's a safety feature to disallow localhost fallsback because then you are using a ws instead of a wss connection. In your script
you simply do beet.allowLocalhostFallback(); when you want the fallback to trigger.
By trying the samples i get this error:
Firefox can’t establish a connection to the server at wss://local.get-beet.io:60556/.
By watching the code the fallback flag is false:
https://github.com/bitshares/beet-js/blob/master/src/lib/socket.js#L3
By beet README:
While logged-in, Beet exposes a websocket API LOCALLY that can only be accessed by applications running on your computer ...
I think the default should be localhost, i am not sure why the fallback is there and why beet will expose to that url.
At least some docs for clarification about this should be needed, hosts should be maybe in a config file among other variables if we really need them(for me it should just need to try to connect to ws://localhost:60555)
The text was updated successfully, but these errors were encountered: