Succesful login does not redirect/login #1952

Closed
opened 2026-03-22 13:48:15 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @GrauBlitz on GitHub (May 10, 2024).

Description

I run Vikunja in docker, now out of a sudden I cannot login into it.

The server log shows:

▶ 192.168.X.Y  POST 200 /api/v1/login 112.947274ms - Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:125.0) Gecko/20100101 Firefox/125.0

The client log also shows a successful login (POST answer with token key and token value) with the same request. But after that the cycle in the "Login" button disappears and nothing happens, no redirect, no error (also checked in JS console). The sessions seems also not to be set, because switching to anything other than /login redirects again to the /login page.

If I try some credentials it shows a normal failed login error.

Vikunja Version

v0.23.0

Browser and version

Firefox 125

Can you reproduce the bug on the Vikunja demo site?

Please select

Screenshots

No response

Originally created by @GrauBlitz on GitHub (May 10, 2024). ### Description I run Vikunja in docker, now out of a sudden I cannot login into it. The server log shows: ``` ▶ 192.168.X.Y POST 200 /api/v1/login 112.947274ms - Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:125.0) Gecko/20100101 Firefox/125.0 ``` The client log also shows a successful login (POST answer with token key and token value) with the same request. But after that the cycle in the "Login" button disappears and nothing happens, no redirect, no error (also checked in JS console). The sessions seems also not to be set, because switching to anything other than /login redirects again to the /login page. If I try some credentials it shows a normal failed login error. ### Vikunja Version v0.23.0 ### Browser and version Firefox 125 ### Can you reproduce the bug on the Vikunja demo site? Please select ### Screenshots _No response_
Author
Owner

@GrauBlitz commented on GitHub (May 10, 2024):

Well... I solved it myself. The issue was that the server time differed by a lot from the client time. But still strange that no error or hint was shown what the problem was.

@GrauBlitz commented on GitHub (May 10, 2024): Well... I solved it myself. The issue was that the server time differed by a lot from the client time. But still strange that no error or hint was shown what the problem was.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#1952