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

Install with Debian immediately errors on run. #2459

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

Originally created by @rjulian on GitHub (Jan 3, 2026).

Description

Hey all,

Just wanted to report what I imagine is more a UX bug than it is an actual bug. Following the docs recommendation to install vikunja from .deb, this was the experience:

$ sudo dpkg -i vikunja-v1.0.0-rc3-x86_64.deb                                                                                                                                                        
Selecting previously unselected package vikunja.
Preparing to unpack vikunja-v1.0.0-rc3-x86_64.deb ...
Unpacking vikunja (1.0.0~rc3) ...
Setting up vikunja (1.0.0~rc3) ...
                                                                                                                                                                                                                   
 $ vikunja                          
time=2026-01-03T11:42:15.566+01:00 level=INFO msg="Using config file: /etc/vikunja/config.yml"
time=2026-01-03T11:42:15.567+01:00 level=ERROR msg="service.publicurl is required when cors.enable is true"

After editing the config file and setting cors: false it clearly works. As a short term solution, I think just adding notes in the docs to update that config would suffice. In the long term, I expect you could solve the problem in a cleaner method.

Vikunja Version

v1.0.0-rc3

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @rjulian on GitHub (Jan 3, 2026). ### Description Hey all, Just wanted to report what I imagine is more a UX bug than it is an actual bug. Following the docs recommendation to install vikunja from .deb, this was the experience: ``` $ sudo dpkg -i vikunja-v1.0.0-rc3-x86_64.deb Selecting previously unselected package vikunja. Preparing to unpack vikunja-v1.0.0-rc3-x86_64.deb ... Unpacking vikunja (1.0.0~rc3) ... Setting up vikunja (1.0.0~rc3) ... $ vikunja time=2026-01-03T11:42:15.566+01:00 level=INFO msg="Using config file: /etc/vikunja/config.yml" time=2026-01-03T11:42:15.567+01:00 level=ERROR msg="service.publicurl is required when cors.enable is true" ``` After editing the config file and setting `cors: false` it clearly works. As a short term solution, I think just adding notes in the docs to update that config would suffice. In the long term, I expect you could solve the problem in a cleaner method. ### Vikunja Version v1.0.0-rc3 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2026-03-22 14:08:19 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jan 5, 2026):

Updated the docs in 3e5d108fd0

@kolaente commented on GitHub (Jan 5, 2026): Updated the docs in https://github.com/go-vikunja/website/commit/3e5d108fd069ff271d7b41f34c6a9735a4bd98a5
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#2459
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?