-
Notifications
You must be signed in to change notification settings - Fork 18
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
adalite.to on Safari can't find BitBox. Chrome works without problems #39
Comments
Electrum and Sparrow do not use the bridge. Is the bridge running? You can check by visiting http://localhost:8178/. What is the contents of your /etc/hosts file? Does Firefox work? |
/etc/hosts: `## Host Databaselocalhost is used to configure the loopback interfacewhen the system is booting. Do not change this entry.127.0.0.1 localhost http://localhost:8178/ shows: `BitBoxBridge v1.5.0 api version = 1.5.0` |
Safari blocks fetching dada from http://localhost:8178/api/v1/devices. |
@thisconnect would 127.0.0.1 work instead? |
@benma unfortunately not fetch('http://127.0.0.1:8178/api/v1/devices').then(body => body.json()).then(console.log).catch(console.error) |
@benma @thisconnect I think this is due to Safari breaking the spec, not allowing localhost content over http for a https website. https://bugs.webkit.org/show_bug.cgi?id=171934 |
Interesting! Seems like the issue won't be resolved anytime soon either :/ |
On Mac OS Big Sur i can´t use adalite.to with Safari. The site can't find the device. http://127.0.0.1:8178/ shows, that bitbox bridge is running. Electrum and Sparrow can use the bridge without any problems. Chrome works perfectly, but i think, it doesn't use the bridge directly.
So, is there a common issue with Safari and BitBox Bridge?
The text was updated successfully, but these errors were encountered: