Facebook
Twitteregyklikkcom
New Pleskian
- Server operating system version
- Ubuntu 22.04.5 LTS
- Plesk version and microupdate number
- Plesk Obsidian 18.0.74
We've been trying to update for several days, but:
-
We value your experience with Plesk during 2025
Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025.
Please take this short survey:
https://survey.webpros.com/
Issue Why is the MariaDB repo server not working?
- Thread starter egyklikkcom
- Start date
learning_curve
Golden Pleskian
There's nothing wrong with the url shown in your post (you presumably have already confirmed that outside of the upgrade process) which is expected.
You don't have a forum signature & you've not provided any details in your post, so it's not clear which MariaDB releases you're trying to upgrade from / to.
Are you using the Plesk UI process that's covered in this Plesk support page ? If so, then you may have noticed that the Plesk UI option, is still a "beta test" (sic) tool, so as a result, there are many comments on that support page and on this forum thread too (which you've already visited).
FWIW Many users (us included) have always used the Manual procedure that's also featured on that same support page, without big issues or any setbacks.
Tim_Wakeling
Basic Pleskian
I'm afraid there IS a problem with the URL shown in the post. It is returning an error: "Oops! Something went wrong, but we're working on it. Please try again later." But it has been doing this for a while now, and it may be time to investigate whether this is going to be fixed by MariaDB or is because they have moved something and Plesk needs updating to match?
sistemas@chequemotiva
New Pleskian
Hi:
Yes, the problem is of mariadb, in that url comment this error:
Thanks!
Yes, the problem is of mariadb, in that url comment this error:
Thanks!
learning_curve
Golden Pleskian
As stated really @Tim_Wakeling. There was no problem with the URL outside of the OP's post (we don't use the same process, so can't comment on errors from within the OP's post), The point being, it's not the URL itself that is defective. Some where within the OP's config / your config (you have the same issue now it seems, as you have posted a seperate thread ) there's an error when calling that URL. Having said that, the OP and youself, run differnt OS on your servers, so it would appear that the error is either within the Plesk UI config (which we don't use...) and/or it's a third party (that you both use) invoked error (e.g. Cloudfare as an example). We've always used the Manual procedure that's also featured on the support page (link in previous post), without any big issues or any setbacks.
Tim_Wakeling
Basic Pleskian
Well, the URL is returning an error, and the error is nothing to do with the Plesk server calling it; it's a problem at the MariaDB end. We can see that because the same error is returned outside of Plesk from a browser. So all I'm saying is, given this error has persisted for several days, it may be time for Plesk to look into whether the URL needs to change or MariaDB is going to fix it. One of those needs to happen for the tool, which is an advertised Plesk feature, to work. Fortunately, as I have discovered elsewhere, the team does appear to be aware of the issue, so I hope to hear about a fix (from one side or the other) soon. Failing that, I'll do the manual method, but there is a reason the tool exists - the manual method is not easy.
learning_curve
Golden Pleskian
Yet... not for us (see forum sig)
Again, not for us!
Understood. Looks like Plesk do need to address this if it is their own issue and/or post a workaround for all that may be effected if it's a MariaDB issue.
Yes, you're right, the manual upgrade process is more challenging, especially when upgrading to MariaDB 11.4.* but, we did it some time ago now and it was all okay. Have posted a link which may assist you on your own thread.
Tim_Wakeling
Basic Pleskian
You're not seeing the error in a browser? That's odd!
I am seeing it even when using another device not connected to my WiFi, with no link whatsoever to my Plesk server.
learning_curve
Golden Pleskian
Yes, not seeing it in a browser, but to be 100% accurate:
We get redirected from that link, to here: Download MariaDB Server - MariaDB.org (momentarily...)
Then re-redirected to here: Download MariaDB Server - MariaDB.org
The result is then a manual selection process relating to which Maria DB release is required, as you'll already know
In fairness, can see why, that redirect / redirect process would cause errors, if, it is within a Plesk UI upgrade (i.e. no manual input)
OElemental
New Pleskian
And I've had the same problem for the past few days on AlmaLinux 9.7 and MariaDB 11.4. It's partly fixed by changing the baseurl in /etc/yum.repos.d/mariadb.repo to:
But I still don't have a working url for updating mariadb-tools, which causes the update engine to timeout.
Does anyone know of a current working mirror for MariaDB Tools?
Tim_Wakeling
Basic Pleskian
Just tried that URL again and now it is working.
I won't run the MariaDB upgrade right now in the middle of the working day, but will try it again when I can out of hours. Maybe now it will work...
I won't run the MariaDB upgrade right now in the middle of the working day, but will try it again when I can out of hours. Maybe now it will work...
OElemental
New Pleskian
I still can't get the right result from "baseurl = Index of /legacy/tools/rhel/9/x86_64/"
It looks like the MariaDB Tools repo has moved to "Index of /legacy/tools/rhel/9/x86_64/" for AlmaLinux 9
It looks like the MariaDB Tools repo has moved to "Index of /legacy/tools/rhel/9/x86_64/" for AlmaLinux 9
OElemental
New Pleskian
That should have said - custom-downloads.mariadb.com/legacy/tools/rhel/9/x86_64
has replaced - downloads.mariadb.com/Tools/rhel/9/x86_64
has replaced - downloads.mariadb.com/Tools/rhel/9/x86_64
