github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-30 13:46:39 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

Can no longer log in #1912

New Issue
Closed
opened 2026-03-22 13:45:54 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-03-22 13:45:54 -05:00
Owner
Copy Link

Originally created by @ozuzo on GitHub (Feb 1, 2024).

Description

Updated our 0.22 version to 0.22.1, to check out the fix for the subprojects not always being correctly displayed in the menu on the left. After updating I no longer seem to be able to login using (previously working) credentials stored in the browser. On the network tab, I see

{"code":1011,"message":"Wrong username or password."}
as response.

Side note: running Vikunja on a shared host which does not expose user-defined ports to the internet, so I've added a proxy rule to the .htaccess file of the frontend:

RewriteEngine On
RewriteRule .* - [e=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

RewriteRule ^\/?(index\.html|favicon\.ico|assets|audio|fonts|images|manifest\.webmanifest|robots\.txt|sw\.js|workbox-.*|dav|\.well-known) - [L]
RewriteRule ^api/(.*[^/])/?$ http://localhost:3456/api/$1 [P,L]
RewriteRule ^(.*)$ index.html [QSA,L]

-- this worked fine until this morning.

One other note (don't ask ;-) -- passwords are not set via Vikunja itself, but are synced with another tool we're using (Bookstack), so users only have one set of logins to worry about. This also has also worked before (the password hashes are all of the 2$... form)

So two questions: any changes to the login flow, or the way passwords are checked, before I need to start debugging what I might've broken during the update?

Vikunja Frontend Version

0.22.1

Vikunja API Version

0.22.1

Browser and version

Both up-to-date Edge and Firefox

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @ozuzo on GitHub (Feb 1, 2024). ### Description Updated our 0.22 version to 0.22.1, to check out the fix for the subprojects not always being correctly displayed in the menu on the left. After updating I no longer seem to be able to login using (previously working) credentials stored in the browser. On the network tab, I see ``{"code":1011,"message":"Wrong username or password."} `` as response. Side note: running Vikunja on a shared host which does not expose user-defined ports to the internet, so I've added a proxy rule to the .htaccess file of the frontend: ``` RewriteEngine On RewriteRule .* - [e=HTTP_AUTHORIZATION:%{HTTP:Authorization}] RewriteRule ^\/?(index\.html|favicon\.ico|assets|audio|fonts|images|manifest\.webmanifest|robots\.txt|sw\.js|workbox-.*|dav|\.well-known) - [L] RewriteRule ^api/(.*[^/])/?$ http://localhost:3456/api/$1 [P,L] RewriteRule ^(.*)$ index.html [QSA,L] ``` -- this worked fine until this morning. One other note (don't ask ;-) -- passwords are not set via Vikunja itself, but are synced with another tool we're using (Bookstack), so users only have one set of logins to worry about. This also has also worked before (the password hashes are all of the 2$... form) So two questions: any changes to the login flow, or the way passwords are checked, before I need to start debugging what I might've broken during the update? ### Vikunja Frontend Version 0.22.1 ### Vikunja API Version 0.22.1 ### Browser and version Both up-to-date Edge and Firefox ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2026-03-22 13:45:56 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Feb 1, 2024):

passwords are not set via Vikunja itself, but are synced with another tool we're using (Bookstack), so users only have one set of logins to worry about. This also has also worked before (the password hashes are all of the 2$... form)

You really should use openid for that.

To debug this, you could enable database logging to see if the queries work and if the password hash is the problem here.

any changes to the login flow, or the way passwords are checked, before I need to start debugging what I might've broken during the update?

There have not been any explicit changes to that. However, we don't implement the password hashing ourselves but use the Go standard library for that, which may have been updated in a way that it no longer works with the Hashes from Bookstack.

Unfortunately, it does not look like this is a problem Vikunja should solve, because what you're doing is not really intended and there are better alternatives available.

@kolaente commented on GitHub (Feb 1, 2024): > passwords are not set via Vikunja itself, but are synced with another tool we're using (Bookstack), so users only have one set of logins to worry about. This also has also worked before (the password hashes are all of the 2$... form) You really should use openid for that. To debug this, you could enable [database logging](https://vikunja.io/docs/config-options/#database-2) to see if the queries work and if the password hash is the problem here. > any changes to the login flow, or the way passwords are checked, before I need to start debugging what I might've broken during the update? There have not been any explicit changes to that. However, we don't implement the password hashing ourselves but use the Go standard library for that, which may have been updated in a way that it no longer works with the Hashes from Bookstack. Unfortunately, it does not look like this is a problem Vikunja should solve, because what you're doing is not really intended and there are better alternatives available.
GiteaMirror commented 2026-03-22 13:45:56 -05:00
Author
Owner
Copy Link

@ozuzo commented on GitHub (Feb 1, 2024):

Fully understand. Given the limitations on the shared host this was the easiest solution, it is only for a very small group of users.

Where there any database migration steps for .22 -> .22.1? So I know if I should restore a backup if I want to rollback to .22

@ozuzo commented on GitHub (Feb 1, 2024): Fully understand. Given the limitations on the shared host this was the easiest solution, it is only for a very small group of users. Where there any database migration steps for .22 -> .22.1? So I know if I should restore a backup if I want to rollback to .22
GiteaMirror commented 2026-03-22 13:45:57 -05:00
Author
Owner
Copy Link

@ozuzo commented on GitHub (Feb 2, 2024):

Please ignore my stupidity :-) During the upgrade I managed to remove the config.yml file, so that Vikunja was now using a sqlite database instead of the MySQL one....

@ozuzo commented on GitHub (Feb 2, 2024): Please ignore my stupidity :-) During the upgrade I managed to remove the config.yml file, so that Vikunja was now using a sqlite database instead of the MySQL one....
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#1912
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?