Sign In, 2Fa with Security Keys(YubiKey) not working, "Not Registered with this website" #14111

Open
opened 2025-11-02 11:03:13 -06:00 by GiteaMirror · 5 comments
Owner

Originally created by @jalanga on GitHub (Feb 7, 2025).

Description

Adding security key is working.
Signing in with it, I get: "You're using a security key that's not registered with this website"

Using inside docker with traefik as reverse proxy.

ROOT_URL and DOMAIN are set correctly
GITEA__server__ROOT_URL=https://gitea.example.com/
GITEA__server__DOMAIN=gitea.example.com

The demo website is not working, but the issue can be reproduced on the main site, actually now I can't access the account created.

Gitea Version

docker.io/gitea/gitea:1.23.3-rootless

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

Image

Git Version

Operating System

ubuntu

How are you running Gitea?

Docker + traefik

Database

PostgreSQL

Originally created by @jalanga on GitHub (Feb 7, 2025). ### Description Adding security key is working. Signing in with it, I get: "You're using a security key that's not registered with this website" Using inside docker with traefik as reverse proxy. ROOT_URL and DOMAIN are set correctly GITEA__server__ROOT_URL=https://gitea.example.com/ GITEA__server__DOMAIN=gitea.example.com The demo website is not working, but the issue can be reproduced on the **main site**, actually now I can't access the account created. ### Gitea Version docker.io/gitea/gitea:1.23.3-rootless ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots ![Image](https://github.com/user-attachments/assets/659b12e5-081b-4d82-9fd7-54dff518932a) ### Git Version - ### Operating System ubuntu ### How are you running Gitea? Docker + traefik ### Database PostgreSQL
GiteaMirror added the topic/authenticationtype/bug labels 2025-11-02 11:03:13 -06:00
Author
Owner

@techknowlogick commented on GitHub (Feb 8, 2025):

Which tool/device are you using for your passkey?

@techknowlogick commented on GitHub (Feb 8, 2025): Which tool/device are you using for your passkey?
Author
Owner

@jalanga commented on GitHub (Feb 8, 2025):

YubiKey 5c Nfc. On MacOS

I had tested more:

Adding the security key through chromium browser (Google Chrome, Brave) will result in the error above. KO
Adding the security key through Safari, Sign in will work with all browsers. OK

@jalanga commented on GitHub (Feb 8, 2025): YubiKey 5c Nfc. On MacOS I had tested more: Adding the security key through chromium browser (Google Chrome, Brave) will result in the error above. KO Adding the security key through Safari, Sign in will work with all browsers. OK
Author
Owner

@tiran133 commented on GitHub (Feb 13, 2025):

Yes, I can confirm this.

Creating a Passkey with chromium based browsers does not seem to work. I used Vivaldi.
Creating a Passkey with Safari and then logging in with Vivaldi via Passkey works.
I used a YubiKey 5c NCF and a Nano both the same result.

@tiran133 commented on GitHub (Feb 13, 2025): Yes, I can confirm this. Creating a Passkey with chromium based browsers does not seem to work. I used Vivaldi. Creating a Passkey with Safari and then logging in with Vivaldi via Passkey works. I used a YubiKey 5c NCF and a Nano both the same result.
Author
Owner

@BingYanchi commented on GitHub (Aug 12, 2025):

Yes. This issue only occurs during secondary verification after logging in.

If you directly use the "Sign in with a passkey" option at the bottom of the login page without logging in first, the problem does not occur. The issue has also been reproduced on the official site.

Using Yubikey 5 NFC, Chrome

@BingYanchi commented on GitHub (Aug 12, 2025): Yes. This issue only occurs during secondary verification after logging in. If you directly use the "Sign in with a passkey" option at the bottom of the login page without logging in first, the problem does not occur. The issue has also been reproduced on the official site. Using Yubikey 5 NFC, Chrome
Author
Owner

@alanzheng88 commented on GitHub (Aug 30, 2025):

i'm also getting the same error with yubikey 5c nano when going through the user/pass + webauth flow

this doesnt happen if we go through the "Sign in with a passkey" flow.

shouldn't both behave the same?

@alanzheng88 commented on GitHub (Aug 30, 2025): i'm also getting the same error with yubikey 5c nano when going through the user/pass + webauth flow this doesnt happen if we go through the "Sign in with a passkey" flow. shouldn't both behave the same?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#14111