starred/uptime-kuma

Fork 0

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

Wrong datatype error #1039

New issue

Closed

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

deekerman commented

2026-02-28 02:08:03 -05:00

Owner

Originally created by @Goldenflamer on GitHub (Apr 27, 2022).

⚠️ Please verify that this bug has NOT been raised before.

I checked and didn't find similar issue

🛡️ Security Policy

I agree to have read this project Security Policy

Description

There is an error causing a problem when saving certain values. Even if the datatype of the input is correct, there is an error saying "Wrong Datatype?" The error appears most consistently when adding a Steam API key via the settings but I have also seen it with other values. I am using the No Auth mode if that matters,

Steam key has the form A89A....... and is copied and pasted from steam directly, so it is 100% correct.

👟 Reproduction steps

Go to Settings and add a Steam API key
After inserting the Steam API key press save buttton

👀 Expected behavior

Steam API Key should be saved

😓 Actual Behavior

Error popup saying "Wrong data type?"

🐻 Uptime-Kuma Version

1.15.0

💻 Operating System and Arch

Windows 10 21H2 newest Updates as of posting date

🌐 Browser

Google Chrome 101.0.4951.41 64 bit

🐋 Docker Version

Docker Standalone 20.10.14

🟩 NodeJS Version

No response

📝 Relevant log output

No response

Originally created by @Goldenflamer on GitHub (Apr 27, 2022). ### ⚠️ Please verify that this bug has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### Description There is an error causing a problem when saving certain values. Even if the datatype of the input is correct, there is an error saying "Wrong Datatype?" The error appears most consistently when adding a Steam API key via the settings but I have also seen it with other values. I am using the No Auth mode if that matters, Steam key has the form A89A....... and is copied and pasted from steam directly, so it is 100% correct. ### 👟 Reproduction steps Go to Settings and add a Steam API key After inserting the Steam API key press save buttton ### 👀 Expected behavior Steam API Key should be saved ### 😓 Actual Behavior Error popup saying "Wrong data type?" ### 🐻 Uptime-Kuma Version 1.15.0 ### 💻 Operating System and Arch Windows 10 21H2 newest Updates as of posting date ### 🌐 Browser Google Chrome 101.0.4951.41 64 bit ### 🐋 Docker Version Docker Standalone 20.10.14 ### 🟩 NodeJS Version _No response_ ### 📝 Relevant log output _No response_

deekerman

2026-02-28 02:08:03 -05:00

closed this issue
added the
bug
label

deekerman commented

2026-02-28 02:08:06 -05:00

Author

Owner

@chakflying commented on GitHub (Apr 27, 2022):

Saw this too, I think there is a bug with the authentication code when using No Auth mode, but I'm not sure exactly what's going on. Please try to enable auth and login again and the problem should go away.

@chakflying commented on GitHub (Apr 27, 2022): Saw this too, I think there is a bug with the authentication code when using No Auth mode, but I'm not sure exactly what's going on. Please try to enable auth and login again and the problem should go away.

deekerman commented

2026-02-28 02:08:08 -05:00

Author

Owner

@Goldenflamer commented on GitHub (Apr 27, 2022):

Saw this too, I think there is a bug with the authentication code when using No Auth mode, but I'm not sure exactly what's going on. Please try to enable auth and login again and the problem should go away.

Yep you are right, working fine with auth

@Goldenflamer commented on GitHub (Apr 27, 2022): > Saw this too, I think there is a bug with the authentication code when using No Auth mode, but I'm not sure exactly what's going on. Please try to enable auth and login again and the problem should go away. Yep you are right, working fine with auth

deekerman commented

2026-02-28 02:08:08 -05:00

Author

Owner

@Goldenflamer commented on GitHub (Apr 27, 2022):

The problem is that doubleCheckPassword(socket, currentPassword) is called when auth is disabled which should not be the case. There is only one occurrence where there is a check before it if authentication is disabled, maybe the check could be added to other occurrences as well. Or maybe the check is not working properly.

@Goldenflamer commented on GitHub (Apr 27, 2022): The problem is that doubleCheckPassword(socket, currentPassword) is called when auth is disabled which should not be the case. There is only one occurrence where there is a check before it if authentication is disabled, maybe the check could be added to other occurrences as well. Or maybe the check is not working properly.