🐛 Bug Report: Passkey stopped working and redeploy can't create or save new #95

Closed
opened 2025-10-07 00:01:27 +03:00 by OVERLORD · 3 comments
Owner

Originally created by @NightHawkATL on GitHub.

Reproduction steps

I was working on completing the setup a while back and I had portainer setup and it worked. I removed that as an OIDC and the next time I went to login, the passkey in my Bitwarden browser extension/Vaultwarden wouldn't allow me to login anymore. I removed my passkey and shut down the container for a while.

I started it back up to update the image to the latest stable and I then shut it down to delete all but the GeoLite DB file. After starting it back up, I went to the https://FDQN/setup page and created a new account. When I went to save the new passkey, I keep getting an error..

Image

Docker Compose:

services:
  pocket-id:
    image: ghcr.io/pocket-id/pocket-id:latest
    container_name: pocket-id
    network_mode: bridge
    restart: unless-stopped
    environment:
    # See the documentation for more information: https://pocket-id.org/docs/configuration/environment-variables
      - PUBLIC_APP_URL=https://pid.myservweb.com
      - TRUST_PROXY=true
      - MAXMIND_LICENSE_KEY=########
      - GEOLITE_DB_URL=https://download.maxmind.com/app/geoip_download?edition_id=GeoLite2-City&license_key=%s&suffix=tar.gz
      - GEOLITE_DB_PATH=/app/data/GeoLite2-City.mmdb
      - PUID=1000
      - PGID=1000
      - HOST=0.0.0.0
    ports:
      - 1411:1411
    volumes:
      - /portainer/Files/AppData/Config/pocket-id:/app/data
    # Optional healthcheck  
    healthcheck:
      test: "curl -f http://localhost:1411/healthz"
      interval: 1m30s
      timeout: 5s
      retries: 2
      start_period: 10s

Expected behavior

work as expected without errors

Actual Behavior

it doesn't create or save passkeys as expected.

Version and Environment

Latest Version 1.6.4

Docker Compose with Portainer EE.

Log Output

Image
Originally created by @NightHawkATL on GitHub. ### Reproduction steps I was working on completing the setup a while back and I had portainer setup and it worked. I removed that as an OIDC and the next time I went to login, the passkey in my Bitwarden browser extension/Vaultwarden wouldn't allow me to login anymore. I removed my passkey and shut down the container for a while. I started it back up to update the image to the latest stable and I then shut it down to delete all but the GeoLite DB file. After starting it back up, I went to the https://FDQN/setup page and created a new account. When I went to save the new passkey, I keep getting an error.. <img width="395" height="86" alt="Image" src="https://github.com/user-attachments/assets/915dccb7-523e-4efa-a8af-2001ca7c121f" /> Docker Compose: ``` services: pocket-id: image: ghcr.io/pocket-id/pocket-id:latest container_name: pocket-id network_mode: bridge restart: unless-stopped environment: # See the documentation for more information: https://pocket-id.org/docs/configuration/environment-variables - PUBLIC_APP_URL=https://pid.myservweb.com - TRUST_PROXY=true - MAXMIND_LICENSE_KEY=######## - GEOLITE_DB_URL=https://download.maxmind.com/app/geoip_download?edition_id=GeoLite2-City&license_key=%s&suffix=tar.gz - GEOLITE_DB_PATH=/app/data/GeoLite2-City.mmdb - PUID=1000 - PGID=1000 - HOST=0.0.0.0 ports: - 1411:1411 volumes: - /portainer/Files/AppData/Config/pocket-id:/app/data # Optional healthcheck healthcheck: test: "curl -f http://localhost:1411/healthz" interval: 1m30s timeout: 5s retries: 2 start_period: 10s ``` ### Expected behavior work as expected without errors ### Actual Behavior it doesn't create or save passkeys as expected. ### Version and Environment Latest Version 1.6.4 Docker Compose with Portainer EE. ### Log Output <img width="1095" height="429" alt="Image" src="https://github.com/user-attachments/assets/d2687986-7f3f-43c8-9037-cbc84cf9ebcd" />
Author
Owner

@NightHawkATL commented on GitHub:

Also, the emails reference "localhost" and not the FDQN I have setup through my reverse proxy.

Second request to login with a code emailed to me, didn't come through and I am now locked out without starting over.

@NightHawkATL commented on GitHub: Also, the emails reference "localhost" and not the FDQN I have setup through my reverse proxy. Second request to login with a code emailed to me, didn't come through and I am now locked out without starting over.
Author
Owner

@NightHawkATL commented on GitHub:

That seems to have fixed it. I will keep an eye on things and see if I run into any other issues.

Thank you

@NightHawkATL commented on GitHub: That seems to have fixed it. I will keep an eye on things and see if I run into any other issues. Thank you
Author
Owner

@kmendell commented on GitHub:

Change PUBLIC_APP_URL to just APP_URL and see if that fixes at least the login issue.

@kmendell commented on GitHub: Change `PUBLIC_APP_URL` to just `APP_URL` and see if that fixes at least the login issue.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/pocket-id#95