Conversation
…SQL modes. Reason: ERROR 2026 (HY000): TLS/SSL error: SSL is required, but the server does not support it
lucatume
approved these changes
Nov 26, 2025
Contributor
|
To make sure this would not break things in existing code, I've tested this fix on lower PHP versions:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Main Changes
Some of the more recent PHP containers have an upgraded mariadb client (11.8.3) that does not respect the TLS version or certs of older versions of MariaDB. This causes issues with
slic wp dbcommands.Combine that with some WP CLI bugs:
The simplest thing I think is to update mariadb.
Full Error Message:
How To Reproduce:
slic php-version set 8.2 -yThis should show:
mariadb:10.7.8: