• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • 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.

Debian 7.6 point releases causes autoinstaller to break

Tozz

Regular Pleskian
Recently Debian released point release .6 of Debian Wheezy (Debian 7). This change in version number is causing all Plesk updates and upgrades to fail, due to 404 errors:

Code:
Getting new version of Parallels Installer...
File downloading parallels_installer_Debian_7.6_x86_64.md5sum: 
ERROR: The required version '3.16.20' was not found on the server.
This could happen because of configuration error at the download site.
Failed to download the package [url]http://autoinstall.plesk.com/Parallels_Installer/parallels_installer_Debian_7.6_x86_64.md5sum:[/url]
The requested URL returned error: 404

This has been going on a couple of days. When will this be fixed?
 
Using the plesk-installer on that URL seems to resolve the issue, but although this works I don't find this a real solution.
The Plesk auto-updater also breaks, and has been sending update failure notices the past few days.

So, the auto-updater is unreliable and requires manual intervention. This also isn't the first time this has happened with a Debian point release.

Will this issue be permanently resolved in the future?
 
Back
Top