Because the system automatically manages these files upon restart, manual fixes like static file replacement are often overwritten or rendered ineffective. Recommended Resolutions
Ensure that the ssl-ca , ssl-cert , and ssl-key variables in the MySQL configuration (e.g., my.cnf ) point to the correct, persistent certificate files.
The issue is often triggered by how systemd services interact with automatically generated certificate files. When the service restarts, it may recreate or misconfigure the paths to these certificates, leading to a "handshake failure" or validation error. 100688
MySQL Bug #100688 identifies a problem where clients are unable to connect to a remote MySQL server when using certain public or CA-signed certificates. This typically occurs because the system fails to correctly validate the certificate chain when the server and client reside on different remote hosts.
Instead of relying on auto-generated system certificates, use a manually configured Public Key Infrastructure (PKI) to ensure certificates do not change unexpectedly on service restarts. Because the system automatically manages these files upon
To resolve this connectivity issue, administrators typically need to:
If the service is regenerating files, use a systemd override to specify exact execution environments that don't interfere with your SSL setup. When the service restarts, it may recreate or
The code is associated with a specific, long-standing bug in MySQL regarding secure remote connections. The Issue: SSL/TLS Connection Failures