Websites with issues adding the Solo V2

[raspberrycoulis]

I couldn't seem to find a list anywhere, so figured it may be a good idea adding a thread on the topic - websites that currently have problems when trying to add the Solo V2 as a 2FA key. Here is my experience:

1. Microsoft - i.e. for Outlook / Hotmail - Recognises the key (i.e. the LED changes to yellow when you need to tap it), but after tapping it, the website does not allow the key to be added. Have tried multiple times, with two Solo V2 keys on different machines (running macOS and Windows 10) and in different browsers, but nope.
2. Cloudflare - was initially able to add my keys, but then they stopped working when trying to login (gah!) - luckily my Yubikey 5 NFC was to hand, so I was able to get back in. Tried both my Solo V2 keys, but nothing - similar issue to above. Tried removing the keys from my Cloudflare account to re-add them, but similar issue to above (LED changes to yellow; tapping changes to green; website asks for a PIN, enter PIN then nothing.

At the moment, the problems seem too frequent for me and as a result I'm having to dig out my Yubikey 5 NFC instead otherwise I cannot access my accounts!

Would be great if people could add to this thread with any additional websites with issues.

[nickray]

The likely underlying issue is being worked on in trussed-dev/fido-authenticator#8.

[herrchin]

Cloudflare - Enrollment went strangely for me in that after creating a PIN, the Windows 10 prompt kept cycling between "Touch Your Security Key" and "Getting Things Ready". Touching the key once was recognized but the loop remained. Touching it again completed enrollment, and testing the key for login worked fine. Browser is Firefox. I confirmed this exact enrollment oddity using a second solo v2. Both are hacker keys, software untouched since receiving 2 days ago. Working fine after enrollment oddities.

Microsoft - I confirm the issue, everything with key enrollment appears to work up until the very end where you land on a page with "Something went wrong" "We encountered an issue setting up your security key." However, that failure is after other steps succeed like getting an SMS from Microsoft saying "FIDO key added." When looking at my list of keys though, the Solo v2 is not there though.

Google - I'm unable to enroll any of my hacker keys (original shipping firmware) with Google. The Windows 10 prompt says "This security key can't be used. Please try a different one." Multiple computers, Firefox and Chrome, same issue. These keys enrolled fine and have been tested with Twitter, so Google doesn't like the make/model, or maybe it's the underlying keyhandle length concern.

[screendriver]

GitLab and Amazon AWS also are not able to register Solo V2 whereas Solo V1 is working perfectly fine there.

[burtek]

Managed to register in AWS via Firefox. Doesn't work on Chrome/Opera

[didn0t]

Unable to add as a second factor on 1password.com

[burtek]

Disclaimer: All test results below are as for old 20200101.9 firmware. Testing results for new 20220822.0 firmware are to be noted in parenthesis.

---

Key registered on windows doesn't work on android. Key registered in android does work on windows. That applies to both old and new firmware.

Unable to add Solo2 to:

• NextCloud - both as 2FA U2F, Webauthn 2FA or passwordless auth via Webauthn (webauthn works on new firmware)
• Dropbox (still fails)
• Zoho (still fails)
• nVidia (still fails)
• Microsoft
• Heroku (unable to test, my account was closed)
• 2 Discourse forums

Managed to add keys via FF, while being unable to on Chrome/Opera:

• AWS
• OVH

Works fine:

• Sentry
• Twitter
• Cloudflare
• Google
• Facebook
• Auth0
• GitHub
• Bitbucket
• WordPress (new firmware broke registering key on android, windows works)

[iGadget]

On my Nextcloud instance, the Solo2 actually works fine when configured as Webauthn device. Tried with Chrome, Chromium and Firefox on (Linux) desktop and Chrome and Firefox on Android (9 and 11). The key itself can react a bit flaky to the touches though, sometimes I have to tap several times before the authentication comes through.
The only combination I failed to get working so far was when using Ungoogled Chromium (103, Flatpak). So apparently, some Google (proprietary?) tech is required.

[pbl987]

Solo2 with 2:20220822.0 on Firefox + Windows @ Dropbox also fails for me. Yubikey and even Windows Hello just added fine.

[msiqx9]

For Dropbox registration, try Chrome browser in Windows.

[burtek]

@msiqx9 thanks for replying that in multiple threads. The thing is "use another browser" is a workaround, not a solution. We need a solution, not a workaround

[msiqx9]

Most people are happy to use a workround for registration as thereafter the Solo v2 key will work in any browser. A "solution" will be a long time coming as nobody on here has the Rust programming skills to submit corrections. In my case, the Solo v2 now works to login to Dropbox in any browser.

[thegcat]

Registering a Solo2 key with a Pretix instance via Safari doesn't work either.

[phlbnks]

Registering Solo2 to Gitlab fails in Safari 15.4 under MacOS 12.3 (500 error), but succeeds in Firefox interestingly.

[cpainchaud]

New Firmware 2.964.0
Fails with Paypal+Chrome+Windows. "a problem has occured" then it seems to retry/wait forver but the key shows no activity

[westerguard]

For me too in Firefox and Edge.
I can add it in Android+Firefox.

[pbl987]

Fails with Paypal+Chrome+Windows. "a problem has occured" then it seems to retry/wait forver but the key shows no activity

Can you add more than one key to Paypal? I added my Yubikey first, now the option is gone :-(

[westerguard]

Can you add more than one key to Paypal? I added my Yubikey first, now the option is gone :-(

No, you can only add one fido2 key, and you can add TOTP as a backup.

[needs-coffee]

Also if you add a key and want to change it you need to deactivate all 2FA on your account and set it up again....

[epicfacethe3rd]

Currently fails on google chrome on android. Error is given saying "unable to connect"
Cannot add or use key to verify
I am on 2:20220822.0 with unlocked firmware

[pbl987]

So does this problem still exist for other users with newest firmware 2:20220822.0 ?

I did reset with Win 10 settings dialog, but it is not clear to me if it worked properly:

Maybe i should it reset with solo2-cli, but then it is nowhere mentioned how to do it. I guess it to be:

solo0.2.1.exe app oath reset

[needs-coffee]

Not oath - fido but the CLI doesnt show a reset option for this

[calgromi]

I was successful on google.com but failed on dropbox.com with firmware 2:20220822.0 using Safari version 16.0.

[msiqx9]

...but failed on dropbox.com with firmware 2:20220822.0 using Safari version 16.0.

I did initially have problems with registering the key on dropbox.com but eventually succeeded. I use Firefox and Chrome browsers in Windows 11. I suggest you try using a different computer for the initial key registration on dropbox.com.

[calgromi]

Thanks for the answer. I've just tried that on a Windows 10 PC with Firefox 104.0.2 and Edge. Again no success, error popup says: "The security key can't be read. Please try again." I've given up so far and will wait for the next firmware and FIDO2 certification.

[msiqx9]

Maybe try a Chrome browser on the Windows 10 PC. Once you manage to register the Solo v2 on Dropbox, it seems to work flawlessly on dropbox on any browser.

[calgromi]

Tried Opera on macOS Ventura - no success. Finally tried Chrome on macOS Monterey and succeeded. Further logins on Safari work as intended.

[ptman]

https://webauthn.firstyear.id.au/compat_test

[msiqx9]

My Solo v2 failed that test but my Solo Tap passed with some minor issues.

[DaAwesomeP]

As of 2023-07-20 and firmware 2:20220822.0 (2.964.0) my Solo V2 is failing in Firefox 115.0.2:

[pocki]

I have problems on Salesforce Sage People (Edge) with the latest firmware 2:20220822.0
Before trying to add i reseted the key with windows to factory settings (like shown in post discussioncomment-3843570 )

I thought that the problem with key length of max 255 chars is fixed in this version?

[tehabe]

I have issues with Safari, for sites like Google or Synology DSM keys can't be registered with Safari but they can be used. Nextcloud works neither in Safari nor Chrome, it get stuck at the "add key". In iOS 16.3 Apple adds securiy key support to their Apple ID, I hope the Solokeys work for that. Also I kinda hope the issues with Safari are in bug in the Solo 2's firmware because Apple is not well known to fix bugs quickly.

[DaAwesomeP]

See this issue, I am having issues with Microsoft, Paypal, and Gandi on firmware 2:20220822.0 (2.964.0): solokeys/solo2-cli#108

[bcecchinato]

Looks like that the last firmware is bugged with CTAP2. If you are using firefox you can disable it in about:config by setting the key security.webauthn.ctap2 to false. It allowed me to register my new key on some sites (except google and github that are not working at all).

Not the best solution, but at least the key is usable a bit.