Got two Solo2 keys : usb-c and usb-a. Latest firmware. Systematic "unknwon error" on use

[gilbert-fernandes]

Two brand new solo keys.
One in USB-A and one in USB-C
Both are "hacker" models with unlocked firmware.

Installed solo2-cli and build it using cargo.
Then upgraded the two keys firmwares :

USB-A : Solo 2 88E370EEB9BF535D8BE663F07199AF8B (CTAP+PCSC, firmware 2:20220822.0, unlocked)
USB-C : Solo 2 0D07FCA9C11BE25AB005312E3D6851E3 (CTAP+PCSC, firmware 2:20220822.0, unlocked)

Went to Codeberg. I already have a registered key.
Choose to add the Solo Key.
I only have the USB-C key pluggued. Firefox asks me to press on key
I touch the key and get an "unknwon error" from Firefox.

I remove the USB-C key. Plug the USB-A key.
Try to register the Solo2 key. "unknwon error"

I have installed the file 70-solo2.rules in path :
/etc/udev/rules.d
And udev has been restarted.

On this same machine, I have two other keys that work without any issue or problem :
A Yubikey in USB-C format
A USB-A key-id.com key

The Solo2 keys work nowhere. Usb-C and Usb-A keys do not work on ANY website where all the other keys do work.

I have thus deleted the current registered key-id.com key from Codeberg
Plugged the Solo2 key in USB-C format
Error I get is :

Could not read your security key.
unknown error

Remove the Solo2 USB-C key and plug the Solo2 USB-A key.
Try to register key on Codeberg :

Could not read your security key.
unknown error

Before I am allowed to press the sides of the key, Firefox displays a message that says :

codeberg.og is requesting extended information about your security key

So I think that the Solo2 keys fail to give access to whatever that "extended information" is.

I now plug again the key-id.com USB and register the key :
I get the same Firefox message. Led on key blinks. I press the button
It immediatly works and the key is registered.
It's a standard FIDO U2F key that required no configuratoin, nothing. Just works out of the box.

But I would like to use at least 2 keys so I won't lose access if I lose one of them :(

[fl-la]

Had a similiar issue. Try the same in chrome. You have to set a pin before, somehow firefox does not handle this correctly. Chrome asks you to set a pin. Once set, you can proceed in firefox.