Search results

I just found this new support article in the help center: After March 20, 2019, installation of system updates on Plesk servers with Debian 8 fails: Failed to fetch http://ftp.debian.org/debian/dists/jessie-updates: 404 Not Found This seems to address the issue. Will try later. Maybe linking it...

I'm surprised that there are so few with that problem. Has everyone upgraded to stretch already? Maybe the majority hasn't noticed yet, their system isn't updating properly any more. Maybe there is also a difference between wheezy, which is EOL (end of life) and jessie, which is in LTS. LTS -...

made a new thread here: debian jessie apt/system update error mow, maybe you would like to consider posting there as well.

I have an issue with apt updates here, running plesk onyx 17.8.11 update 46 on vps with debian jessie 8.11. See error message above (expand). Possibly also with wheezy. "jessie-updates" source on debian mirrors dosn't exist any more. debian restructured the mirrors yesterday. stretch might not...

Similar issue here. Running plesk onyx 17.8.11 update 46 on vps with debian jessie 8.11. jessie-updates doesn't exist any more. Are IgorG's answers #2 / #4 still the recommended solution? Edit: Possibly not. My Plesk is already set to the "Official Plesk Updates server". After reading twice my...

Hi JohannesT, yes i did do the dist-upgrade. And also the one, that you mentioned above. As a precaution i made a snapshot of the previous state. But it could be wise to ask the hoster of your virtual private server first, since not all hosters use virtualization technologies that support...

Update via command line has worked: /usr/local/psa/admin/bin/autoinstaller

Here is the /tmp/autoinstaller3.log from klicking Updates&Upgrades to klicking "Cancel" after the error message. I think somewhere in the process it decides 17.5.3 was the best version for me and switches me to the component selection. File-Upload.net - log.txt (Edit: Link and linked file deleted)

Hi, Updates & Upgrades shows me that an update to Plesk Onyx 17.8.11 is available. When i follow the steps i get shown a dialogue that allows me to choose Plesk Onyx 17.8.11. After klicking continue, it tells me it is downloading a new plesk installer. After that i get shown the components...

Thank you. I don't see how my case is covered by the support article, since i'm not planing to do a unsupported release upgrade from debian 8 to 9 and didn't change sources.list. apt-get wants to run "dist-upgrade" to do a kernel upgrade which isn't covered by "upgrade". But i guess no one can...

Try to switch Web application firewall mode off an on again. It should work again. At least it does here. There seems to have been a problem with the global user used for the updates. Mark Muyskens solved it together with atomicorp here: Issue - Atomic Base security can not update itself

Works with own account. Thank you! But had to mind, that plesk changes username/password back to the global one when changing settings in the interface. sudo /usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php –f UpdateModSecurityRuleSet ...now runs...

Already did that. Didn't help. We are five people now with the problem in this thread and the other one. Maybe it's a more global problem. Maybe there are only so few because it's weekend. Since i don't have time for further tests anyway i will wait a day or two before investigating more deeply...

Hi, i'm running plesk 17.5.3 #43 web admin edition on debian 8.10 on a virtual private server (kvm) Plesk shows everything is up to date in Tools and Settings - System Updates An "apt-get upgrade" via command line shows: sudo apt-get upgrade ... The following packages have been kept back...

Followed the guide for reinstallation of modsec closely. Now this error shows up, when trying to switch on modsec with atomic basic ruleset. So now it's worse than before, since modsec is off now.

The support page says we should contact Atomicorp for activation of the account. I can't remember creating an account for using the Atomic Basic ModSecurity ruleset half a year ago. There is no field for entering account data for the basic ruleset in plesk. Isn't or wasn't there a global account...

another thread: Issue - Atomic Base security can not update itself

looks like this problem: Issue - ModSecurity - Authorization failed attempting to download an update

So here we are again after the daily cron run: "Error: Failed to update the ModSecurity rule set. Details"

Let's hope it's not only gone until the next cron run, which checks for an update.