HTTPS Error 301 - Moved Permanently When Performing Whm cPanel Update

Hi, I got a mail message like this:

Maintenance ended; however, it did not exit cleanly (256). The following events were logged: “scripts/update-packages”. Review the update logs to determine why the update failed.

Update log preview:
[2025-10-22 01:16:42 +0700] E [/usr/local/cpanel/scripts/update-packages] The “/usr/local/cpanel/scripts/update-packages” command (process 14910) reported error number 1 when it ended.

The log from WHM cPanel update:
[2025-10-22 01:16:42 +0700] [/usr/local/cpanel/scripts/update-packages] failed to retrieve repodata/repomd.xml from cloudlinux-x86_64-server-7
[2025-10-22 01:16:42 +0700] [/usr/local/cpanel/scripts/update-packages] error was [Errno 14] HTTPS Error 301 - Moved Permanently

The repo configuration in cloudlinux.repo:

[cloudlinux-x86_64-server-7-source]
name=CloudLinux-$releasever - source
baseurl=http://repo.cloudlinux.com/cloudlinux/$releasever/os/Sources/
enabled=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CloudLinux

[cloudlinux-x86_64-server-7-debuginfo]
name=CloudLinux-$releasever - debuginfo
baseurl=http://repo.cloudlinux.com/cloudlinux/7/debug/$basearch/
enabled=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CloudLinux

After I run yum clean all && yum makecache, it returns output like this:

One of the configured repositories failed (Unknown),
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=<repoid> ...

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 <repoid>
or
subscription-manager repos --disable=<repoid>

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=<repoid>.skip_if_unavailable=true

failed to retrieve repodata/repomd.xml from cloudlinux-x86_64-server-7
error was [Errno 14] HTTPS Error 301 - Moved Permanently

Need your help soon. Thanks.

*WHM server using cloudlinux 7
*WHM version is 110

William Del Piero cPanel Staff

October 22, 2025 13:34

Hi,

It looks like one of the repositories is failing and may be blocking updates. To help investigate, could you please run the following command and share the output?

yum repolist

This will allow me to check for any custom or misconfigured repositories that might be causing the issue.

Thanks!

dhanyg

October 24, 2025 01:08

Hi, I finally disabled rnhplugin, then did a clean all and makechace. Now that the issue has been resolved. Thanks.

October 24, 2025 14:06

Thank you for keeping us updated — I'm glad to hear the issue has been resolved! Please don’t hesitate to reach out if anything else comes up.

HTTPS Error 301 - Moved Permanently When Performing Whm cPanel Update

Comments

Didn't find what you were looking for?