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

[GH-ISSUE #916] All actions are failing with 401 error #6314

New Issue
Closed
opened 2026-04-20 16:53:52 -05:00 by GiteaMirror · 6 comments
GiteaMirror commented 2026-04-20 16:53:52 -05:00
Owner
Copy Link

Originally created by @fritzbauer on GitHub (Jun 11, 2025).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/916

Description

Since last nightly build it is not possible anymore to perform any action in the Vikunja app. Each time I try to change the position of a task, or mark it as done, or change the title, or do any other change a red box appears in the bottom left "Unauthorized". The network trace also shows 401 errors being thrown.

On https://try.vikunja.io/ it is not even possible to login with "demo". The page also shows an error "Unauthorized".

Vikunja Version

Version: v0.24.1-1361-f487f81f

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

No response

Originally created by @fritzbauer on GitHub (Jun 11, 2025). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/916 ### Description Since last nightly build it is not possible anymore to perform any action in the Vikunja app. Each time I try to change the position of a task, or mark it as done, or change the title, or do any other change a red box appears in the bottom left "Unauthorized". The network trace also shows 401 errors being thrown. On https://try.vikunja.io/ it is not even possible to login with "demo". The page also shows an error "Unauthorized". ### Vikunja Version Version: v0.24.1-1361-f487f81f ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots _No response_
GiteaMirror commented 2026-04-20 16:53:54 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jun 11, 2025):

Should be fixed now in 842e7f524b, please check with the next unstable build (should be ready for deployment in ~30min, also on try).

A workaround would be to add your Vikunja URL to the allowed cors origins.

<!-- gh-comment-id:2962503526 --> @kolaente commented on GitHub (Jun 11, 2025): Should be fixed now in https://github.com/go-vikunja/vikunja/commit/842e7f524b37218a4a24b05da094daf3bcb2dcb5, please check with the next unstable build (should be ready for deployment in ~30min, also on [try](https://try.vikunja.io)). A workaround would be to add your Vikunja URL to the allowed cors origins.
GiteaMirror commented 2026-04-20 16:53:54 -05:00
Author
Owner
Copy Link

@fritzbauer commented on GitHub (Jun 11, 2025):

Was not fixed after that update for me, but setting VIKUNJA_CORS_ORIGINS helped. Thank you!

<!-- gh-comment-id:2962899904 --> @fritzbauer commented on GitHub (Jun 11, 2025): Was not fixed after that update for me, but setting VIKUNJA_CORS_ORIGINS helped. Thank you!
GiteaMirror commented 2026-04-20 16:53:56 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jun 11, 2025):

@fritzbauer which version are you using?

If you enable debug logs, there should be a message about the configured cors origins. Is your publicurl in there?

<!-- gh-comment-id:2962921009 --> @kolaente commented on GitHub (Jun 11, 2025): @fritzbauer which version are you using? If you enable debug logs, there should be a message about the configured cors origins. Is your publicurl in there?
GiteaMirror commented 2026-04-20 16:53:57 -05:00
Author
Owner
Copy Link

@fritzbauer commented on GitHub (Jun 12, 2025):

Am on Version: v0.24.1-1369-15a1919d right now.
Yes, the message showed it was only configured for 127.0.0.1 and localhost origins. Indeed it seems I never configured ServicePublicURL... after setting it, it now successfully works without explicitly setting cors.origins.

<!-- gh-comment-id:2965607952 --> @fritzbauer commented on GitHub (Jun 12, 2025): Am on Version: v0.24.1-1369-15a1919d right now. Yes, the message showed it was only configured for 127.0.0.1 and localhost origins. Indeed it seems I never configured ServicePublicURL... after setting it, it now successfully works without explicitly setting cors.origins.
GiteaMirror commented 2026-04-20 16:53:57 -05:00
Author
Owner
Copy Link

@m-spitfire commented on GitHub (Jul 30, 2025):

I faced the same issue, since I did not set the publicurl option, but only frontendurl (since I deployed in NixOS with services.vikunja.) Should the default value of publicurl be the frontendurl?

<!-- gh-comment-id:3136380093 --> @m-spitfire commented on GitHub (Jul 30, 2025): I faced the same issue, since I did not set the `publicurl` option, but only `frontendurl` (since I deployed in NixOS with [`services.vikunja`](https://github.com/NixOS/nixpkgs/blob/nixos-25.05/nixos/modules/services/web-apps/vikunja.nix).) Should the default value of `publicurl` be the `frontendurl`?
GiteaMirror commented 2026-04-20 16:53:58 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jul 30, 2025):

@m-spitfire frontendurl has no effect since a while now, it was entirely replaced by publicurl. The version in NixOS has that change.

<!-- gh-comment-id:3136461388 --> @kolaente commented on GitHub (Jul 30, 2025): @m-spitfire `frontendurl` has no effect since a while now, it was entirely replaced by `publicurl`. The version in NixOS has that change.
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#6314
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?