github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-03-22 13:05:43 -05:00
Code Issues 447 Packages Projects Releases 9 Wiki Activity

Unable to Login #606

New Issue
Closed
opened 2025-11-01 21:00:13 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-01 21:00:13 -05:00
Owner
Copy Link

Originally created by @akorb90 on GitHub (Sep 10, 2025).

Description

Hello everyone,

today I realized something is broken with my vikunja installation. I'm unable to log into the web interface:

Image

I'm only using OIDC Login.

I'm not quite sure when it was working for the last time, I did an update like a week ago any maybe only used my webdav android app since then.

I had an collation error in the database as it didnt get updates properly:

db-1 | 2025-09-10T14:08:48.738699116Z 2025-09-10 14:08:48.738 UTC [209] WARNING: database "vikunja" has a collation version mismatch
db-1 | 2025-09-10T14:08:48.738727642Z 2025-09-10 14:08:48.738 UTC [209] DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.
db-1 | 2025-09-10T14:08:48.738738280Z 2025-09-10 14:08:48.738 UTC [209] HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE vikunja REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.

Fixed it with "ALTER DATABASE vikunja REFRESH COLLATION VERSION", now no more errors, but still can't login.

Any ideas on this? The logs don't show any error, diffrent browser doesn't work as well

Vikunja Version

latest docker image

Browser and version

brave, edge and firefox in current versions

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @akorb90 on GitHub (Sep 10, 2025). ### Description Hello everyone, today I realized something is broken with my vikunja installation. I'm unable to log into the web interface: <img width="1920" height="917" alt="Image" src="https://github.com/user-attachments/assets/35a5e829-b1e2-4e60-ae20-5440bfaf54b0" /> I'm only using OIDC Login. I'm not quite sure when it was working for the last time, I did an update like a week ago any maybe only used my webdav android app since then. I had an collation error in the database as it didnt get updates properly: db-1 | 2025-09-10T14:08:48.738699116Z 2025-09-10 14:08:48.738 UTC [209] WARNING: database "vikunja" has a collation version mismatch db-1 | 2025-09-10T14:08:48.738727642Z 2025-09-10 14:08:48.738 UTC [209] DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41. db-1 | 2025-09-10T14:08:48.738738280Z 2025-09-10 14:08:48.738 UTC [209] HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE vikunja REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. Fixed it with "ALTER DATABASE vikunja REFRESH COLLATION VERSION", now no more errors, but still can't login. Any ideas on this? The logs don't show any error, diffrent browser doesn't work as well ### Vikunja Version latest docker image ### Browser and version brave, edge and firefox in current versions ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2025-11-01 21:00:14 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Sep 10, 2025):

You'll need to set a publicurl. https://vikunja.io/docs/config-options/#1-service-publicurl

Closing as duplicate of https://github.com/go-vikunja/vikunja/issues/1303

@kolaente commented on GitHub (Sep 10, 2025): You'll need to set a publicurl. https://vikunja.io/docs/config-options/#1-service-publicurl Closing as duplicate of https://github.com/go-vikunja/vikunja/issues/1303
GiteaMirror commented 2025-11-01 21:00:14 -05:00
Author
Owner
Copy Link

@akorb90 commented on GitHub (Sep 11, 2025):

Hi,

I have already set the Publicurl beforre the update and it's pointing to the correct url. Here's my anonymized compose:

services:
  vikunja:
    image: vikunja/vikunja
    environment:
      VIKUNJA_SERVICE_PUBLICURL: https://notes.public.url
      VIKUNJA_DATABASE_HOST: db
      VIKUNJA_DATABASE_PASSWORD: ${VIKUNJA_DATABASE_PASSWORD}
      VIKUNJA_DATABASE_TYPE: postgres
      VIKUNJA_DATABASE_USER: ${VIKUNJA_DATABASE_USER}
      VIKUNJA_DATABASE_DATABASE: ${VIKUNJA_DATABASE_DATABASE}
      VIKUNJA_SERVICE_JWTSECRET: ${VIKUNJA_SERVICE_JWTSECRET}
    ports:
      - "1180:3456"
    volumes:
      - /opt/vikunja/files:/app/vikunja/files
      - /opt/vikunja/config.yml:/etc/vikunja/config.yml
    depends_on:
      db:
        condition: service_healthy
    restart: unless-stopped
    
  db:
    image: postgres:17
    environment:
      POSTGRES_PASSWORD: ${VIKUNJA_DATABASE_PASSWORD}
      POSTGRES_USER: ${VIKUNJA_DATABASE_USER}
    volumes:
      - /opt/vikunja/db:/var/lib/postgresql/data
    restart: unless-stopped
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -h localhost -U $$POSTGRES_USER"]
      interval: 2s

and the config.yaml:

auth:
  local:
    enabled: false
  openid:
    enabled: true
    redirecturl: "https://notes.puclic.url/auth/openid/"
    providers:
      - name: "authentik Login"
        authurl: "https://auth.public.url/application/o/vikunja/"
        logouturl: "https://auth.public.url/application/o/vikunja/end-session/"
        clientid: "clientid"
        clientsecret: "secret"
@akorb90 commented on GitHub (Sep 11, 2025): Hi, I have already set the Publicurl beforre the update and it's pointing to the correct url. Here's my anonymized compose: ``` services: vikunja: image: vikunja/vikunja environment: VIKUNJA_SERVICE_PUBLICURL: https://notes.public.url VIKUNJA_DATABASE_HOST: db VIKUNJA_DATABASE_PASSWORD: ${VIKUNJA_DATABASE_PASSWORD} VIKUNJA_DATABASE_TYPE: postgres VIKUNJA_DATABASE_USER: ${VIKUNJA_DATABASE_USER} VIKUNJA_DATABASE_DATABASE: ${VIKUNJA_DATABASE_DATABASE} VIKUNJA_SERVICE_JWTSECRET: ${VIKUNJA_SERVICE_JWTSECRET} ports: - "1180:3456" volumes: - /opt/vikunja/files:/app/vikunja/files - /opt/vikunja/config.yml:/etc/vikunja/config.yml depends_on: db: condition: service_healthy restart: unless-stopped db: image: postgres:17 environment: POSTGRES_PASSWORD: ${VIKUNJA_DATABASE_PASSWORD} POSTGRES_USER: ${VIKUNJA_DATABASE_USER} volumes: - /opt/vikunja/db:/var/lib/postgresql/data restart: unless-stopped healthcheck: test: ["CMD-SHELL", "pg_isready -h localhost -U $$POSTGRES_USER"] interval: 2s ``` and the config.yaml: ``` auth: local: enabled: false openid: enabled: true redirecturl: "https://notes.puclic.url/auth/openid/" providers: - name: "authentik Login" authurl: "https://auth.public.url/application/o/vikunja/" logouturl: "https://auth.public.url/application/o/vikunja/end-session/" clientid: "clientid" clientsecret: "secret" ```
GiteaMirror commented 2025-11-01 21:00:15 -05:00
Author
Owner
Copy Link

@akorb90 commented on GitHub (Sep 11, 2025):

I just recreate my config.yaml atfer I found this line in the logs:

msg="It looks like your openid configuration is in the wrong format. Please check the docs for the correct format."

Did you change the format of the yaml?

old:

auth:
  local:
    enabled: false
 openid:
    enabled: true
    providers:
      - name: "authentik Login"

new and working:

auth:
  local:
    enabled: false
  openid:
    enabled: true
    providers:
      authentik:
        name: "authentik"
@akorb90 commented on GitHub (Sep 11, 2025): I just recreate my config.yaml atfer I found this line in the logs: > msg="It looks like your openid configuration is in the wrong format. Please check the docs for the correct format." Did you change the format of the yaml? old: ``` auth: local: enabled: false openid: enabled: true providers: - name: "authentik Login" ``` new and working: ``` auth: local: enabled: false openid: enabled: true providers: authentik: name: "authentik" ```
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/caldav
area/filters
area/frontend
area/gantt
area/internal-code
area/typesense
bug
changes requested
confirmed
dependencies
enhancement
good first issue
help wanted
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#606
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?