• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Panel won't update

Scott.B

Basic Pleskian
I hoping someone can help me with this problem. It has been going on now for a few weeks and no sure how to get around it. I want to upgrade to Plesk 12, but want to make sure current version of 11.5.30 is working properly.

Whenever Plesk tried to update I get the following error.

Installing packages
Loaded plugins: fastestmirror, priorities, refresh-packagekit
Loading mirror speeds from cached hostfile
* atomic: www5.atomicorp.com
* epel: mirror.compevo.com
437 packages excluded due to repository priority protections
warning: rpmts_HdrFromFdno: Header V3 RSA/SHA1 Signature, key ID 4520afa9: NOKEY
Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY.art.txt
Fatal error during packages installation: The GPG keys listed for the "CentOS / Red Hat Enterprise Linux 6 - atomicrocketturtle.com" repository are already installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository.
YumBaseError: The GPG keys listed for the "CentOS / Red Hat Enterprise Linux 6 - atomicrocketturtle.com" repository are already installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository.

ERROR: Failed to run the Yum utility.
The Yum utility failed to install the required packages.
Attention! Your software might be inoperable.
Please, contact product technical support.
 
I did the command above and got this

[root@u16271698 ~]# yum update atomic-release Loaded plugins: fastestmirror, priorities, refresh-packagekit
Loading mirror speeds from cached hostfile
epel/metalink | 13 kB 00:00
* atomic: www5.atomicorp.com
* epel: mirror.compevo.com
atomic | 3.4 kB 00:00
base | 3.7 kB 00:00
extras | 3.4 kB 00:00
updates | 3.4 kB 00:00
434 packages excluded due to repository priority protections
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package atomic-release.noarch 0:1.0-16.el6.art will be updated
---> Package atomic-release.noarch 0:1.0-19.el6.art will be an update
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
Package Arch Version Repository Size
================================================================================
Updating:
atomic-release noarch 1.0-19.el6.art atomic 8.5 k

Transaction Summary
================================================================================
Upgrade 1 Package(s)

Total size: 8.5 k
Is this ok [y/N]: y
Downloading Packages:
warning: rpmts_HdrFromFdno: Header V3 RSA/SHA1 Signature, key ID 4520afa9: NOKEY
Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY.art.txt


The GPG keys listed for the "CentOS / Red Hat Enterprise Linux 6 - atomicrocketturtle.com" repository are already installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository.
 
Igor

Thanks the solutions in the thread above worked.

For others who may come across this thread for a solution here is what I did.

I followed link https://www.atomicorp.com/forum/view...t=7591&p=40937 and edited the /etc/yum.repos.d/atomic.repo file.

I then updated my atomic repository by doing

yum upgrade atomic-release

After that I was able to update components. If the next scheduled update does not work I'll come back to update this thread.
 
Back
Top