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 #1336] Upgrade to RC1/unstable can no longer log in #6359

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

Originally created by @simojenki on GitHub (Aug 23, 2025).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/1336

Description

I'm running a pretty vanilla docker setup, Only env vars I set on docker container are;
VIKUNJA_SERVICE_TIMEZONE
VIKUNJA_SERVICE_ENABLEEMAILREMINDERS
VIKUNJA_SERVICE_PUBLICURL

Everything ran fine for 12+ months.

System upgraded to RC, can no longer log in,

  • I've tried reset the pw via docker cli, no good
  • I've checked the TZ of both server and container, seem to be ok
  • I already had VIKUNJA_SERVICE_PUBLICURL set, so no change required there.

I just get 'Unauthorized' everytime.

I tried chaning the VIKUNJA_LOG_LEVEL to DEBUG, but that didnt yield much of interest.

Vikunja Version

v1.0.0-rc1 or unstasble

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

Please select

Screenshots

No response

Originally created by @simojenki on GitHub (Aug 23, 2025). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/1336 ### Description I'm running a pretty vanilla docker setup, Only env vars I set on docker container are; VIKUNJA_SERVICE_TIMEZONE VIKUNJA_SERVICE_ENABLEEMAILREMINDERS VIKUNJA_SERVICE_PUBLICURL Everything ran fine for 12+ months. System upgraded to RC, can no longer log in, - I've tried reset the pw via docker cli, no good - I've checked the TZ of both server and container, seem to be ok - I already had VIKUNJA_SERVICE_PUBLICURL set, so no change required there. I just get 'Unauthorized' everytime. I tried chaning the VIKUNJA_LOG_LEVEL to DEBUG, but that didnt yield much of interest. ### Vikunja Version v1.0.0-rc1 or unstasble ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? Please select ### Screenshots _No response_
GiteaMirror commented 2026-04-20 16:57:05 -05:00
Author
Owner
Copy Link

@simojenki commented on GitHub (Aug 23, 2025):

Just to confirm I see the log for request from the UI into the server, I get a 401. So it looks like something in the server has decided that I am not authenticated. Odd given that both my original pw, nor my reset pw work.

<!-- gh-comment-id:3217003669 --> @simojenki commented on GitHub (Aug 23, 2025): Just to confirm I see the log for request from the UI into the server, I get a 401. So it looks like something in the server has decided that I am not authenticated. Odd given that both my original pw, nor my reset pw work.
GiteaMirror commented 2026-04-20 16:57:06 -05:00
Author
Owner
Copy Link

@Klaus-Kleber commented on GitHub (Aug 24, 2025):

I have the same issue. With my still logged in clients, I also can't edit anything and get the message "Unauthorized".
I am using 2FA, maybe that is causing the error.

<!-- gh-comment-id:3217969664 --> @Klaus-Kleber commented on GitHub (Aug 24, 2025): I have the same issue. With my still logged in clients, I also can't edit anything and get the message "Unauthorized". I am using 2FA, maybe that is causing the error.
GiteaMirror commented 2026-04-20 16:57:06 -05:00
Author
Owner
Copy Link

@davidancalagon commented on GitHub (Aug 24, 2025):

Same issue here. Have two user accounts, neither can log in, even says Unauthorized when attempting email password recovery.

<!-- gh-comment-id:3218273090 --> @davidancalagon commented on GitHub (Aug 24, 2025): Same issue here. Have two user accounts, neither can log in, even says Unauthorized when attempting email password recovery.
GiteaMirror commented 2026-04-20 16:57:07 -05:00
Author
Owner
Copy Link

@Xanawatt commented on GitHub (Aug 24, 2025):

Yeah, this is completely broken, was just trying out the project and both rc0 and rc1 do not allow for initial registration even. The latest version that works is v0.24.6

<!-- gh-comment-id:3218376157 --> @Xanawatt commented on GitHub (Aug 24, 2025): Yeah, this is completely broken, was just trying out the project and both rc0 and rc1 do not allow for initial registration even. The latest version that works is v0.24.6
GiteaMirror commented 2026-04-20 16:57:07 -05:00
Author
Owner
Copy Link

@simojenki commented on GitHub (Aug 27, 2025):

I can log in again;

  • I rolled back "unstable" to "1.0.0-rc1"
  • I set VIKUNJA_CORS_ENABLE: "false" on my docker container.

My complete set of env vars are now;

env:
      TZ: "{{ tz }}"
      VIKUNJA_SERVICE_JWTSECRET: "something-secret"
      VIKUNJA_SERVICE_TIMEZONE: "{{ tz }}"
      VIKUNJA_SERVICE_ENABLEEMAILREMINDERS: "false"
      VIKUNJA_SERVICE_PUBLICURL: "https://{{ public_domain }}:443"
      VIKUNJA_CORS_ENABLE: "false"
<!-- gh-comment-id:3226249517 --> @simojenki commented on GitHub (Aug 27, 2025): I can log in again; - I rolled back "unstable" to "1.0.0-rc1" - I set VIKUNJA_CORS_ENABLE: "false" on my docker container. My complete set of env vars are now; ``` env: TZ: "{{ tz }}" VIKUNJA_SERVICE_JWTSECRET: "something-secret" VIKUNJA_SERVICE_TIMEZONE: "{{ tz }}" VIKUNJA_SERVICE_ENABLEEMAILREMINDERS: "false" VIKUNJA_SERVICE_PUBLICURL: "https://{{ public_domain }}:443" VIKUNJA_CORS_ENABLE: "false" ```
GiteaMirror commented 2026-04-20 16:57:07 -05:00
Author
Owner
Copy Link

@fernandeusto commented on GitHub (Aug 27, 2025):

add VIKUNJA_CORS_ENABLE: "false" and it run OK with latest image

<!-- gh-comment-id:3226287118 --> @fernandeusto commented on GitHub (Aug 27, 2025): add VIKUNJA_CORS_ENABLE: "false" and it run OK with latest image
GiteaMirror commented 2026-04-20 16:57:08 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Aug 29, 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

<!-- gh-comment-id:3237354816 --> @kolaente commented on GitHub (Aug 29, 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 2026-04-20 16:57:08 -05:00
Author
Owner
Copy Link

@simojenki commented on GitHub (Aug 29, 2025):

Interestingly I tried this again, previously I had put both protocol and port into the public url;
ie. https://vikunja.example.com:443
However that does not work, if I put just 'https://vikunja.example.com' into the public url it does work (with cors enabled/default)

<!-- gh-comment-id:3238382242 --> @simojenki commented on GitHub (Aug 29, 2025): Interestingly I tried this again, previously I had put both protocol and port into the public url; ie. https://vikunja.example.com:443 However that does not work, if I put just 'https://vikunja.example.com' into the public url it does work (with cors enabled/default)
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#6359
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?