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

[GH-ISSUE #2608] Panic with keyvalue type redis and redis not enabled #6712

New Issue
Closed
opened 2026-04-20 17:17:38 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-20 17:17:38 -05:00
Owner
Copy Link

Originally created by @alifelan on GitHub (Apr 12, 2026).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2608

Pre-submission checklist

  • I have searched for existing open or closed issue reports with the same problem.

Description

During initial setup, i set the keyvalue type to redis, but missed adding enabled to redis, even though the configuration was there. That ended up with this panic

time=2026-04-12T07:18:46.845Z level=INFO msg="Using config file: /etc/vikunja/config.yml"
time=2026-04-12T07:18:46.845Z level=INFO msg="Running migrations…"
time=2026-04-12T07:18:46.909Z level=INFO msg="Ran all migrations successfully."
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x103e232]

goroutine 1 [running]:
code.vikunja.io/api/pkg/modules/keyvalue/redis.(*Storage).GetWithValue(0x1?, {0x251fbc4, 0x10}, {0x20e84c0, 0xc0007ebb48})
	/go/src/code.vikunja.io/api/pkg/modules/keyvalue/redis/redis.go:82 +0x32
code.vikunja.io/api/pkg/modules/keyvalue.GetWithValue(...)
	/go/src/code.vikunja.io/api/pkg/modules/keyvalue/keyvalue.go:62
code.vikunja.io/api/pkg/modules/auth/openid.GetAllProviders()
	/go/src/code.vikunja.io/api/pkg/modules/auth/openid/providers.go:77 +0xa5
code.vikunja.io/api/pkg/initialize.FullInitWithoutAsync()
	/go/src/code.vikunja.io/api/pkg/initialize/init.go:103 +0x79
code.vikunja.io/api/pkg/initialize.FullInit()
	/go/src/code.vikunja.io/api/pkg/initialize/init.go:121 +0x17
code.vikunja.io/api/pkg/cmd.init.func36(0xc00035d900?, {0x24e34dd?, 0x4?, 0x24e347d?})
	/go/src/code.vikunja.io/api/pkg/cmd/web.go:140 +0xf
github.com/spf13/cobra.(*Command).execute(0x42df340, {0xc000040090, 0x0, 0x0})
	/go/pkg/mod/github.com/spf13/cobra@v1.10.2/command.go:1004 +0xa5a
github.com/spf13/cobra.(*Command).ExecuteC(0x42df340)
	/go/pkg/mod/github.com/spf13/cobra@v1.10.2/command.go:1148 +0x465
github.com/spf13/cobra.(*Command).Execute(...)
	/go/pkg/mod/github.com/spf13/cobra@v1.10.2/command.go:1071
code.vikunja.io/api/pkg/cmd.Execute()
	/go/src/code.vikunja.io/api/pkg/cmd/cmd.go:44 +0x1a
main.main()
	/go/src/code.vikunja.io/api/main.go:22 +0xf

Setting .redis.enabled: true addressed the issue. While not a big problem, this makes it a bit more complicated for users to know what part was wrong

Vikunja Version

2.3.0

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @alifelan on GitHub (Apr 12, 2026). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2608 ### Pre-submission checklist - [x] I have searched for existing open or closed issue reports with the same problem. ### Description During initial setup, i set the keyvalue type to redis, but missed adding enabled to redis, even though the configuration was there. That ended up with this panic ``` time=2026-04-12T07:18:46.845Z level=INFO msg="Using config file: /etc/vikunja/config.yml" time=2026-04-12T07:18:46.845Z level=INFO msg="Running migrations…" time=2026-04-12T07:18:46.909Z level=INFO msg="Ran all migrations successfully." panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x103e232] goroutine 1 [running]: code.vikunja.io/api/pkg/modules/keyvalue/redis.(*Storage).GetWithValue(0x1?, {0x251fbc4, 0x10}, {0x20e84c0, 0xc0007ebb48}) /go/src/code.vikunja.io/api/pkg/modules/keyvalue/redis/redis.go:82 +0x32 code.vikunja.io/api/pkg/modules/keyvalue.GetWithValue(...) /go/src/code.vikunja.io/api/pkg/modules/keyvalue/keyvalue.go:62 code.vikunja.io/api/pkg/modules/auth/openid.GetAllProviders() /go/src/code.vikunja.io/api/pkg/modules/auth/openid/providers.go:77 +0xa5 code.vikunja.io/api/pkg/initialize.FullInitWithoutAsync() /go/src/code.vikunja.io/api/pkg/initialize/init.go:103 +0x79 code.vikunja.io/api/pkg/initialize.FullInit() /go/src/code.vikunja.io/api/pkg/initialize/init.go:121 +0x17 code.vikunja.io/api/pkg/cmd.init.func36(0xc00035d900?, {0x24e34dd?, 0x4?, 0x24e347d?}) /go/src/code.vikunja.io/api/pkg/cmd/web.go:140 +0xf github.com/spf13/cobra.(*Command).execute(0x42df340, {0xc000040090, 0x0, 0x0}) /go/pkg/mod/github.com/spf13/cobra@v1.10.2/command.go:1004 +0xa5a github.com/spf13/cobra.(*Command).ExecuteC(0x42df340) /go/pkg/mod/github.com/spf13/cobra@v1.10.2/command.go:1148 +0x465 github.com/spf13/cobra.(*Command).Execute(...) /go/pkg/mod/github.com/spf13/cobra@v1.10.2/command.go:1071 code.vikunja.io/api/pkg/cmd.Execute() /go/src/code.vikunja.io/api/pkg/cmd/cmd.go:44 +0x1a main.main() /go/src/code.vikunja.io/api/main.go:22 +0xf ``` Setting `.redis.enabled: true` addressed the issue. While not a big problem, this makes it a bit more complicated for users to know what part was wrong ### Vikunja Version 2.3.0 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror added the concern/uxarea/config labels 2026-04-20 17:17:38 -05:00
GiteaMirror commented 2026-04-20 17:17:40 -05:00
Author
Owner
Copy Link

@vikunja-bot-app[bot] commented on GitHub (Apr 12, 2026):

This issue has been fixed in #2609, please check with the next unstable build (should be ready for deployment in ~30min, also on the demo).

<!-- gh-comment-id:4231245809 --> @vikunja-bot-app[bot] commented on GitHub (Apr 12, 2026): This issue has been fixed in #2609, please check with the next unstable build (should be ready for deployment in ~30min, also on [the demo](https://try.vikunja.io)).
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 area/config concern/ux
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#6712
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?