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

vikunja cannot run with default config #2362

New Issue
Closed
opened 2026-03-22 14:04:25 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-03-22 14:04:25 -05:00
Owner
Copy Link

Originally created by @maggch97 on GitHub (Sep 22, 2025).

Description

./vikunja
time=2025-09-22T21:10:38.575+08:00 level=INFO msg="No config file found, using default or config from environment variables."
time=2025-09-22T21:10:38.576+08:00 level=ERROR msg="service.publicurl is required when cors.enable is true"

related to https://github.com/go-vikunja/vikunja/pull/1351

Vikunja Version

latest

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

Please select

Screenshots

No response

Originally created by @maggch97 on GitHub (Sep 22, 2025). ### Description ``` ./vikunja time=2025-09-22T21:10:38.575+08:00 level=INFO msg="No config file found, using default or config from environment variables." time=2025-09-22T21:10:38.576+08:00 level=ERROR msg="service.publicurl is required when cors.enable is true" ``` related to https://github.com/go-vikunja/vikunja/pull/1351 ### Vikunja Version latest ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? Please select ### Screenshots _No response_
GiteaMirror commented 2026-03-22 14:04:26 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Sep 22, 2025):

It won't work if you don't provide a publicurl. You need to add one.

@kolaente commented on GitHub (Sep 22, 2025): It won't work if you don't provide a publicurl. You need to add one.
GiteaMirror commented 2026-03-22 14:04:26 -05:00
Author
Owner
Copy Link

@ElBi21 commented on GitHub (Nov 28, 2025):

With Vikunja 0.23.0 this behaviour doesn't occur, and the default configuration doesn't ask for a public URL. If one just needs to quickly set up Vikunja and doesn't need the latest version, that can be an option (clearly, it's suggested to use always the latest version for security reasons). Just make sure to pull the container vikunja/vikunja:0.23.0. Idk if this also doesn't happen in other v0.24.X versions, but I can confirm that it still happens with the latest version

@ElBi21 commented on GitHub (Nov 28, 2025): With Vikunja `0.23.0` this behaviour doesn't occur, and the default configuration doesn't ask for a public URL. If one just needs to quickly set up Vikunja and doesn't need the latest version, that can be an option (clearly, it's suggested to use always the latest version for security reasons). Just make sure to pull the container `vikunja/vikunja:0.23.0`. Idk if this also doesn't happen in other v0.24.X versions, but I can confirm that it still happens with the `latest` version
GiteaMirror commented 2026-03-22 14:04:27 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Nov 28, 2025):

Please do not use 0.23.0. That version is unsupported and contains a few critical security issues that could allow other users to access your tasks.

@kolaente commented on GitHub (Nov 28, 2025): Please do not use 0.23.0. That version is unsupported and contains a few critical security issues that could allow other users to access your tasks.
GiteaMirror commented 2026-03-22 14:04:27 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Nov 28, 2025):

Please do not use 0.23.0. That version is unsupported and contains a few critical security issues that could allow other users to access your tasks.

@kolaente commented on GitHub (Nov 28, 2025): Please do not use 0.23.0. That version is unsupported and contains a few critical security issues that could allow other users to access your tasks.
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#2362
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?