Recent content by akira9000

Had same situation last night. Alma 9.8 - upgraded stock MariaDB 10.5.x to 10.11.x in the GUI. Plesk 18.0.77 ( noticed the machine has just updated to 18.0.78 through the night ) Wordpress sites no longer connect on localhost. Have to use 127.0.0.1. Machine runs fine apart from that. Have...

Username: TITLE upgrade to Mariadb 10.11 now Wordpress only connects to DB on 127.0.0.1 PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Alma 9.8, Plesk 18.0.78, Maria DB 10.11.18 PROBLEM DESCRIPTION Upgraded Maria DB to 10.11.18 from the default 10.5.x that was on the machine...

Hi people. Did anybody get any further with this one? I am being hit with "Serve static assets with an efficient cache policy" throughout all my Wordpress sites too. Anybody aware of additional Nginx directives to appease Google insights reports? I usually run with the attached by default...

Was anything pushed automatically last night? Been having the Apache 123 page appearing sporadically since the 26th. Been getting round it by turning off Apache and going entirely via Nginx on certain subs. Then this morning, everything back to normal, all my machines acting like this never...

Ignore - me not noticing the mirror dropdown!

Just doing some housekeeping and noticed that the repo URLs on the MariaDB main site are different to the syntax on the guide I referenced at the start of the thread. The old ones look like: [mariadb] name = MariaDB baseurl = http://yum.mariadb.org/10.5/centos7-amd64 gpgkey =...

Thanks Peter

Hi, This Plesk help article details upgrading from 10.0 to 10.1 How to upgrade MariaDB 10.0 to 10.1 on CentOS 7 Just checking that I can use the steps as the basis for a machine on 10.1 already and take it up to 10.5 or up to any 10.x really? Obviously changing the repo details, I assume all...

So to round out this thread, I did actually manage to fix and forgot to post the solution. I ran into this help article - To remove duplicate install files After that, I could re-run the upgrade and all good.

This time I am also presented with this alert on the dashboard

So at least a pattern. Have checked the manual updates in Plesk and have been presented with the same ones that wouldn't auto update at the start of this thread. These look like the ones I upgraded manually after the "crash" for Obsidian 18.0.28 but this time it must be the Update #3 batch...

email alert from that machine this morning: Hello, Administrator Some problems occurred with the System Updates tool on your server xyz.com. Please resolve them manually. Reason: 2020-07-21 03:11:56 INFO: pum is called with arguments: ['--list', '--repo-info', '--json'] 2020-07-21 03:11:56...

Same here Igor. Did a yum update too. Terminal said: There are unfinished transactions remaining. You might consider running yum-complete-transaction first to finish them. The program yum-complete-transaction is found in the yum-utils package. I assume this is from the glitch I described at the...

Hi everyone, Was just running the updater on the last of my Plesk v17 boxes. CentOS 7.8.2003 8GB RAM 4 cores The updater failed right at the end with a warning that Plesk may not function. So then noticed that there were additional updates available in the Plesk Updater page which stayed...

Clearing cookies fixed mine.