Hi Jean-Christophe,
Sorry for this back and forth, I tried again to reproduce what you
mentioned but with a self-signed CA (like Rafael did in the first
comment) and it worked like a charm. Before you saying this is not the
same scenario you are facing, as far as I can see you are reporting a
problem when setting the ssl parameters (if the logs are saying "CA
certificate ca.pem is self signed" is because it is likely not reading
the files from your Let's Encrypt directory). In this case it does not
matter if it's a private or public CA. If you can confirm it is reading
your Let's Encrypt files and it is reporting that the certificate is
self signed share the logs and config files here and it will likely be
an upstream issue.
You might be tired of us asking for reproduction steps but there is no
way around that, we can't reproduce your problem. Try to add as much
details as you can, for instance, create a new container/VM of Ubutu
Focal/Groovy, install mysql-server, run command X, edit these files
adding these content, restart mysql service and so on.
I am marking this bug again as Incomplete, when you have more input for
us please change the status back to New.
** Changed in: mysql-8.0 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1890611
Title:
Client cannot connect to remote mysql-server when the latter is
configured with ssl parameters using a public CA
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1890611/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
