# Yellow LED and unresponsive for a while after use as SSH-key

**URL:** <https://onlykey.discourse.group/t/yellow-led-and-unresponsive-for-a-while-after-use-as-ssh-key/82>\
**Category:** Uncategorized\
**Created:** [October 30, 2020, 5:03pm UTC](https://onlykey.discourse.group/t/yellow-led-and-unresponsive-for-a-while-after-use-as-ssh-key/82 "2020-10-30T17:03:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![NCLI](https://yyz2.discourse-cdn.com/free1/user_avatar/onlykey.discourse.group/ncli/32/20_2.png) [@NCLI](https://onlykey.discourse.group/u/NCLI)\
**Post date:** [October 30, 2020, 5:03pm UTC](https://onlykey.discourse.group/t/yellow-led-and-unresponsive-for-a-while-after-use-as-ssh-key/82/1 "2020-10-30T17:03:37Z")

</div>

As the title says, the Onlykey LED turns yellow, and it becomes completely unresponsive for 20-30 seconds after having been used for SSH authentication via onlykey-agent.

This only happens after a successful login, with correct confirmation code. Is this intentional behavior, and if so, is there a way to reduce this timeout? I often need to enter a root password pretty much immediately after logging in. What I do know is physically unplug the Onlykey after login, then re-insert it and type my PIN. It’s annoying, but way faster than waiting for the LED to turn green, and functionality to return to normal.

---

<div class="post-metadata">

**Author:** ![t11](https://avatars.discourse-cdn.com/v4/letter/t/8e7dd6/32.png) [@t11](https://onlykey.discourse.group/u/t11)\
**Post date:** [November 27, 2020, 9:28pm UTC](https://onlykey.discourse.group/t/yellow-led-and-unresponsive-for-a-while-after-use-as-ssh-key/82/2 "2020-11-27T21:28:56Z")

</div>

Yes, with the next version of firmware and onlykey-agent this will be fixed