version 2.1.0-beta.1 there is a bug where the connection string with the Microsoft SQL Sever database stops working #4581

New issue

Closed

opened 2026-02-28 04:08:08 -05:00 by deekerman · 1 comment

deekerman commented

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

Owner

Originally created by @rodrigobuch on GitHub (Jan 6, 2026).

in version 2.1.0-beta.1 there is a bug where the connection string with the Microsoft SQL Sever database stops working
connection example:

SQL Server: Server=192.168.0.12;Database=prd_integracao_test;User Id=test;Password=******;

UptimeKuma log error:

[SQLSERVER] ERROR: Database query failed: Multiple values were found, expected only one value
2026-01-06T16:16:25-03:00 [MONITOR] WARN: Monitor #30 'MSSQL - PROTOCOLOS - AWS': Pending: Database connection/query failed: Multiple values were found,
expected only one value | Max retries: 2 | Retry: 2 | Retry Interval: 7200 seconds | Type: sqlserver

🛡️ Security Policy

I have read and agree to Uptime Kuma's Security Policy.

📝 Description

No response

👟 Reproduction steps

👀 Expected behavior

the monitor connection stopped working after update

😓 Actual Behavior

the monitor connection stopped working after update

🐻 Uptime-Kuma Version

2.1.0-beta.1

💻 Operating System and Arch

Ubuntu Server 24.04 LTS

🌐 Browser

Google Chrome

🖥️ Deployment Environment

Runtime Environment:
- Docker: Version X.X.X (Build Y.Y.Y)
- Docker Compose: Version X.X.X
- Portainer (BE/CE): Version X.X.X (LTS: Yes/No)
- MariaDB: Version X.X.X (LTS: Yes/No)
- Node.js: Version X.X.X (LTS: Yes/No)
- Kubernetes (K3S/K8S): Version X.X.X (LTS: Yes/No, via [method/tool])
Database:
- SQLite: Embedded
- MariaDB: Embedded/External
Database Storage:
- Filesystem:
  - Linux: ext4/XFS/Btrfs/ZFS/F2FS
  - macOS: APFS/ HFS+
  - Windows: NTFS/ReFS
- Storage Medium: HDD/eMMC/SSD/NVMe
Uptime Kuma Setup:
- Number of monitors: X

📝 Relevant log output

SQL Server: Server=192.168.0.12;Database=prd_integracao_test;User Id=test;Password=******;

UptimeKuma log error:

[SQLSERVER] ERROR: Database query failed: Multiple values were found, expected only one value
2026-01-06T16:16:25-03:00 [MONITOR] WARN: Monitor #30 'MSSQL - PROTOCOLOS - AWS': Pending: Database connection/query failed: Multiple values were found, 
expected only one value | Max retries: 2 | Retry: 2 | Retry Interval: 7200 seconds | Type: sqlserver

Originally created by @rodrigobuch on GitHub (Jan 6, 2026). ### 📑 I have found these related issues/pull requests in version 2.1.0-beta.1 there is a bug where the connection string with the Microsoft SQL Sever database stops working connection example: SQL Server: Server=192.168.0.12;Database=prd_integracao_test;User Id=test;Password=******; UptimeKuma log error: [SQLSERVER] ERROR: Database query failed: Multiple values were found, expected only one value 2026-01-06T16:16:25-03:00 [MONITOR] WARN: Monitor #30 'MSSQL - PROTOCOLOS - AWS': Pending: Database connection/query failed: Multiple values were found, expected only one value | Max retries: 2 | Retry: 2 | Retry Interval: 7200 seconds | Type: sqlserver ### 🛡️ Security Policy - [x] I have read and agree to Uptime Kuma's [Security Policy](https://github.com/louislam/uptime-kuma/security/policy). ### 📝 Description _No response_ ### 👟 Reproduction steps <img width="1898" height="202" alt="Image" src="https://github.com/user-attachments/assets/23f9e74e-883f-4517-bc52-fe4b71dc97c4" /> ### 👀 Expected behavior the monitor connection stopped working after update ### 😓 Actual Behavior the monitor connection stopped working after update ### 🐻 Uptime-Kuma Version 2.1.0-beta.1 ### 💻 Operating System and Arch Ubuntu Server 24.04 LTS ### 🌐 Browser Google Chrome ### 🖥️ Deployment Environment - **Runtime Environment**: - Docker: Version `X.X.X` (Build `Y.Y.Y`) - Docker Compose: Version `X.X.X` - Portainer (BE/CE): Version `X.X.X` (LTS: Yes/No) - MariaDB: Version `X.X.X` (LTS: Yes/No) - Node.js: Version `X.X.X` (LTS: Yes/No) - Kubernetes (K3S/K8S): Version `X.X.X` (LTS: Yes/No, via `[method/tool]`) - **Database**: - SQLite: Embedded - MariaDB: Embedded/External - **Database Storage**: - **Filesystem**: - Linux: ext4/XFS/Btrfs/ZFS/F2FS - macOS: APFS/ HFS+ - Windows: NTFS/ReFS - **Storage Medium**: HDD/eMMC/SSD/NVMe - **Uptime Kuma Setup**: - Number of monitors: `X` ### 📝 Relevant log output ```bash session SQL Server: Server=192.168.0.12;Database=prd_integracao_test;User Id=test;Password=******; UptimeKuma log error: [SQLSERVER] ERROR: Database query failed: Multiple values were found, expected only one value 2026-01-06T16:16:25-03:00 [MONITOR] WARN: Monitor #30 'MSSQL - PROTOCOLOS - AWS': Pending: Database connection/query failed: Multiple values were found, expected only one value | Max retries: 2 | Retry: 2 | Retry Interval: 7200 seconds | Type: sqlserver ```

deekerman

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

closed this issue
added the
bug
label

deekerman commented

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

Author

Owner

@CommanderStorm commented on GitHub (Jan 6, 2026):

Was already fixed yesterday in the following PR:

https://github.com/louislam/uptime-kuma/pull/6601

@CommanderStorm commented on GitHub (Jan 6, 2026): Was already fixed yesterday in the following PR: - https://github.com/louislam/uptime-kuma/pull/6601