• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue "Allow local MariaDB/MySQL server to accept external connections" unchecked after every MariaDB update

bybl

New Pleskian
Server operating system version
Ubuntu 22.04
Plesk version and microupdate number
Plesk Obsidian v18.0.66_build1800250106.19
I'm running a MariaDB installation on my always up-to-date Plesk server (the one used by Plesk itself). However, every time MariaDB updates automatically, the option in the title gets unchecked. (The option in Tools & Settings > Database Servers > localhost (MariaDB))
This has happened multiple times over the past few months, leading to frustrated customers who suddenly can't connect to their applications or databases.

Is there any way to prevent this from happening besides manually updating packages and rechecking the option each time?

I couldn't find a similar thread, but I find it hard to believe this is normal. Could this be a misconfiguration on my part or just a bug?
 
I just came here to report exactly the same issue this morning after last night's MariaDB update. I have experienced it before, but can't be sure it's everytime MariaDB updates itself. I've also had the mariadb.conf file reset to default after an update too on one occasion which was quite disastrous for our site!
 
@bybl / @TurnRound FWIW We've never had this issue, ever.
That's going right back to when we started using Plesk / MariaDB etc back in 2017.
However, we have always used manual updates and never auto-updates, that might / might not be a factor
 
This is a known bug identified with ID PPPM-14664, as a result /etc/mysql/my.cnf is being rolled back to vendor settings. Our team will introduce a fix in one of the upcoming releases. At this time, I cannot provide any ETA.

The suggested workaround until the bug is fixes is to define bind-address = 0.0.0.0 in another config file, such as /etc/mysql/conf.d/bind-address.conf. I hope that helps.
 
This is a known bug identified with ID PPPM-14664, as a result /etc/mysql/my.cnf is being rolled back to vendor settings. Our team will introduce a fix in one of the upcoming releases. At this time, I cannot provide any ETA.

The suggested workaround until the bug is fixes is to define bind-address = 0.0.0.0 in another config file, such as /etc/mysql/conf.d/bind-address.conf. I hope that helps.
Thank you very much, I hope this does the trick (..and for the update to come out soon).

For the future: Where can I find these bug ids / reports? I searched here and outside of the forum, but couldn't find my exact problem anywhere.
 
This is a known bug identified with ID PPPM-14664, as a result /etc/mysql/my.cnf is being rolled back to vendor settings ~~
That ^^ might be the reason, we've not had this issue
For quite a long time now (and on a few MariaDB releases previous to the current one) the following symlink has been in place: my.cnf -> mariadb.cnf
Said mariadb.cnf file is never rolled back, modified or overwritten (on any of our servers anyway)
 
For the future: Where can I find these bug ids / reports? I searched here and outside of the forum, but couldn't find my exact problem anywhere.

There is no publicly available source that lists all bugs found in the current Plesk version. There's a Report section on the Forum intended for bug reports. However, there's no guarantee the particular issue you are experiencing has been reported on the Forum. If there's no existing thread reporting an issue similar to the one you are experiencing, please do not hesitate to bring that to our attention. We are doing our best to address as many threads as possible.
 
Back
Top