Still required to register for new account despite ACCOUNT_REGISTRATION=false and ALLOW_UNAUTHENTICATED=true

[tejashah88]

I have the following docker-compose.yml file to launch this app locally on my PC for personal use.

services:
  convertx:
    image: ghcr.io/c4illin/convertx
    container_name: convertx
    restart: unless-stopped
    ports:
      - "3000:3000"
    environment:
      - ACCOUNT_REGISTRATION=false
      - ALLOW_UNAUTHENTICATED=true
      - AUTO_DELETE_EVERY_N_HOURS=0
      - HTTP_ALLOWED=true
    volumes:
      - ./data:/app/data

I tried running this with Docker Compose but when opening up the webpage on localhost:3000, it leads me to a setup page, where I'm required to register for an account despite specifying ACCOUNT_REGISTRATION=false and ALLOW_UNAUTHENTICATED=true and HTTP_ALLOWED=true. This was tested on an Incognito Window using the Brave Browser (Chrome-based) on a Windows 10 Pro Laptop.

Peering through the source code, I think I found a potential culprit. The FIRST_RUN variable is set when no users exist, but the ALLOW_UNAUTHENTICATED flag is not checked in conjunction, which causes the routing to send the user to /setup until a user is finally found in the database.

I can imagine a temporary workaround is to put a dummy user into the database when ALLOW_UNAUTHENTICATED is set to true, but I'd like to know what you think.

[tejashah88]

One obvious thing to note is that after creating the user, shutting down the container and restarting it back up, it won't prompt me for the login details since there's at least one user in the database.

[armond-avanes]

I'm facing the exact same issue!