https://bugs.kde.org/show_bug.cgi?id=503894
--- Comment #19 from Karsten de Freese <[email protected]> --- I've been able to resolve my problem in the meantime - 1st of all, I was wrong in assuming that the mariadb version installed on my server already provides TLS connections with self-generated certificates - this is only with a very recent version of mariadb I cannot use for other reasons (not supported with nextcloud) - So I configured mariadb TLS with the certificates I'm using for a web server on the same machine. This did the trick, and digikam connects to its databases again. No changes needed in digikam's database configuration. -- You are receiving this mail because: You are watching all bug changes.
