• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

I cant upgrade to Plesk 8.2

I

Isaacj

Guest
Hello!, i'm trying to upgrade to the last version of Plesk, i'm currently running 8.1.1, but when i try to upgrade to 8.2.0 or 8.2.1 appears this error:

The following could cause the installation failure:
1)Packages "psa-php4-configurator-1.1.0-rhel4.build81061129.22.noarch" and "psa-php4-configurator-1.3.0-rhel4.build82070807.17.noarch" cannot be installed at the same time
.

2)Packages "php-4.3.9-3.18.x86_64" and "php-4.3.9-3.22.9.x86_64" cannot be installed at the same time
because of the conflict on the file "/etc/httpd/conf.d/php.conf"

Here is my uname:

Linux ############ 2.6.9-55.ELsmp #1 SMP Fri Apr 20 16:36:54 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux

What could be the problem?

Thanks for all.
 
Hi,

This indicates that Plesk can not be installed due to dependency issues.

It looks like it can not install psa-php4-configurator-1.3.0-rhel4.build82070807.17.noarch because it can not be installed together with php-4.3.9-3.18.x86_64 but I am not quite sure about this.

To find exact chain of dependencies that lead to this error you should look in autoinstaller log file: /tmp/autoinstaller3.log

If you do not manage to resolve these dependencies yourself post qoute from autoinstaller log with dependency resolving description and we will try to review it together ;)
 
Back
Top