1
0
Fork
You've already forked openkuma
1

Cannot proceed beyond password request #1

Closed
opened 2026年07月06日 09:35:29 +02:00 by alexpcooper · 2 comments

I entered my login credentials, when first loading up the app, and it brought in all of my configuration.

Since then it subsequently asks for a password again (which I get because it's session based) but either entering the password, a wrong password or pressing cancel makes no difference - the screen remains.

Also highlighted by others on r/UptimeKuma on Reddit

I'm using 2FA, which I was asked for the first time around but have not been asked for again since.

--- UPDATE ---
Since v0.1.1 I can now hit cancel and see everything. Doesn't appear to accept the password though and most of my monitors are in a pending state. Refreshing re-triggers the password prompt.

I entered my login credentials, when first loading up the app, and it brought in all of my configuration. Since then it subsequently asks for a password again (which I get because it's session based) but either entering the password, a wrong password or pressing cancel makes no difference - the screen remains. Also highlighted by others on [r/UptimeKuma on Reddit](https://www.reddit.com/r/UptimeKuma/comments/1unjuof/comment/ovnet92/) I'm using 2FA, which I was asked for the first time around but have not been asked for again since. --- UPDATE --- Since v0.1.1 I can now hit cancel and see everything. Doesn't appear to accept the password though and most of my monitors are in a pending state. Refreshing re-triggers the password prompt.
Owner
Copy link

ok, finally managed to reproduce it — the 2FA detail was what I was missing, thanks for that.

the reconnect dialog was only asking for the password and ignoring the 2FA code, so the server kept asking for the code and the prompt just came back. there was also a separate reconnect bug that could get things stuck, which is probably why your monitors were stuck pending.

both fixed in 0.1.2: the dialog now asks for the 2FA code when your account has one, keeps what you typed, and shows the error instead of silently reopening.

it's up now, installs over your current version without losing settings: https://codeberg.org/emon/openkuma/releases/latest

let me know if it's still off after updating. thanks for sticking with it.

ok, finally managed to reproduce it — the 2FA detail was what I was missing, thanks for that. the reconnect dialog was only asking for the password and ignoring the 2FA code, so the server kept asking for the code and the prompt just came back. there was also a separate reconnect bug that could get things stuck, which is probably why your monitors were stuck pending. both fixed in 0.1.2: the dialog now asks for the 2FA code when your account has one, keeps what you typed, and shows the error instead of silently reopening. it's up now, installs over your current version without losing settings: https://codeberg.org/emon/openkuma/releases/latest let me know if it's still off after updating. thanks for sticking with it.

That's working now! Thank you, @emon ! 🙌

That's working now! Thank you, @emon ! 🙌
Sign in to join this conversation.
No Branch/Tag specified
main
v0.1.2
v0.1.1
v0.1.0
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
emon/openkuma#1
Reference in a new issue
emon/openkuma
No description provided.
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?