When entering my 1.0 anchor number I get the following.
I am using physical Passkey(YubiKey) to login via Windows. No other devices linked. Recovery phrases are stored physically as well.
I tried multiple browsers, and multiple anchor numbers, all give the same error.
I heard about the January 26 Update but was under the impression that one could still access their funds/neurons via the NNS.
Especially because of these statements in the FAQ:
“2. Do I need to upgrade before a certain date?
No. Internet Identity is a decentralized service, meaning you control your own upgrade timeline. There is no mandatory deadline. The upgrade will remain available indefinitely.
3. Will I lose access to Internet Identity 1.0 after upgrading?
No. Upgrading adds a new discoverable passkey for Internet Identity 2.0 without removing your existing Internet Identity 1.0 authentication methods.”
Any help would be greatly appreciated since currently I am unable to access all of my funds.
Well, it would seem that your II number is not correct. If it were correct, you should be able to upgrade. Are you sure you are typing it in correctly or using a valid one? Are you sure you are remembering it correctly?
Have you tried using your recovery phrase instead??
Have a look at identity.ic0.app/self-service, it should list all your identity numbers previously used on that domain (assuming you’ve signed into that particular browser before and didn’t clear browser history).
You can indeed also gain access through your recovery phrase at id.ai/recovery.
If you could share a JSON export from the above self-service page with support (link in footer on id.ai), we would highly appreciate it. This will help us gain insight in why you might possibly be getting errors.
So, I managed to regain access to my main Identity. The problem was that I was still on Windows 10, so the authflow didn’t work somehow. After installing W11 I could upgrade my Identity.
Now after linking a new Yubikey it still gave me problems. I used the seed phrase recovery option, linked a new Yubikey passkey, since I didn’t have the PIN anymore, then I deleted a Windows Hello Passkey, tried to log back in with the new physical passkey, where it showed me my new name, which I just gave the Identity, so it knew the yubikey is linked to the identity but when I entered the PIN it gave:
“Unexpected error
**Credential not found. Either you removed the passkey from the identity or this identity needs to be migrated.”
**
Edit: I deleted the Yubi Passkey and re-added it, as well as one on my phone and now everything works just fine.
I still find it quite weird that id.ai will log you out if you just refresh the page, but the NNS page will still be logged in if you close the tab and then reopen it..
This is by design, the id.ai page has access to every application that your identity uses. This means in practice, for security reasons, that you’ll always have to re-authenticate when reloading/revisiting the page.
This might change over time while we continue to improve upon the II user experience, e.g. implementing more fine grained approaches to authentication where it’s only needed when making actual changes.
