Failed To Update Plesk

[Liam_Carey]

When I logged in today I saw this message:

"Failed to update Plesk. To solve this problem, you can send the update log to Parallels support. View the update logs (Dec 5, 2014). Copy the logs to your computer before you close this message. To close this message, click here."

Here is the error log - how do I fix this issue:

Execution failed.
Command: autoinstaller
Arguments: Array
(
[0] => --select-product-id
[1] => plesk
[2] => --select-release-current
[3] => --upgrade-installed-components
[4] => --include-components-from-class
[5] => vendor=parallels
[6] => --include-components-from-class
[7] => patched
)

Details: Doing restart of Parallels Installer...
File downloading products.inf3: Error: Couldn't resolve host 'autoinstall.plesk.com', retry...
Error: Couldn't resolve host 'autoinstall.plesk.com', retry...
Error: Couldn't resolve host 'autoinstall.plesk.com', retry...
File downloading versions.inf3: Error: Couldn't resolve host 'autoinstall.plesk.com', retry...
Error: Couldn't resolve host 'autoinstall.plesk.com', retry...
Error: Couldn't resolve host 'autoinstall.plesk.com', retry...

ERROR: Failed to read product information from the file : Can't process products.inf3: Failed to download the package http://autoinstall.plesk.com/products.inf3:
Couldn't resolve host 'autoinstall.plesk.com'

Can't process versions.inf3: Failed to download the package http://autoinstall.plesk.com/versions.inf3:
Couldn't resolve host 'autoinstall.plesk.com'


Not all packages were installed.
Please resolve this issue and try installing the packages again.
If you cannot resolve the issue on your own, contact product technical support for assistance.

 

[TarasS]

Post contents of your /etc/resolv.conf

 

[UFHH01]

Hello Liam_Carey,

you could add in "/etc/hosts" :

72.21.81.253 autoinstall.plesk.com​

... if you experience problems while connecting to a Plesk - server... but you could as well try your update/upgrade/patch later again, because such issues normally are for a short duration ( some DNS - server might be under high traffic or any other related issue, that causes to an unexpected false domain resolution ).