Search results

I see the latest update readme mentions a script to upgrade from CentOS 7 to AlmaLinux 8. However it says Virtuozzo and Docker containers are not supported. Is there an alternative way to upgrade a container? If not, has anyone switched to using VMs instead of containers so future upgrades...

This suggestion (time limit hotfixes and/or system updates) can be voted on at Have some setting to limit days and timeframe of any updates

I understand this is an old thread but Plesk support pointed me to it. The configured update schedule is also not used for "system updates" which are always installed daily.

After banging on this a while I eventually found there was an IPv6 routing issue in the data center, outside of our equipment. It was a bit subtle as it only affected some IPv6 connections, both inbound and outbound, so was not easy to pick up in testing...most pinging was fine but the...

Support says a cert for any additional domain aliases is unnecessary and we should only create certs for the primary domain. :eek: I guess the "solution" is to validate only certain domains so it doesn't time out.

Per Change Log for Plesk Obsidian this extension is now part of SSL It, is that correct? Should a separate thread be pinned for that? Does anyone know a way to lengthen the timeout for an LE cert validation beyond the current roughly 10 minutes? See Issue - SSL It! - LE Cert fails: The...

Yet another example...this site had all certs fail to renew yesterday but it retried automatically overnight and worked for some of them, so now we've got to hammer it until it works for the rest of the domains, limited by LE's daily cert limits. "Permanent SEO-safe 301 redirect from HTTP to...

I should note that I checked our router's Suricata which isn't blocking the connection. Presumably LE servers aren't on threat lists like Spamhaus DROP or ET or CINS, though I did just try to remove that block temporarily to test, to no avail. Does LE verify over IPv4? The log entries I saw...

We started having trouble with LE cert renewal several days ago, on multiple servers. The automatic renewal fails more frequently on sites with multiple aliases, hence multiple domains. Some renew fine but for 1-2 on each site we see either: Timeout during connect (likely firewall problem)...

Plesk published a KB article patch: https://support.plesk.com/hc/en-us/articles/4410046014610-Plesk-Update-Manager-fails-on-Almalinux-8-5-OS-NoneType-object-has-no-attribute-run-sack- After doing that the System Updates check now succeeds, at least if run manually.

I had opened a ticket with Plesk this morning on this. We had converted a CentOS 8 to AlmaLinux on Friday and get the error daily since then, though I can install updates via yum just fine, and in fact installed two today just to prove it worked. re: the number of updates not being correct, 1)...

Already did per the above but thanks. :) I looked at the servers that upgraded to 18.0.35 since I did this last Thursday and all had one extra fail2ban.sqlite3.* file. So not an infinite number nor enough to run out of space as the Plesk KB describes, thankfully, but if the database is (used to...

I see, thanks for the update. I hadn't had a change to dig into it much yet but I had already scripted the two commands above, plus one to delete the extra, dated copies: rm -f /var/lib/fail2ban/fail2ban.sqlite3.* Also note article After update to Plesk 18.0.35 disk space usage increases...

The space issue caused a failed Plesk upgrade (we got the email alert 30 hours later, after the second attempt/failure) so I had to engage support. Along the way they wrote: "Since 18.0.35 fail2ban was updated to version v0.11 which has automatic scripts for purging old fail2ban data, therefore...

We had a client's server run out of disk space last night. It looks like fail2ban had made several copies of its database for some reason until it ran out: -rw------- 1 root root 1232522240 May 4 09:18 fail2ban.sqlite3 -rw------- 1 root root 1232522240 May 3 21:03...

Hmm, so why did it fail until I put in that setting and (apparently more importantly) triggered a PHP restart? /tmp did exist of course. Unless something disconnected the running PHP process from tmp? Or it uses the longer path and moves the file into /tmp? (inquiring minds want to know...)

Hi Igor, I see... I didn't get that far, but if I remove "upload_tmp_dir = /tmp" the upload works. So likely you are correct that adding the setting would have restarted the site and/or PHP. So is the default for Plesk+PHP FPM the...

Server is CentOS Linux release 7.9.2009 (Core). A web site uploads a CSV file for import. I am told it worked approximately Jan. 20. On Jan. 27 we installed CentOS updates. As the server admin I made no other recent changes and Plesk updated in early January. This week when the user tried...

It isn't out yet, the Virtuozzo blog says Q1 2021. If there is no supported path with Plesk to upgrade from CentOS 7 to 8 (Resolved - upgrade from centos 7 to centos 8 supported ?) then it seems like even though we (in this thread) are "used to" CentOS it might be time to consider other...

Yes, it is not my choice. :) We have been strongly recommending WordPress sites and really any sites move to PHP 7.x but some clients resist change.