Symptoms
Attempting to install WP Toolkit results in the following error:
[ root@server ~]# sh <(curl https://wp-toolkit.plesk.com/cPanel/installer.sh || wget -O - https://wp-toolkit.plesk.com/cPanel/installer.sh)
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 4034 100 4034 0 0 23633 0 --:--:-- --:--:-- --:--:-- 23729
Detecting OS type and version ...
Creating YUM Repository configuration file ...
Installing GPG ...
Loaded plugins: fastestmirror, langpacks, product-id, search-disabled-repos, subscription-manager, universal-hooks
This system is registered with an entitlement server, but is not receiving updates. You can use subscription-manager to assign subscriptions.
Loading mirror speeds from cached hostfile
* EA4: 185.53.12.144
* cpanel-addons-production-feed: 185.53.12.144
* cpanel-plugins: 185.53.12.144
EA4 | 2.9 kB 00:00:00
cpanel-addons-production-feed | 2.9 kB 00:00:00
cpanel-plugins | 2.9 kB 00:00:00
imunify360 | 2.7 kB 00:00:00
imunify360-rollout-1 | 3.0 kB 00:00:00
imunify360-rollout-2 | 3.0 kB 00:00:00
imunify360-rollout-3 | 3.0 kB 00:00:00
imunify360-rollout-4 | 3.0 kB 00:00:00
mysql-connectors-community | 2.6 kB 00:00:00
mysql-tools-community | 2.6 kB 00:00:00
mysql57-community | 2.6 kB 00:00:00
wp-toolkit-cpanel | 2.9 kB 00:00:00
https://wp-toolkit.plesk.com/cPanel/dist-rpm-rhel-7.9-x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below knowledge base article
https://access.redhat.com/articles/1320623
If above article doesn't help to resolve this issue please open a ticket with Red Hat Support.
One of the configured repositories failed (WP Toolkit third parties),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
1. Contact the upstream for the repository and get them to fix the problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).
3. Run the command with the repository temporarily disabled
yum --disablerepo=wp-toolkit-thirdparties ...
4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:
yum-config-manager --disable wp-toolkit-thirdparties
or
subscription-manager repos --disable=wp-toolkit-thirdparties
5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:
yum-config-manager --save --setopt=wp-toolkit-thirdparties.skip_if_unavailable=true
failure: repodata/repomd.xml from wp-toolkit-thirdparties: [Errno 256] No more mirrors to try.
https://wp-toolkit.plesk.com/cPanel/dist-rpm-rhel-7.9-x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
ERROR: Failed to install gnupg package, see installation log above
Description
This occurs on RedHat Operating Systems as the variable distroverpkg does not get properly written to the baseurl within the WP Toolkit yum repository. Resulting in the following repository file.
[ root@server ~]# cat /etc/yum.repos.d/wp-toolkit-cpanel.repo
[wp-toolkit-cpanel]
name=WP Toolkit for cPanel
baseurl=https://wp-toolkit.plesk.com/cPanel/wp-toolkit/
enabled=1
gpgcheck=1
[wp-toolkit-thirdparties]
name=WP Toolkit third parties
baseurl=https://wp-toolkit.plesk.com/cPanel/dist-rpm-rhel-7.9-x86_64/
enabled=1
gpgcheck=1
Workaround
Add the variable distroverpkg=centos-release within /etc/yum.conf.
This will resemble the following:
[ root@server ~]# grep distroverpkg /etc/yum.conf
distroverpkg=centos-release