mythfrontend v36 requires database SSL?

[gocubsgo]

I just updated to v36 (from v35) on my Fedora backend and macOS frontends. Everything seems to be fine on the server, but mythfrontend fails to connect to the database with this error:

Code: Select all

2026-04-16 11:12:27.357539 E  [DBManager2] Unable to connect to database!
2026-04-16 11:12:27.357544 E  Driver error was [1/2026]:
QMYSQL: Unable to connect
Database error was:
TLS/SSL error: SSL is required, but the server does not support it

I'm not really interested in enabling TLS/SSL for mariadb. How can I force the mythfrontend client to not use SSL?

[white_haired_uncle]

I'm not a db guy, but you might try this (or something similar):

Code: Select all

spartan$ cat ~/.my.cnf
[client]
skip-ssl = true

[gocubsgo]

Thanks for the suggestion. I had tried that, but still got the same error. I think this is the flag that needs to be changed, but perhaps embedded mysql clients don't use ~/.my.cnf?

[gocubsgo]

In the absence of a more permanent solution, I was able to work around this issue by adding this

Code: Select all

export MARIADB_TLS_DISABLE_PEER_VERIFICATION=1

to /Applications/mythfrontend.app/Contents/MacOS/mythfrontend.zsh

[jhoyt]

I don't know what version of mariadb you're running, but this worked on my system.

On the server, edit the files in /etc/mysql/mariadb.conf.d and/or /etc/mysql/mysql.conf.d for any ssl entries (e.g. ssl-ca, ssl-key, ssl-cert). Comment them out then restart mariadb.

[gocubsgo]

From the error mythfrontend was showing, I assumed my server wasn't configured for SSL. I just confirmed that by reviewing /etc/my.cnf.d/mariadb-server.cnf and adjacent files.

The trouble was mythfrontend on my Macs was failing to connect because "SSL is required". Hacking MARIADB_TLS_DISABLE_PEER_VERIFICATION into mythfrontend.zsh worked, but I'll have to remember to re-apply it when I upgrade.