Article ID: 113175, created on Jan 17, 2012, last review on Aug 4, 2016

  • Applies to:
  • Plesk


It is not possible to retrieve Plesk packages from the repository at The following error is displayed:

Getting new version of Parallels Installer...
ERROR: The required version '3.11.0' was not found on the server.
This could happen because of configuration error at the download site.
Failed to download the package
The requested URL returned error: 404
Not all packages were installed.

OR [Errno -1] Package does not match intended download. Suggestion: run yum --enablerepo=PHP_5_3_29-dist clean metadata
Trying other mirror.
centos7.15020319.x86_64: [Errno 256] No more mirrors to try.', u'plesk-php53-ioncube-loader-4.7.2-centos7.15020319.x86_64: [Errno 256] No more mirrors to try.', u'plesk-php52-xdebug-2.2.3-
ERROR: Failed to run the Yum utility.
The Yum utility failed to install the required packages.

It is also not possible to download the file using wget:


Connecting to||:80... connected.
HTTP request sent, awaiting response... 200 OK 
Length: 222396 (217K) [text/xml] 
Saving to: `plesk.inf3.9' 3% [====> ] 6,960 --.-K/s in 0.001s 
2013-09-01 00:21:21 (6.56 MB/s) - Read error at byte 6960/222396 (Connection reset by peer). Retrying.


  1. Plesk uses a content delivery network (CDN) to distribute Plesk packages. This technology uses several cache servers which are distributed across different parts of the internet. All of the servers share a common domain name,, which resolves to different IP addresses depending on the network segment that a request comes from. Sometimes, a server becomes out of sync with the main replica and files go missing.

  2. Network issues (TCP window scaling).


Use the main replica of the Plesk repository until your local CDN server synchronizes with it. To do this, configure a static resolution rule in the file /etc/hosts:


If this does not help, disable TCP window scaling:

echo 0 > /proc/sys/net/ipv4/tcp_window_scaling

See the following link for more details on TCP window scaling

If the issue still persists, open the /etc/hosts file and replace: 


a914db3fdc7a53ddcfd1b2db8f5a1b9c 56797cefb1efc9130f7c48a7d1db0f0c 5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 614fd0b754f34d5efe9627f2057b8642 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF