🐛 Bug Report: Docker new install /login/setup does not allow passkey setup. #231

Closed
opened 2025-10-09 16:33:54 +03:00 by OVERLORD · 4 comments
Owner

Originally created by @Yonder711 on GitHub.

Reproduction steps

When attempting the initial setup on a docker new install and going to the /login/setup it does not take me to the setting page to setup a passkey. It does not behave like the demo does. It only asks for the new passkey and appears stuck in a bit of a loop. It is the same as the comment on the end of Bug #360.

Expected behavior

It should take me to /settings page if it is to behave as the online demo does. Allow for Passkey setup and then allow login.

Actual Behavior

Image
Image
Image
The initial start does not take me to setup and only to authenticate which i cannot do.

Version and Environment

Deb 12
Docker compose setup as per the recommended instructions.
The pull was from today and i would expect to be the latest of 53

Log Output

Web console shows:
CX8HSG55.js:1 startAuthentication() was not called correctly. It will try to continue with the provided options, but this call should be refactored to use the expected call structure instead. See https://simplewebauthn.dev/docs/packages/browser#typeerror-cannot-read-properties-of-undefined-reading-challenge for more information.
D @ CX8HSG55.js:1
B @ 8.CB_SYT5N.js:1
await in B
j @ Cz0SBzgo.js:1
click @ Cz0SBzgo.js:1
j @ Cz0SBzgo.js:1
(anonymous) @ Cz0SBzgo.js:1
(anonymous) @ C2Dn4pW3.js:1
Pe @ C2Dn4pW3.js:1
a @ C2Dn4pW3.js:1Understand this warning
BPfOPGdp.js:1 Error: WebAuthn is not supported in this browser
at D (CX8HSG55.js:1:1843)
at HTMLButtonElement.B (8.CB_SYT5N.js:1:3736)

Originally created by @Yonder711 on GitHub. ### Reproduction steps When attempting the initial setup on a docker new install and going to the /login/setup it does not take me to the setting page to setup a passkey. It does not behave like the demo does. It only asks for the new passkey and appears stuck in a bit of a loop. It is the same as the comment on the end of Bug #360. ### Expected behavior It should take me to /settings page if it is to behave as the online demo does. Allow for Passkey setup and then allow login. ### Actual Behavior ![Image](https://github.com/user-attachments/assets/1eb0f196-24b3-403e-8f2f-22f643b5fd5b) ![Image](https://github.com/user-attachments/assets/ca75bb37-d61b-41c4-af57-7baf94b229df) ![Image](https://github.com/user-attachments/assets/586ace5a-c3e9-4fde-9e36-602e366c56f2) The initial start does not take me to setup and only to authenticate which i cannot do. ### Version and Environment Deb 12 Docker compose setup as per the recommended instructions. The pull was from today and i would expect to be the latest of 53 ### Log Output Web console shows: CX8HSG55.js:1 startAuthentication() was not called correctly. It will try to continue with the provided options, but this call should be refactored to use the expected call structure instead. See https://simplewebauthn.dev/docs/packages/browser#typeerror-cannot-read-properties-of-undefined-reading-challenge for more information. D @ CX8HSG55.js:1 B @ 8.CB_SYT5N.js:1 await in B j @ Cz0SBzgo.js:1 click @ Cz0SBzgo.js:1 j @ Cz0SBzgo.js:1 (anonymous) @ Cz0SBzgo.js:1 (anonymous) @ C2Dn4pW3.js:1 Pe @ C2Dn4pW3.js:1 a @ C2Dn4pW3.js:1Understand this warning BPfOPGdp.js:1 Error: WebAuthn is not supported in this browser at D (CX8HSG55.js:1:1843) at HTMLButtonElement.B (8.CB_SYT5N.js:1:3736)
OVERLORD added the bug label 2025-10-09 16:33:54 +03:00
Author
Owner

@Yonder711 commented on GitHub:

Note the screen shots added in the opposite order. Please view from bottom to top.

@Yonder711 commented on GitHub: Note the screen shots added in the opposite order. Please view from bottom to top.
Author
Owner

@stonith404 commented on GitHub:

You have to add a reverse proxy in front to enable https. I'm converting this to a discussion as this is not a bug of Pocket ID.

@stonith404 commented on GitHub: You have to add a reverse proxy in front to enable https. I'm converting this to a discussion as this is not a bug of Pocket ID.
Author
Owner

@Yonder711 commented on GitHub:

I have attempted to try https again and it is not responding with or without the port 3000.
I was not using https as the documentation specifically stated only http at the end of the docker install section.
Also http was the only way a webui was seen.

Image

@Yonder711 commented on GitHub: I have attempted to try https again and it is not responding with or without the port 3000. I was not using https as the documentation specifically stated only http at the end of the docker install section. Also http was the only way a webui was seen. ![Image](https://github.com/user-attachments/assets/d464accc-e37a-4c1a-a000-c2fe28eb295b)
Author
Owner

@kmendell commented on GitHub:

You need to access pocket id over https this is a requirement of the webauthn api.

@kmendell commented on GitHub: You need to access pocket id over `https` this is a requirement of the webauthn api.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/pocket-id-pocket-id-2#231