mirror of
https://github.com/databasus/databasus.git
synced 2026-04-06 00:32:03 +02:00
[Feature Request/Bug] Add option to disable SSL for MySQL connections (Error 2026) #55
Assignees
MrUnknownDE
Clear assignees
MrUnknownDE
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github/databasus#55
Reference in New Issue
Block a user
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?
Originally created by @Maluslock on 3/16/2026
Describe the bug
When backing up a legacy MySQL server (e.g., v5.7) or a server in a private network (192.168.x.x) that does not support modern TLS protocols or has SSL disabled, the backup fails with Error 2026.
The current implementation of Databasus seems to force SSL or relies on mysqldump defaults that trigger an SSL handshake, which fails when the server and client have a protocol mismatch (e.g., TLS 1.2 vs 1.0).
Error Log
Plaintext
Last backup error:
MySQL SSL connection failed. stderr: -- Connecting to 192.168.170.144...
mysqldump: Got error: 2026: SSL connection error: error:00000001:lib(0)::reason(1) when trying to connect
Environment
Databasus Version: latest (Docker)
Target MySQL Version: 5.7.1
Network: Private LAN
The Pain Point
Currently, there is no option in the UI to:
Pass --ssl-mode=DISABLED or --skip-ssl to the underlying mysqldump command.
Set useSSL=false in the connection string.
Forcing users to create wrapper scripts or modify system-level openssl.cnf inside the container is highly inefficient and error-prone for DevOps teams.
Suggested Solution
Please add a toggle or a dropdown in the Database Settings UI to control SSL behavior:
SSL Mode: Preferred (default), Required, or Disabled.
If Disabled is selected, append --ssl-mode=DISABLED (for MySQL 5.7+) or --skip-ssl (for MariaDB/Legacy) to the mysqldump execution.