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

[GH-ISSUE #1307] Latest Release Two Factor - Unauthorized #6348

New Issue
Closed
opened 2026-04-20 16:56:24 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-20 16:56:24 -05:00
Owner
Copy Link

Originally created by @Novanglus96 on GitHub (Aug 18, 2025).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/1307

Description

There was a new release pushed to the docker hub in the last 24 hours. After updating to that version, I get Unauthorized errors for any changes I attempt to make, i.e. closing Tasks, Creating Tasks, etc. It appears to be an issue with Two Factor Authorization as I had that turned on prior to the update and when viewing two factor in Settings, it has en enroll option as if it is not setup.

I can confirm that rolling back to verison 0.24.6 allows me to login and authenticate with two factor, but then I get db errors since apparently there were db scheme changes with the lastest version.

Vikunja Version

Latest

Browser and version

Chrome

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

No response

Originally created by @Novanglus96 on GitHub (Aug 18, 2025). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/1307 ### Description There was a new release pushed to the docker hub in the last 24 hours. After updating to that version, I get Unauthorized errors for any changes I attempt to make, i.e. closing Tasks, Creating Tasks, etc. It appears to be an issue with Two Factor Authorization as I had that turned on prior to the update and when viewing two factor in Settings, it has en enroll option as if it is not setup. I can confirm that rolling back to verison 0.24.6 allows me to login and authenticate with two factor, but then I get db errors since apparently there were db scheme changes with the lastest version. ### Vikunja Version Latest ### Browser and version Chrome ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots _No response_
GiteaMirror commented 2026-04-20 16:56:26 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Aug 18, 2025):

Likely not a problem with the two factor auth. Please confirm that your problem is not one of these:

<!-- gh-comment-id:3197312095 --> @kolaente commented on GitHub (Aug 18, 2025): Likely not a problem with the two factor auth. Please confirm that your problem is not one of these: - https://github.com/go-vikunja/vikunja/issues/1303 - https://github.com/go-vikunja/vikunja/issues/1306
GiteaMirror commented 2026-04-20 16:56:26 -05:00
Author
Owner
Copy Link

@Novanglus96 commented on GitHub (Aug 18, 2025):

It is similar to 1306 but I also haven't changed any settings. I do not use authentik so 1303 doesn't apply to me. I also haven't changed any config settings, and I did not intend to update to a rc release. I was using the latest tag so not sure how I would end up with a rc build. Is there a way to roll back to 0.24.6 safely?

<!-- gh-comment-id:3197445790 --> @Novanglus96 commented on GitHub (Aug 18, 2025): It is similar to 1306 but I also haven't changed any settings. I do not use authentik so 1303 doesn't apply to me. I also haven't changed any config settings, and I did not intend to update to a rc release. I was using the latest tag so not sure how I would end up with a rc build. Is there a way to roll back to 0.24.6 safely?
GiteaMirror commented 2026-04-20 16:56:27 -05:00
Author
Owner
Copy Link

@Novanglus96 commented on GitHub (Aug 18, 2025):

An interesting note as well, that if I am already logged in, I can view and navigate without issue. It's just updates that trigger the Unauthorized error.

<!-- gh-comment-id:3197450059 --> @Novanglus96 commented on GitHub (Aug 18, 2025): An interesting note as well, that if I am already logged in, I can view and navigate without issue. It's just updates that trigger the Unauthorized error.
GiteaMirror commented 2026-04-20 16:56:27 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Aug 18, 2025):

Did you set a publicurl?

You can pin your docker configuration to 0.24.6. Rolling back is not really supported though, you'll need to restore a backup and switch to the old version.

<!-- gh-comment-id:3197455622 --> @kolaente commented on GitHub (Aug 18, 2025): Did you set a publicurl? You can pin your docker configuration to `0.24.6`. Rolling back is not really supported though, you'll need to restore a backup and switch to the old version.
GiteaMirror commented 2026-04-20 16:56:28 -05:00
Author
Owner
Copy Link

@Novanglus96 commented on GitHub (Aug 18, 2025):

I did not have a publicurl set, just a frontend url. Adding VIKUNJA_SERVICE_PUBLICURL to my config worked!

Thanks!

<!-- gh-comment-id:3197485655 --> @Novanglus96 commented on GitHub (Aug 18, 2025): I did not have a publicurl set, just a frontend url. Adding VIKUNJA_SERVICE_PUBLICURL to my config worked! Thanks!
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#6348
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?