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

web3 is not connecting to Rinkeby provider in Firefox #47

Closed
troggy opened this issue Oct 9, 2018 · 5 comments
Closed

web3 is not connecting to Rinkeby provider in Firefox #47

troggy opened this issue Oct 9, 2018 · 5 comments
Assignees
Labels

Comments

@troggy
Copy link
Member

troggy commented Oct 9, 2018

Looks like CORS issue.

Probably related: web3/web3.js#1803

Firefox 63.0b13

Bounty

Delivery

  • make Bridge UI work in latest Firefox/Brave. Probably, it is as easy as downgrading web3 to beta.33, although I expect some headache with @types/web3 in this case.

Bounty setup

Value: 165 DAI

gardener: @troggy / 0%
worker: @troggy / 90%
reviewer: @johannbarbie / 10%

@sunify sunify closed this as completed in b7f5db2 Oct 19, 2018
@troggy troggy reopened this Nov 8, 2018
@sunify sunify closed this as completed in 64300ca Nov 12, 2018
@sunify
Copy link
Member

sunify commented Nov 27, 2018

I've upgraded web3 to latest beta. beta.33 contains wrong typings and that leads to a lot of typescript errors.

I'll fix web3 and send PR

@sunify sunify reopened this Nov 27, 2018
@troggy
Copy link
Member Author

troggy commented Nov 27, 2018

👍
anyway, it didn't work for me in Firefox lately

@troggy
Copy link
Member Author

troggy commented Dec 11, 2018

Doesn't work in Brave as well.

Same error

Access to fetch at 'https://rinkeby.infura.io/' from origin 'http://localhost:1234' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: Redirect is not allowed for a preflight request.

@troggy troggy added the bounty label Dec 24, 2018
@troggy troggy self-assigned this Dec 30, 2018
@troggy
Copy link
Member Author

troggy commented Dec 30, 2018

Brave has different reasons :( And there is no soution yet.

brave/brave-browser#2252

UPD: workaround is to switch off Fingerprinting protection

@troggy
Copy link
Member Author

troggy commented Jan 4, 2019

closed via #92

@troggy troggy closed this as completed Jan 4, 2019
troggy added a commit that referenced this issue Jan 21, 2019
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

2 participants