Date: prev next · Thread: first prev next last
2026 Archives by date, by thread · List index


I am using LO Base to connect from my desktop client to a home network
mariadb server. However, the version of LibreOffice from OpenSUSE fails
to connect to the mariadb server with an error message complaining that
my mariadb does not support provide TLS/SSL connection (which was
apparently not required, and therefore not used in the previous OS
versions of the LOBase connector configurations. I use the
MySQL/Mariadb Connector.  

The community version of LO with MySQL/Mariadb Connector does not
require TLS/SSL support, so everything works as always previously.

Currently I have installed LibreOffice 
Version: 25.8.4.2 (X86_64)
Build ID: 290daaa01b999472f0c7a3890eb6a550fd74c6df
CPU threads: 2; OS: Linux 6.19; UI render: default; VCL: gtk3
Locale: en-GB (en_GB.UTF-8); UI: en-US
Calc: threaded

How can I tell the connector driver not to expect TLS/SSL support from
the MariaDB? The alternative would be to tell the MAriaDB to support
TLS/SSL. But that seems equally mysterious.

Cheers
Harvey

-- 
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/users/
Privacy Policy: https://www.documentfoundation.org/privacy

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.