[BUG] Startup issues with v5 - report here

[el-tiuri]

v5 fails to start up using the recommended docker-compose file.

Logs:
2026-03-03T10:18:24Z INF cmd/tinyauth/tinyauth.go:114 > Starting tinyauth log_stream=app version=v5.0.0
2026-03-03T10:18:24Z fatal Failed to execute command | error=command tinyauth error: failed to bootstrap app: parse "://": missing protocol scheme

[kusk]

Same error here.

[steveiliop56]

Can you share the docker compose file you used? Is it the one from the documentation or did you customize it?

[kusk]

networks:
  caddy_network:
    name: caddy_network
    external: true

services:
  tinyauth:
    container_name: tinyauth
    image: ghcr.io/steveiliop56/tinyauth:latest
    restart: unless-stopped
    volumes:
      - /data/tinyauth:/data
      - /var/run/docker.sock:/var/run/docker.sock
    environment:
      - TINYAUTH_OAUTH_PROVIDERS_GOOGLE_CLIENTID=...
      - TINYAUTH_OAUTH_PROVIDERS_GOOGLE_CLIENTSECRET=...
      - TINYAUTH_OAUTH_WHITELIST=….
      - TINYAUTH_APP_URL=http://tinyauth.....com
    labels:
      caddy: http://tinyauth.....com
      caddy.reverse_proxy: "{{upstreams 3000}}"
      tinyauth.apps.tinyauth.config.domain: tinyauth…..com
    networks:
      - caddy_network

I have tried to migrate to the new config, but not sure I did it correctly.

[kusk]

I found the error myself. I had to change from TINYAUTH_APP_URL to TINYAUTH_APPURL without the last underscore.

[steveiliop56]

@kusk and @el-tiuri there seems to be an misunderstanding as to the migration instructions. The migration does not only involve adding the TINYAUTH_ prefix but also changing and categorizing most of the configuration options. For your static configuration options (so everything but the OAuth providers) you can use the automated configuration migrator (everything happens browser side). As for the OAuth configuration, please refer to the documentation for all of the new options you should use.

[kusk]

Yeah, I ended up using both the migator and the documentation to fix the problem.

[TonyCollett]

The Migrator doesn't seem to pick up values correctly.

On the left is my original working configuration (blurred of course) and on the right is what was automatically migrated. I'm still having an issue with starting TinyAuth

EDIT: Worked out my issue with the configuration values (CLIENT_ID needed to be CLIENTID, and so on) and got it running. Might want to include a full list of changes (i.e. PROVIDERS_[NAME]_CLIENT_ID is now TINYAUTH_OAUTH_PROVIDERS_[NAME]_CLIENTID)

[steveiliop56]

Yes there is a warning about dynamic values below. They are not supported by the migrator, you will have to migrate them manually.

[TonyCollett]

Yes there is a warning about dynamic values below. They are not supported by the migrator, you will have to migrate them manually.

Ahh, I didn't realise that. All good then. Thanks for the update

[sebinistor]

Same issue in the UNRAID community edition when pulling with tag :latest
I reverted to 4.1.0 as it is not clear which variable of the container needs an updated and to what...

[YouveGotMeowxy]

I'm getting a similar error:

my .env file:

TZ="America/Chicago"

TINYAUTH_APPURL="https://tinyauth.domain.com"
TINYAUTH_DATABASEPATH="/data/tinyauth.db"
TINYAUTH_RESOURCESDIR="/data/resources"
TINYAUTH_LOGJSON="true"
TINYAUTH_LOGLEVEL="trace"
TINYAUTH_SERVER_PORT="3000"
TINYAUTH_AUTH_USERSFILE="/data/users"
TINYAUTH_AUTH_SECURECOOKIE="true"
TINYAUTH_UI_TITLE="GATE"
TINYAUTH_UI_FORGOTPASSWORDMESSAGE="Contact admin to reset your password"

[steveiliop56]

@YouveGotMeowxy seems like the environment variables are not passed to Tinyauth. But, even if they are passed configuration will most likely fail to parse due to the following options:

TINYAUTH_DATABASEPATH="/data/tinyauth.db"
TINYAUTH_RESOURCESDIR="/data/resources"
TINYAUTH_LOGJSON="true"
TINYAUTH_LOGLEVEL="trace"

They should be:

TINYAUTH_DATABASE_PATH="/data/tinyauth.db"
TINYAUTH_RESOURCES_PATH="/data/resources"
TINYAUTH_LOG_JSON="true"
TINYAUTH_LOG_LEVEL="trace"

@sebinistor basically the entire configuration changed. The environment variables and CLI flags now follow a new scheme. You can visit the reference, find the new environment variable that fits your use case and migrate it. Alternatively, you can use the config migrator (as mentioned won't work for OAuth variables, you will have to manually migrate those).