NK 3 fails after factory reset

Nitrokeys
1

I am running Fedora KDE 43 and attempting to install Nitrokey 3. I have installed rules to /etc/udev/rules.d/, (sudo ls /etc/udev/rules.d/.
41-nitrokey.rules

)

and successfully restarted services.

But I can’t use GUI app or Nitropy CLI to either set or change PINs.

nitropy fido2 reset gives error as cut and pasted fron log file

ymr@fedora:~$ ls /tmp/nitropy-20260313T163416-c1h9d2ul.log

/tmp/nitropy-20260313T163416-c1h9d2ul.log
ymr@fedora:~$ cat /tmp/nitropy-20260313T163416-c1h9d2ul.log
164 INFO pynitrokey.cli Timestamp: 2026-03-13 16:34:16.486146
165 INFO pynitrokey.cli OS: uname_result(system=‘Linux’, node=‘fedora’, release=‘6.19.6-200.fc43.x86_64
‘, version=’#1 SMP PREEMPT_DYNAMIC Thu Mar 5 00:10:35 UTC 2026’, machine=‘x86_64’)
165 INFO pynitrokey.cli Python version: 3.14.3
165 INFO pynitrokey.cli Cli arguments: [‘fido2’, ‘reset’]
165 INFO pynitrokey.cli pynitrokey version: 0.11.3
166 INFO pynitrokey.cli cryptography version: 46.0.5
166 INFO pynitrokey.cli fido2 version: 2.1.1
166 INFO pynitrokey.cli nethsm version: 2.0.1
167 INFO pynitrokey.cli nitrokey version: 0.4.2
167 INFO pynitrokey.cli pyusb version: 1.3.1
167 DEBUG root print: Reset is only possible within 10secs after plugging in the device.
167 DEBUG root print: Please (re-)plug in your Nitrokey FIDO2 now!
34507 DEBUG root print: choosing: yes
34507 DEBUG root print: Press key to confirm – again, your credentials will be lost!!!
34559 DEBUG fido2.hid.linux Failed opening device /dev/hidraw1
Traceback (most recent call last):
File “/home/ymr/.local/share/pipx/venvs/pynitrokey/lib64/python3.14/site-packages/fido2/hid/linux.py”, line
96, in list_descriptors
devices.append(get_descriptor(hidraw))
~~~~~~~~~~~~~~^^^^^^^^
File “/home/ymr/.local/share/pipx/venvs/pynitrokey/lib64/python3.14/site-packages/fido2/hid/linux.py”, line
53, in get_descriptor
with open(path, “rb”) as f:
~~~~^^^^^^^^^^^^
PermissionError: [Errno 13] Permission denied: ‘/dev/hidraw1’
34560 DEBUG fido2.hid.linux Failed opening device /dev/hidraw0
Traceback (most recent call last):
File “/home/ymr/.local/share/pipx/venvs/pynitrokey/lib64/python3.14/site-packages/fido2/hid/linux.py”, line
96, in list_descriptors
devices.append(get_descriptor(hidraw))
~~~~~~~~~~~~~~^^^^^^^^
File “/home/ymr/.local/share/pipx/venvs/pynitrokey/lib64/python3.14/site-packages/fido2/hid/linux.py”, line
53, in get_descriptor
with open(path, “rb”) as f:
~~~~^^^^^^^^^^^^
PermissionError: [Errno 13] Permission denied: ‘/dev/hidraw0’
34867 DEBUG fido2.hid Got keepalive status: 02
35119 DEBUG fido2.hid Got keepalive status: 02
35366 DEBUG fido2.hid Got keepalive status: 02
35614 DEBUG fido2.hid Got keepalive status: 02
35866 DEBUG fido2.hid Got keepalive status: 02
36114 DEBUG fido2.hid Got keepalive status: 02
36366 DEBUG fido2.hid Got keepalive status: 02
36614 DEBUG fido2.hid Got keepalive status: 02
36862 DEBUG fido2.hid Got keepalive status: 02
37115 DEBUG fido2.hid Got keepalive status: 02
37363 DEBUG fido2.hid Got keepalive status: 02
37615 DEBUG fido2.hid Got keepalive status: 02
37862 DEBUG fido2.hid Got keepalive status: 02
38111 DEBUG fido2.hid Got keepalive status: 02
38363 DEBUG fido2.hid Got keepalive status: 02
38611 DEBUG fido2.hid Got keepalive status: 02
38858 DEBUG fido2.hid Got keepalive status: 02
39111 DEBUG fido2.hid Got keepalive status: 02
39358 DEBUG fido2.hid Got keepalive status: 02
39611 DEBUG fido2.hid Got keepalive status: 02
39858 DEBUG fido2.hid Got keepalive status: 02
40106 DEBUG fido2.hid Got keepalive status: 02
40359 DEBUG fido2.hid Got keepalive status: 02
40607 DEBUG fido2.hid Got keepalive status: 02
40858 DEBUG fido2.hid Got keepalive status: 02
41107 DEBUG fido2.hid Got keepalive status: 01
41355 DEBUG fido2.hid Got keepalive status: 02
41607 DEBUG fido2.hid Got keepalive status: 02
41855 DEBUG fido2.hid Got keepalive status: 02
42103 DEBUG fido2.hid Got keepalive status: 02
42355 DEBUG fido2.hid Got keepalive status: 02
42603 DEBUG fido2.hid Got keepalive status: 02
42855 DEBUG fido2.hid Got keepalive status: 02
43103 DEBUG fido2.hid Got keepalive status: 02
43351 DEBUG fido2.hid Got keepalive status: 02
43603 DEBUG fido2.hid Got keepalive status: 02
43850 DEBUG fido2.hid Got keepalive status: 02
44103 DEBUG fido2.hid Got keepalive status: 02
44351 DEBUG fido2.hid Got keepalive status: 02
44599 DEBUG fido2.hid Got keepalive status: 02
44850 DEBUG fido2.hid Got keepalive status: 02
45099 DEBUG fido2.hid Got keepalive status: 02
45347 DEBUG fido2.hid Got keepalive status: 02
45599 DEBUG fido2.hid Got keepalive status: 02
45846 DEBUG fido2.hid Got keepalive status: 02
46098 DEBUG fido2.hid Got keepalive status: 02
46347 DEBUG fido2.hid Got keepalive status: 02
46595 DEBUG fido2.hid Got keepalive status: 02
46846 DEBUG fido2.hid Got keepalive status: 02
47095 DEBUG fido2.hid Got keepalive status: 02
47347 DEBUG fido2.hid Got keepalive status: 02
47594 DEBUG fido2.hid Got keepalive status: 02
47842 DEBUG fido2.hid Got keepalive status: 02
48095 DEBUG fido2.hid Got keepalive status: 02
48343 DEBUG fido2.hid Got keepalive status: 02
48591 DEBUG fido2.hid Got keepalive status: 02
48842 DEBUG fido2.hid Got keepalive status: 02
49091 DEBUG fido2.hid Got keepalive status: 02
49343 DEBUG fido2.hid Got keepalive status: 02
49591 DEBUG fido2.hid Got keepalive status: 02
49838 DEBUG fido2.hid Got keepalive status: 02
50091 DEBUG fido2.hid Got keepalive status: 02
50339 DEBUG fido2.hid Got keepalive status: 02
50586 DEBUG fido2.hid Got keepalive status: 02
50839 DEBUG fido2.hid Got keepalive status: 02
51087 DEBUG fido2.hid Got keepalive status: 02
51338 DEBUG fido2.hid Got keepalive status: 02
51587 DEBUG fido2.hid Got keepalive status: 02
51834 DEBUG fido2.hid Got keepalive status: 02
52086 DEBUG fido2.hid Got keepalive status: 02
52335 DEBUG fido2.hid Got keepalive status: 02
52583 DEBUG fido2.hid Got keepalive status: 02
52834 DEBUG fido2.hid Got keepalive status: 02
53082 DEBUG fido2.hid Got keepalive status: 02
53335 DEBUG fido2.hid Got keepalive status: 02
53583 DEBUG fido2.hid Got keepalive status: 02
53831 DEBUG fido2.hid Got keepalive status: 02
54082 DEBUG fido2.hid Got keepalive status: 02
54330 DEBUG fido2.hid Got keepalive status: 02
54583 DEBUG fido2.hid Got keepalive status: 02
54831 DEBUG fido2.hid Got keepalive status: 02
55079 DEBUG fido2.hid Got keepalive status: 02
55330 DEBUG fido2.hid Got keepalive status: 02
55578 DEBUG fido2.hid Got keepalive status: 02
55826 DEBUG fido2.hid Got keepalive status: 02
56078 DEBUG fido2.hid Got keepalive status: 02
56326 DEBUG fido2.hid Got keepalive status: 02
56578 DEBUG fido2.hid Got keepalive status: 02
56826 DEBUG fido2.hid Got keepalive status: 02
57075 DEBUG fido2.hid Got keepalive status: 02
57326 DEBUG fido2.hid Got keepalive status: 02
57574 DEBUG fido2.hid Got keepalive status: 02
57827 DEBUG fido2.hid Got keepalive status: 02
58074 DEBUG fido2.hid Got keepalive status: 02
58322 DEBUG fido2.hid Got keepalive status: 02
58575 DEBUG fido2.hid Got keepalive status: 02
58823 DEBUG fido2.hid Got keepalive status: 02
59071 DEBUG fido2.hid Got keepalive status: 02
59322 DEBUG fido2.hid Got keepalive status: 02
59571 DEBUG fido2.hid Got keepalive status: 02
59823 DEBUG fido2.hid Got keepalive status: 02
60071 DEBUG fido2.hid Got keepalive status: 01
60319 DEBUG fido2.hid Got keepalive status: 02
60570 DEBUG fido2.hid Got keepalive status: 02
60819 DEBUG fido2.hid Got keepalive status: 02
61067 DEBUG fido2.hid Got keepalive status: 02
61319 DEBUG fido2.hid Got keepalive status: 02
61567 DEBUG fido2.hid Got keepalive status: 02
61818 DEBUG fido2.hid Got keepalive status: 02
62067 DEBUG fido2.hid Got keepalive status: 02
62315 DEBUG fido2.hid Got keepalive status: 02
62566 DEBUG fido2.hid Got keepalive status: 02
62814 DEBUG fido2.hid Got keepalive status: 02
63062 DEBUG fido2.hid Got keepalive status: 02
63314 DEBUG fido2.hid Got keepalive status: 02
63562 DEBUG fido2.hid Got keepalive status: 02
63815 DEBUG fido2.hid Got keepalive status: 02
64062 DEBUG fido2.hid Got keepalive status: 02
64310 DEBUG fido2.hid Got keepalive status: 02
64562 DEBUG fido2.hid Got keepalive status: 02
64810 DEBUG fido2.hid Got keepalive status: 02
64898 DEBUG root print: Critical error:
64899 DEBUG root print: Reset failed (CTAP error: 0x2F - USER_ACTION_TIMEOUT)
64899 DEBUG root print: Did you confirm with a key-press 10secs after plugging in?
64899 DEBUG root print: Please re-try…
64899 DEBUG root listing all connected devices:
64906 DEBUG root :: ‘Nitrokey FIDO2’ keys
64906 DEBUG root :: ‘Nitrokey Start’ keys:
64935 DEBUG root :: ‘Nitrokey 3’ keys
64970 DEBUG root /dev/hidraw2: Nitrokey 3 2FBBC03B466539589D5F7025C246E0D4
64970 DEBUG root :: ‘Nitrokey Passkey’ keys
64979 DEBUG root print: ----------------------------------------------------------------------------

64979 DEBUG root print: Critical error occurred, exiting now
64979 DEBUG root print: Unexpected? Is this a bug? Would you like to get support/help?
64979 DEBUG root print: - You can report issues at: https://support.nitrokey.com/
64979 DEBUG root print: - Writing an e-mail to support@nitrokey.com is also possible
64979 DEBUG root print: - Please attach the log: ‘/tmp/nitropy-20260313T163416-c1h9d2ul.log’ with an
y support/help request!
64979 DEBUG root print: - Please check if you have udev rules installed:

2

Hello, as explained here:

it requires admin rights if you did not do the cmd with sudo could you then try.

And also you could try the reset with chromium based browser.

3

Hello and thank you for your email

First suggestion to rub with sudo does not work as below

mr@fedora:~$ sudo ~/.local/bin/nitropy fido2 reset
Command line tool to interact with Nitrokey devices 0.11.3
THIS COMMAND SHOULD NOT BE RUN AS ROOT!

Please install udev rules and run nitropy as regular user (without sudo).
We suggest using: https://raw.githubusercontent.com/Nitrokey/libnitrokey/master/data/41-nitrokey.rules
For more information, see: https://docs.nitrokey.com/software/nitropy/linux/udev.html

Set ALLOW_ROOT=1 environment variable to disable this warning.

Reset is only possible within 10secs after plugging in the device.
Please (re-)plug in your Nitrokey FIDO2 now!
Warning: Your credentials will be lost!!! continue? [(y)es/(n)o]: y
choosing: yes
Press key to confirm – again, your credentials will be lost!!!

y
Critical error:
Reset failed (CTAP error: 0x2F - USER_ACTION_TIMEOUT)
Did you confirm with a key-press 10secs after plugging in?
Please re-try…

4

USER_ACTION_TIMEOUT makes me wonder whether the Nitrokey wants your confirmation via touch to perform the reset. Did you try touching the touch “button” of your NK3?

5

Thank you for your response
I didnot touch the key.
I will try again

6

Thanks you. This was helpful - but not quite right
nitropy fido2 reset has worked successfully
mr@fedora:~$ nitropy fido2 reset
Command line tool to interact with Nitrokey devices 0.11.3
Reset is only possible within 10secs after plugging in the device.
Please (re-)plug in your Nitrokey FIDO2 now!
Warning: Your credentials will be lost!!! continue? [(y)es/(n)o]: y
choosing: yes
Press key to confirm – again, your credentials will be lost!!!
…aaaand they’re gone

But ymr@fedora:~$ nitropy fido2 status
Command line tool to interact with Nitrokey devices 0.11.3
Warning: This command only works with the Nitrokey FIDO2, not with other FIDO2
devices!
Critical error:
An unhandled exception occurred
Exception encountered: NoSoloFoundError(‘no Nitrokey FIDO2 found’)

(Attachment nitropy-20260315T075827-xde8bosf.log is missing)

7

That’s the same for me with a Nitrokey 3. I guess – as the command already says – it “only works with the Nitrokey FIDO2”, and thus not with the NK3. Try setting up your PIN and credentials using your web browser now.

Or try nitropy fido2 list-credentials or nitropy fido2 get-info.

8

No this is also working with the NK3.

I just tried on my side and it worked.

Even without sudo it worked.

What you need to make sure is to unplug and replug the Nitrokey just before entering "y” when it ask:

Warning: Your credentials will be lost!!! continue? [(y)es/(n)o]: y

Then you need to touch your Nitrokey and then the reset is done.

9

Please note that I was referring to “nitropy fido2 status” not working on the NK3.

It’s clear that “nitropy fido2 reset” works on the NK3. MRafael even confirmed that “nitropy fido2 reset” worked after I explained that touching the Nitrokey is required.

10

my bad yes you are right.

11

Yes, thanks you for that classification