Hi @gre,
do you know if the blocking of CCID and HID classes in Chrome (https://www.yubico.com/support/security-advisories/ysa-2018-02/) affects your plans to use WebUSB?

it shouldn't be a problem.

Hi!I know how to get around this error when signing transactions!

everything works fine for binance DEX!

https://bugs.chromium.org/p/chromium/issues/detail?id=935131

We are talking about windows or Linux?

@Luganova from what we have seen it affects all platform.

I agree! It is necessary to confirm the transaction in a split second! I did not have time-time out!

It appears that a Chrome update may have solved the problem. Waiting for more confirmations.

Working on latest chromium's latest revision 637660. https://download-chromium.appspot.com/

On chrome 72, this also causes the error Invalid data received (0x6a80) when using btc.signMessageNew with certain sizes of message.

Still seeing this in the latest version of chrome - 73.0.3683.86 (Official Build) (64-bit)
Also tried it with the latest firmware + ledger lib and the timeout issue after ~3 seconds is still happening.

On chrome 72, this also causes the error Invalid data received (0x6a80) when using btc.signMessageNew with certain sizes of message.

I get the same error with eth.signTransaction with chrome - 73.0.3683.86

I'm having the same issue, despite the fact that ledger support advised using brave and opera browser but it's still not working in all these platforms with same error U2F Timeout.

1.1.8

that ledger support advised using brave and opera browser but it's still not working in all these platforms with same error U2F Timeout.

Same here. It used to work with Brave a couple of weeks back but not it's broken there too

Here too. For me it used to work with Opera some weeks ago but now that does not work either.

It still timeout when I use the brave

Not working for me too, I have tried Opera, Brave, last Chromium...
How can I send tokens?

@iicc1 for us the workaround was to quickly (during 1 second) confirm twice

Thanks for you reply @poserr, I didn't see it. I was finally able to do with an old Brave release that I downloaded here: https://github.com/brave/browser-laptop/releases

@iicc1 which one did you download from those?

@dzsobacsi v0.25.300

Version 73.0.3683.103 (Official Build) (64-bit) U2F timeout still exists

v.0.25.300 didn't work for me ...

I have this error.
Ledger Nano S
Firmware: 1.5.5
Ethereum App 1.2.7
dYdX Exchange accessed via MetaMask connected to Ledger Nano S
Tried using Chrome, Opera, and Brave
Tried using Windows 10 Home and Windows 7 Enterprise (up-to-date security patches). All six of these options create the same error. All my funds are essentially trapped on the dYdX Exchange/in the smart contract.

Update: Was able to work around. Copied the MetaMask data and sent the identical transaction via MEW in the advanced data field instead and it worked.

Thanks for all the suggestions. I seem to have solved the problem independently, well at least temporarily. But I’m still of the opinion this is a big issue for the community. Like the above poster, I also lost access to my tokens. More importantly I was unable to conclude several time sensitive trades on a DEX because of this “known issue”. I’m just amazed that this isn’t a bigger deal across the web. I’m also amazed that this has not been solved yet. Its been months now. I’m sorry but the first post on this thread was in Feb. Anyway enough, I’m sorry about the rant. Here is what I did.

First I uninstalled the latest version ofChrome and reverted back to an older version. I installed a version that was released just before Feb 2019, when the known issue occurred. I used Version 71.0.3578.80 (Official Build) (64-bit)
You’ll have to stop chrome from auto updating, (which it likes to do all the time). Just do a quick search on the web to see how to do that.
In my particular case I was using metamask to complete my transactions.
Initially I installed the latest version of Metamask, but that also seems to cause similar issues. So I decided to use MetaMask 5.2.1. This version was released around the same time as the Chrome version I have reverted to using.
You can also easily find this on the web. When installing the metamask extension, use developer mode within the extension settings.
Then click on "load unpacked" and install the custom extension. Not sure how to stop auto updates on metamask however. You might have to reinstall over time.
Again I am not sure how long this will work for, and if it will work for everyone. But it does prove that reverting to older web browsers does seem to be the way to go for now.

Tried everything. old version of opera will only allow install of ver Version 3.14.1 of metamask which does not support Ledger! There is NO WAY to access ERC 20 Tokens on Ledger. This is crazy!

Error message:

I used Chrome Beta and that one works for me ;)

Worked with:

Metamask: 6.7.2
Chrome: 75.0.3770.100
Ledger Nano S: Secure Element: 1.55, MCU: 1.7

Still getting "Failed to sign with Ledger device: U2F TIMEOUT" on Manjaro/Brave. What can I do? It's been weeks. :/

Also hangs the Ledger dead.

Still getting "Failed to sign with Ledger device: U2F TIMEOUT" on Manjaro/Brave. What can I do? It's been weeks. :/

Alright, I could actually get around the aforementioned issue by following this link (granted, I probably should've look there earlier): https://support.ledger.com/hc/en-us/articles/115005165269-Fix-connection-issues

I was missing this part:

"wget -q -O - https://raw.githubusercontent.com/LedgerHQ/udev-rules/master/add_udev_rules.sh | sudo bash"

However, now I keep getting "Failed: need signature."

It's really not funny anymore.

It is hilarious that they recommend searching for a driver for windows 10 that doesn't exist.

@AdvocateOne, thank you for the information you provided.

We suspect this is related to USB driver on Windows 7. Can you try updating them ?

https://support.ledger.com/hc/en-us/articles/115005165269-Fix-connection-issues

Thanks a lot.

This simply doesn't work. There are no windows drivers that I can find. Please provide a direct download link for your drivers.

For all users experiencing this issue - try to update Firmware on your device to the latest version (1.5.5) and update your Ethereum app as well (1.2.4)

This does not work. On every browser (Chrome, FF, Brave, Opera) MM times out too soon with the latest firmware (1.5.5) and Ethereum app. The topic of this bug should be changed to reflect this is a general problem with Ledger support and MetaMask. It should also include the fact that MM U2F hangs the ledger stone dead when attempting to sign an ERC20 transaction (or any transaction with contract data).

The lack of progress on this bug is dismaying in the extreme; it makes the Ledger almost completely useless when browsing web3/u2f pages.

Will LedgerHQ/nanos-secure-sdk#21 fix this bug?

MetaMask/metamask-extension#6345

I sent some erc-20 tokens to my ledger prior to discovering this issue (trying to be safer!). Obviously I can't move them now in metamask . Am I SOL until this is resolved or a new ledgerlive is released?

I tried @dogperrokukur 's post of rolling back chrome/mm extension from Jun19 and the page just freezes on the "connect a hardware wallet" screen of metamask. Any assistance is greatly appreciated.

If you're running Windows 1903 please see https://www.reddit.com/r/ledgerwallet/comments/cxf3h9/new_beta_windows_pop_up_issue/ and report in the reddit thread if this fixed your issue

Why is this discussion on reddit and not here?

For better visibility and follow up - of course, you can also report here. We'll update the related threads once the beta is closed if the outcome is successful.

The situation should be back to normal (using latest firmware)

@gre what do we need to update for EOS?

Still seeing this issue with Ledger Nano S firmware 1.6.0. Basically won't connect to Metamask. I can connect to Ledger Live 2.0.
TransportError: Failed to sign with Ledger device: U2F DEVICE_INELIGIBLE
Can someone please help? I am on Ubuntu 18.04 LTS

+1 Seeing this error as well

Me too. 🙌 WebUSB is broken with the ledger web3-subprovider.

Please share a (minimal) example that reproduce the problem in a new Github issue because it's not easy to understand what exactly you are raising. this task is about U2F support issue we had a year ago and have nothing to do with WebUSB or web3-subprovider.