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

CORS error when attempting to connect to ledger device #1218

Open
SgtPooki opened this issue Mar 14, 2023 · 0 comments
Open

CORS error when attempting to connect to ledger device #1218

SgtPooki opened this issue Mar 14, 2023 · 0 comments

Comments

@SgtPooki
Copy link

Describe the bug

I keep getting "failed to fetch" even though it lets me connect to my ledger device successfully

image

Error in the browser console shows:

Access to fetch at 'https://graph.glif.link/query' from origin 'https://safe.glif.io/' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

Network requests:

image

image

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'https://safe.glif.io/'
  2. Click on 'ledger device'
  3. Click on 'connect'
  4. (optionally select ledger device in popup)
  5. See error

Expected behavior
It connects to my ledger device successfully

Screenshots

see above

Desktop (please complete the following information):

  • Device: MacBook Pro Apple M1 Max
  • OS: macOS Ventura 13.1
  • Browser: Brave
  • Version: 1.48.171

Additional context

Note that my ledger device hasn't been used/altered since last accepting tokens. I attempted to accept some tokens and received this same error. I then tried connecting to ledger live (successfully) and saw that a firmware update was available, so i updated my ledger device hoping that would solve the problem, but I'm was still getting the same error. Then I noticed it was a CORS error, so it seems highly likely that it's a problem with the website itself.

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

1 participant