github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-03-09 07:13:35 -05:00
Code Issues 219 Packages Projects Releases 2 Wiki Activity

migrate error with database connect string #104

New Issue
Closed
opened 2025-11-01 20:47:07 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-01 20:47:07 -05:00
Owner
Copy Link

Originally created by @Freundschaft on GitHub (Nov 9, 2022).

Description

after upgrading from 0.19 to 0.20 vikunja-api doesnt start anymore with the following error:

2022-11-09T14:12:46.21822349Z: CRITICAL ▶ migration/initMigration 001 Could not connect to db: parse "postgres://vikunja:password@1.1.1.1:5432/vikunja?sslmode=disable&sslcert=&sslkey=&sslrootcert=": invalid port ":password" after host

It seems that something with the parsing mechanism during migration doesnt work properly.

Vikunja Frontend Version

0.20

Vikunja API Version

0.20

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @Freundschaft on GitHub (Nov 9, 2022). ### Description after upgrading from 0.19 to 0.20 vikunja-api doesnt start anymore with the following error: 2022-11-09T14:12:46.21822349Z: CRITICAL ▶ migration/initMigration 001 Could not connect to db: parse "postgres://vikunja:password@1.1.1.1:5432/vikunja?sslmode=disable&sslcert=&sslkey=&sslrootcert=": invalid port ":password" after host It seems that something with the parsing mechanism during migration doesnt work properly. ### Vikunja Frontend Version 0.20 ### Vikunja API Version 0.20 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror added the bug label 2025-11-01 20:47:07 -05:00
GiteaMirror commented 2025-11-01 20:47:08 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Nov 9, 2022):

How are you hosting Vikunja? Do you have special characters in the host name, username or password?

@kolaente commented on GitHub (Nov 9, 2022): How are you hosting Vikunja? Do you have special characters in the host name, username or password?
GiteaMirror commented 2025-11-01 20:47:09 -05:00
Author
Owner
Copy Link

@Freundschaft commented on GitHub (Nov 10, 2022):

yes, Im using this helm chart, https://artifacthub.io/packages/helm/k8s-at-home/vikunja/2.3.0
and Im using special characters in the password,
host name is an ip address, username is without special characters.

the chart creates a config.yml in /etc/vikunja that looks like this:

/etc/vikunja # cat config.yml
service:
frontendurl: "https://vikunja.civilfleet.org/"
database:
type: "postgres"
user: "vikunja"
password: xxxxxxxxxx
host: "1.1.1.1"
database: "vikunja"
/etc/vikunja #

@Freundschaft commented on GitHub (Nov 10, 2022): yes, Im using this helm chart, https://artifacthub.io/packages/helm/k8s-at-home/vikunja/2.3.0 and Im using special characters in the password, host name is an ip address, username is without special characters. the chart creates a config.yml in /etc/vikunja that looks like this: /etc/vikunja # cat config.yml service: frontendurl: "https://vikunja.civilfleet.org/" database: type: "postgres" user: "vikunja" password: xxxxxxxxxx host: "1.1.1.1" database: "vikunja" /etc/vikunja #
GiteaMirror commented 2025-11-01 20:47:09 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Nov 10, 2022):

Does it work with the unstable version of the api?

@kolaente commented on GitHub (Nov 10, 2022): Does it work with the unstable version of the api?
GiteaMirror commented 2025-11-01 20:47:09 -05:00
Author
Owner
Copy Link

@Freundschaft commented on GitHub (Nov 10, 2022):

i just tried:

so its

0.19: works
0.20 doesnt work
unstable: works

@Freundschaft commented on GitHub (Nov 10, 2022): i just tried: so its 0.19: works 0.20 doesnt work unstable: works
GiteaMirror commented 2025-11-01 20:47:09 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Nov 10, 2022):

Then it's already fixed and will be included with the next release.

@kolaente commented on GitHub (Nov 10, 2022): Then it's already fixed and will be included with the next release.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/caldav
area/filters
area/frontend
area/gantt
area/internal-code
area/typesense
bug
changes requested
confirmed
dependencies
enhancement
good first issue
help wanted
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label bug
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#104
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?