github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-21 18:53:07 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

Can't log in with 1.0.0-rc1 #2284

New Issue
Closed
opened 2026-03-22 14:00:48 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-03-22 14:00:48 -05:00
Owner
Copy Link

Originally created by @eugeneyng on GitHub (Aug 21, 2025).

Description

My docker auto-updated vikunja/vikunja:latest and after it updated to 1.0.0-rc1, I could no longer login. The front end says "Unauthorized"

Here is my docker-compose:

services:
  vikunja:
    container_name: vikunja
    environment:
      VIKUNJA_CORS_ENABLE: true
      VIKUNJA_DATABASE_PATH: /db/vikunja.db
      VIKUNJA_DATABASE_TYPE: sqlite
      VIKUNJA_SERVICE_ENABLEREGISTRATION: false
      VIKUNJA_SERVICE_JWTSECRET: secret
      VIKUNJA_SERVICE_PUBLICURL: http://vikunja.my.website
    image: vikunja/vikunja
    ports:
      - 3456:3456
    restart: unless-stopped
    volumes:
      - ./data/files:/app/vikunja/files
      - ./data/db:/db

Here is the log from docker:

user@server:~/docker/vikunja$ sudo docker logs vikunja
time=2025-08-21T01:37:24.299Z level=INFO msg="No config file found, using default or config from environment variables."
time=2025-08-21T01:37:24.300Z level=INFO msg="Running migrations…"
time=2025-08-21T01:37:24.311Z level=INFO msg="Ran all migrations successfully."
time=2025-08-21T01:37:24.313Z level=INFO msg="Mailer is disabled, not sending reminders per mail"
time=2025-08-21T01:37:24.314Z level=INFO msg="Mailer is disabled, not sending overdue per mail"
time=2025-08-21T01:37:24.314Z level=INFO msg="Vikunja version v1.0.0-rc1"
time=2025-08-21T01:37:24.314Z level=DEBUG msg="CORS enabled with origins: http://127.0.0.1:*, http://localhost:*, http://vikunja.my.website"
⇨ http server started on [::]:3456
time=2025-08-21T01:37:41.870Z level=INFO msg="POST /api/v1/login" component=http status=401 remote_ip=[my-ip] latency=71.029µs user_agent="Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:141.0) Gecko/20100101 Firefox/141.0"

When I went back to 0.24.6, login worked again.

Vikunja Version

1.0.0-rc1

Browser and version

FireFox

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @eugeneyng on GitHub (Aug 21, 2025). ### Description My docker auto-updated vikunja/vikunja:latest and after it updated to 1.0.0-rc1, I could no longer login. The front end says "Unauthorized" Here is my docker-compose: ``` services: vikunja: container_name: vikunja environment: VIKUNJA_CORS_ENABLE: true VIKUNJA_DATABASE_PATH: /db/vikunja.db VIKUNJA_DATABASE_TYPE: sqlite VIKUNJA_SERVICE_ENABLEREGISTRATION: false VIKUNJA_SERVICE_JWTSECRET: secret VIKUNJA_SERVICE_PUBLICURL: http://vikunja.my.website image: vikunja/vikunja ports: - 3456:3456 restart: unless-stopped volumes: - ./data/files:/app/vikunja/files - ./data/db:/db ``` Here is the log from docker: ``` user@server:~/docker/vikunja$ sudo docker logs vikunja time=2025-08-21T01:37:24.299Z level=INFO msg="No config file found, using default or config from environment variables." time=2025-08-21T01:37:24.300Z level=INFO msg="Running migrations…" time=2025-08-21T01:37:24.311Z level=INFO msg="Ran all migrations successfully." time=2025-08-21T01:37:24.313Z level=INFO msg="Mailer is disabled, not sending reminders per mail" time=2025-08-21T01:37:24.314Z level=INFO msg="Mailer is disabled, not sending overdue per mail" time=2025-08-21T01:37:24.314Z level=INFO msg="Vikunja version v1.0.0-rc1" time=2025-08-21T01:37:24.314Z level=DEBUG msg="CORS enabled with origins: http://127.0.0.1:*, http://localhost:*, http://vikunja.my.website" ⇨ http server started on [::]:3456 time=2025-08-21T01:37:41.870Z level=INFO msg="POST /api/v1/login" component=http status=401 remote_ip=[my-ip] latency=71.029µs user_agent="Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:141.0) Gecko/20100101 Firefox/141.0" ``` When I went back to 0.24.6, login worked again. ### Vikunja Version 1.0.0-rc1 ### Browser and version FireFox ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2026-03-22 14:00:51 -05:00
Author
Owner
Copy Link

@eugeneyng commented on GitHub (Aug 21, 2025):

I see this is a duplicate of #1306

@eugeneyng commented on GitHub (Aug 21, 2025): I see this is a duplicate of #1306
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
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#2284
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?