starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

Unable to log in, the login request cannot be sent. #3882

New issue

Open

opened 2026-02-28 03:44:01 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-28 03:44:01 -05:00

Owner

Originally created by @fernvenue on GitHub (Jan 9, 2025).

https://github.com/louislam/uptime-kuma/issues/4828

🛡️ Security Policy

I agree to have read this project Security Policy

Description

This issue still hasn't been resolved. I replicated the problem again today, and in the browser's developer mode, I didn't see any login-related requests; it basically just throws an error directly. I tried Firefox and Chromium, all the same, got error meesage Incorrect username or password..

👟 Reproduction steps

Just login with browser.

👀 Expected behavior

😓 Actual Behavior

No actual request send to the server, just directly return the error message.

🐻 Uptime-Kuma Version

1.23.15

💻 Operating System and Arch

Debian 12 Bookworm (amd64)

🌐 Browser

Firefox 128.5.0esr (64-bit) & Chromium Version 131.0.6778.204 (Official Build, ungoogled-chromium) (64-bit)

🖥️ Deployment Environment

Runtime: nixos-unstable
Database: -
Filesystem used to store the database on: ext4
number of monitors: 12

📝 Relevant log output

No response

Originally created by @fernvenue on GitHub (Jan 9, 2025). ### 📑 I have found these related issues/pull requests - https://github.com/louislam/uptime-kuma/issues/4828 ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### Description This issue still hasn't been resolved. I replicated the problem again today, and in the browser's developer mode, I didn't see any login-related requests; it basically just throws an error directly. I tried Firefox and Chromium, all the same, got error meesage `Incorrect username or password.`. ### 👟 Reproduction steps Just login with browser. ### 👀 Expected behavior Login successfully, or at least the login request send to the server. ### 😓 Actual Behavior No actual request send to the server, just directly return the error message. ### 🐻 Uptime-Kuma Version 1.23.15 ### 💻 Operating System and Arch Debian 12 Bookworm (amd64) ### 🌐 Browser Firefox 128.5.0esr (64-bit) & Chromium Version 131.0.6778.204 (Official Build, ungoogled-chromium) (64-bit) ### 🖥️ Deployment Environment - Runtime: [nixos-unstable](https://github.com/NixOS/nixpkgs/blob/nixos-unstable/pkgs/by-name/up/uptime-kuma/package.nix) - Database: - - Filesystem used to store the database on: `ext4` - number of monitors: 12 ### 📝 Relevant log output _No response_

deekerman added the

bug

A:deployment

labels

2026-02-28 03:44:01 -05:00

deekerman commented

2026-02-28 03:44:04 -05:00

Author

Owner

@fernvenue commented on GitHub (Jan 9, 2025):

It seems to be related to the disabled authentication. Accessing /dashboard still requires login, but authentication cannot be completed because it has been disabled.

@fernvenue commented on GitHub (Jan 9, 2025): It seems to be related to the disabled authentication. Accessing `/dashboard` still requires login, but authentication cannot be completed because it has been disabled.

deekerman commented

2026-02-28 03:44:04 -05:00

Author

Owner

@appletonzzzz commented on GitHub (Jan 18, 2025):

I am having the same issue. Steps to reproduce for me:

Switch on auth
Don’t set a password
Switch off auth
Navigate away from the auth page
Locked out of dashboard

@appletonzzzz commented on GitHub (Jan 18, 2025): I am having the same issue. Steps to reproduce for me: 1. Switch on auth 2. Don’t set a password 3. Switch off auth 4. Navigate away from the auth page 5. Locked out of dashboard

deekerman commented

2026-02-28 03:44:04 -05:00

Author

Owner

@github-actions[bot] commented on GitHub (Oct 15, 2025):

This issue was marked as cannot-reproduce by a maintainer.
If an issue is non-reproducible, we cannot fix it, as we do not know what the underlying issue is.
If you have any ideas how we can reproduce this issue, we would love to hear them.

We don't have a good way to deal with truely unreproducible issues and are going to close this issue in a month.
If think there might be other differences in our environment or in how we tried to reproduce this, we would appreciate any ideas.

@github-actions[bot] commented on GitHub (Oct 15, 2025): This issue was marked as `cannot-reproduce` by a maintainer. If an issue is non-reproducible, we cannot fix it, as we do not know what the underlying issue is. If you have any ideas how we can reproduce this issue, we would love to hear them. We don't have a good way to deal with truely unreproducible issues and are going to close this issue in a month. If think there might be other differences in our environment or in how we tried to reproduce this, we would appreciate any ideas.