I'm pretty happily using dnf5 on my fedora 38. It's both a new library for dependency resolution and a new frontend, replacing dnf/libdnf (though nearly completely drop-in compatible with the CLI of dnf). It's much faster at doing things like searching the package database for words, so that's refreshing. Speaking of refreshing: Can I configure dnf5 to download metadata from different remote repositories (Fedora 38, Fedora 38, updates, Fedora 38 openh264, Fedora 38 nonfree updates, rpm fusion updates, rpm fusion non-free updates …) in parallel?

On AIX 7.2 had installed dnf system through https://public.dhe.ibm.com/aix/freeSoftware/aixtoolbox/ezinstall/ppc/dnf_aixtoolbox.sh I need install rust but, when i try do it i got:

bash-5.2# dnf install rust
Last metadata expiration check: 1 day, 4:00:30 ago on Tue Jul 22 04:31:45 EDT 2025.
Error: 
 Problem: package rust-1.86.0-250527.ppc requires rust1.86 >= 1.86.0, but none of the providers can be installed
  - cannot install the best candidate for the job
  - nothing provides libunwind.a(libunwind.so.1) needed by rust1.86-1.86.0-250516.ppc
  - nothing provides libc++.a(libc++.so.1) needed by rust1.86-1.86.0-250516.ppc
  - nothing provides libc++abi.a(libc++abi.so.1) needed by rust1.86-1.86.0-250516.ppc
  - nothing provides libunwind.a(libunwind.so.1) needed by rust1.86-1.86.0-250527.ppc
  - nothing provides libc++.a(libc++.so.1) needed by rust1.86-1.86.0-250527.ppc
  - nothing provides libc++abi.a(libc++abi.so.1) needed by rust1.86-1.86.0-250527.ppc
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

Thanks in advance for any help

How a protected package can be removed using microdnf package manager? When running docker container almalinux/9-minimal (or redhat/ubi9-minimal) like

podman run -it --rm almalinux/9-minimal

and inside the container

microdnf install -y dnf && microdnf remove -y dnf

the latter command fails with

error: Could not depsolve transaction; 1 problem detected:
 Problem: The operation would result in removing the following protected packages: dnf

Is there a way to list the packages that were updated with $ sudo dnf --refresh upgrade from the command line? I cannot seem to find any suitable option in the man page for DNF.

I know how to install a specific version or how to exclude a package from transactions, but I want to mark a specific version of package to be skipped. Is that possible? Background: gdk-pixbuf2-2.42.9 has a known issue, which is already [fixed in upstream](https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/216) . It's just a matter of time, when that update will become available in fedora 36. Anyway, I downgraded that package and still want to dnf update my machine, without remembering: hey, exclude that package - or worse: exclude it using dnf.conf and forget about it.

I have a new Centos 8 installation and am trying to use dnf to install the packages I need. Company rules (and common sense, honestly) is that any outgoing traffic needs to be done over HTTPS. However running this command: dnf module list fails because it is trying to connect to http://mirrorlist.centos.org/ ?... Is there any way to get dnf to use https instead?

###### Problem 1:

installed package libcurl-minimal-8.9.1-2.fc41.x86_64 conflicts with libcurl(x86-64) provided by libcurl-8.9.1-2.fc41.x86_64 from fedora
  - package dnf5-plugin-automatic-5.2.6.2-1.fc41.x86_64 from fedora requires libcurl-full(x86-64), but none of the providers can be installed
  - cannot install the best update candidate for package libcurl-minimal-8.9.1-2.fc41.x86_64
  - cannot install the best update candidate for package dnf-automatic-4.21.1-1.fc41.noarch
 Problem 2: problem with installed package
  - installed package libcurl-minimal-8.9.1-2.fc41.x86_64 conflicts with libcurl(x86-64) provided by libcurl-8.9.1-2.fc41.x86_64 from fedora
  - package libcurl-minimal-8.9.1-2.fc41.x86_64 from fedora conflicts with libcurl(x86-64) provided by libcurl-8.9.1-2.fc41.x86_64 from fedora
  - package dnf5-plugin-automatic-5.2.6.2-1.fc41.x86_64 from fedora requires libcurl-full(x86-64), but none of the providers can be installed
  - problem with installed package
  - installed package dnf-automatic-4.21.1-1.fc41.noarch requires python3-dnf = 4.21.1-1.fc41, but none of the providers can be installed
  - package dnf-automatic-4.21.1-1.fc41.noarch from fedora requires python3-dnf = 4.21.1-1.fc41, but none of the providers can be installed
  - cannot install both python3-dnf-4.21.1-2.fc41.noarch from updates and python3-dnf-4.21.1-1.fc41.noarch from @System
  - cannot install both python3-dnf-4.21.1-2.fc41.noarch from updates and python3-dnf-4.21.1-1.fc41.noarch from fedora
  - cannot install the best update candidate for package python3-dnf-4.21.1-1.fc41.noarch

###### Update: The issue with the repositories was resolved by Dnfdragora. I set the program on "To Update" and two selections were identified: update of Python3 and libcurl-minimal. The first was updated and the second removed from the system. I performed a CLI dnf-update check which showed no further conflicts. Hope this helps others.

After updating my Fedora system to Fedora 41 it is using DNF in version 5 which is a replacement of DNF 4 that works differently in some situations. I noticed that the command dnf repository-packages ancient-repo remove no longer works. This command was useful for removing all packages installed from a specific repository (ancient-repo in this case). For example, with DNF 4, I could run:

dnf repository-packages ancient-repo remove

But in DNF 5, this results in an error:

Unknown argument "repository-packages" for command "dnf5". Add "--help" for more information about the arguments.
It could be a command provided by a plugin, try: dnf5 install 'dnf5-command(repository-packages)'

How can I achieve the same functionality with DNF 5? **Is there an alternative command or a workaround to remove all packages installed from a specific repository?**

Using yum there was the chance that a transaction wasn't succesful, so that the next operation was blocked and the message told me to run yum-complete-transaction to fix the issue. What about dnf? Is there a way, maybe using a command like

-sh
dnf history info last | grep Return-Code    : Success

to understand if there are uncompleted transaction or event that requires attention and fix?

I've got a question about yum. When I upgrade my system using dnf, it downloads packages from the Web. Can I set dnf configuration so that I could save rpm files for later use, with the same system but without Web connection?

in **rhel-8.10** a dnf check reports audit-libs-3.0.7-5.el8.x86_64 is a duplicate with audit-libs-3.1.2-1.el8.x86_64 bash-4.4.20-4.el8_6.x86_64 is a duplicate with bash-4.4.20-5.el8.x86_64 elfutils-libelf-0.189-3.el8.x86_64 is a duplicate with elfutils-libelf-0.190-2.el8.x86_64 gdk-pixbuf2-2.36.12-5.el8.x86_64 is a duplicate with gdk-pixbuf2-2.36.12-6.el8_10.x86_64 gmp-1:6.1.2-10.el8.x86_64 is a duplicate with gmp-1:6.1.2-11.el8.x86_64 gpgme-1.13.1-11.el8.x86_64 is a duplicate with gpgme-1.13.1-12.el8.x86_64 iproute-6.2.0-5.el8_9.x86_64 is a duplicate with iproute-6.2.0-6.el8_10.x86_64 kmod-25-19.el8.x86_64 is a duplicate with kmod-25-20.el8.x86_64 kmod-libs-25-19.el8.x86_64 is a duplicate with kmod-libs-25-20.el8.x86_64 libacl-2.2.53-1.el8.x86_64 is a duplicate with libacl-2.2.53-3.el8.x86_64 libblkid-2.32.1-44.el8_9.1.x86_64 is a duplicate with libblkid-2.32.1-46.el8.x86_64 libblockdev-utils-2.28-4.el8.x86_64 is a duplicate with libblockdev-utils-2.28-6.el8.x86_64 libmount-2.32.1-44.el8_9.1.x86_64 is a duplicate with libmount-2.32.1-46.el8.x86_64 libtalloc-2.4.0-3.el8.x86_64 is a duplicate with libtalloc-2.4.1-0.el8.x86_64 libtdb-1.4.8-3.el8.x86_64 is a duplicate with libtdb-1.4.9-0.el8.x86_64 libtevent-0.14.1-3.el8.x86_64 is a duplicate with libtevent-0.16.0-0.el8.x86_64 libuuid-2.32.1-44.el8_9.1.x86_64 is a duplicate with libuuid-2.32.1-46.el8.x86_64 p11-kit-0.23.22-1.el8.x86_64 is a duplicate with p11-kit-0.23.22-2.el8.x86_64 pixman-0.38.4-3.el8_9.x86_64 is a duplicate with pixman-0.38.4-4.el8.x86_64 shadow-utils-2:4.6-19.el8.x86_64 is a duplicate with shadow-utils-2:4.6-22.el8.x86_64 shared-mime-info-1.9-3.el8.x86_64 is a duplicate with shared-mime-info-1.9-4.el8.x86_64 Error: Check discovered 21 problem(s) doing dnf distro-sync as mentioned in a fedora post results in Updating Subscription Management repositories. Last metadata expiration check: 1:05:41 ago on Thu 15 May 2025 09:55:29 AM EDT. Dependencies resolved. Nothing to do. Complete! It does not fix things, re-running the check reports the same 21 problems. How can these *21 problems* be fixed?

We manage a server farm of RHEL 9 machines via Red Hat Satellite and Ansible Tower (AWX). On some machines the dnf versionlock command outputs packages **"foo"** and **"bar"** as versionlocked. Hovever, our Ansible configuration for these machines (using module community.general.yum_versionlock -- not community.general.dnf_versionlock as we had yum-based old RHEL servers in the past) is set to versionlock the packages **"foo"** and **"quux"**. So, where are all the places where version-locked packages are defined? In particular, is there some setting in Satellite, perhaps related to Repos/Products/Hosts?

On several of my RHEL 9 machines managed by Ansible, the java-1.8.0-openjdk package is versionlocked: - name: java-1.8.0-openjdk-1:1.8.0.402.b06-2.el9 state: present However, Ansible tries to update it anyway, and this causes the Ansible Tower job to fail. Below are the corresponding commands when run via Bash shell. [myhost root ~]# dnf versionlock Updating Subscription Management repositories. rhel9flexnet 105 kB/s | 2.0 kB 00:00 rhel9checkmkagent 113 kB/s | 2.0 kB 00:00 rhel9elk8 97 kB/s | 1.7 kB 00:00 rhel9epel 127 kB/s | 2.3 kB 00:00 java-1.8.0-openjdk-1:1.8.0.402.b06-2.el9.* [myhost root ~]# dnf update Updating Subscription Management repositories. rhel9flexnet 112 kB/s | 2.0 kB 00:00 rhel9checkmkagent 122 kB/s | 2.0 kB 00:00 rhel9elk8 108 kB/s | 1.7 kB 00:00 rhel9epel 133 kB/s | 2.3 kB 00:00 Error: Problem: package java-1.8.0-openjdk-1:1.8.0.402.b06-2.el9.x86_64 from @System requires java-1.8.0-openjdk-headless(x86-64) = 1:1.8.0.402.b06-2.el9, but none of the providers can be installed - cannot install both java-1.8.0-openjdk-headless-1:1.8.0.442.b06-2.el9.x86_64 from rhel-9-for-x86_64-appstream-rpms and java-1.8.0-openjdk-headless-1:1.8.0.402.b06-2.el9.x86_64 from @System - cannot install both java-1.8.0-openjdk-headless-1:1.8.0.442.b06-2.el9.x86_64 from rhel-9-for-x86_64-appstream-rpms and java-1.8.0-openjdk-headless-1:1.8.0.402.b06-2.el9.x86_64 from rhel-9-for-x86_64-appstream-rpms - cannot install the best update candidate for package java-1.8.0-openjdk-headless-1:1.8.0.402.b06-2.el9.x86_64 - cannot install the best update candidate for package java-1.8.0-openjdk-1:1.8.0.402.b06-2.el9.x86_64 (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) [myhost root ~]# dnf list installed java-1.8.0-* Updating Subscription Management repositories. Installed Packages java-1.8.0-openjdk.x86_64 1:1.8.0.402.b06-2.el9 @rhel-9-for-x86_64-appstream-rpms java-1.8.0-openjdk-headless.x86_64 1:1.8.0.402.b06-2.el9 @rhel-9-for-x86_64-appstream-rpms [myhost root ~]# dnf list available java-1.8.0-* Updating Subscription Management repositories. rhel9flexnet 111 kB/s | 2.0 kB 00:00 rhel9checkmkagent 122 kB/s | 2.0 kB 00:00 rhel9elk8 99 kB/s | 1.7 kB 00:00 rhel9epel 130 kB/s | 2.3 kB 00:00 Available Packages java-1.8.0-openjdk.x86_64 1:1.8.0.442.b06-2.el9 rhel-9-for-x86_64-appstream-rpms java-1.8.0-openjdk-demo.x86_64 1:1.8.0.442.b06-2.el9 rhel-9-for-x86_64-appstream-rpms java-1.8.0-openjdk-devel.x86_64 1:1.8.0.442.b06-2.el9 rhel-9-for-x86_64-appstream-rpms java-1.8.0-openjdk-headless.x86_64 1:1.8.0.442.b06-2.el9 rhel-9-for-x86_64-appstream-rpms java-1.8.0-openjdk-javadoc.noarch 1:1.8.0.442.b06-2.el9 rhel-9-for-x86_64-appstream-rpms java-1.8.0-openjdk-javadoc-zip.noarch 1:1.8.0.442.b06-2.el9 rhel-9-for-x86_64-appstream-rpms java-1.8.0-openjdk-src.x86_64 1:1.8.0.442.b06-2.el9 rhel-9-for-x86_64-appstream-rpms On a shell I would just run dnf update --exclude=java-1.8.0-* to bypass the problem and get a successful update. However, this needs to be done via Ansible playbooks. I am interested to know how would one do that via Ansible (workaround), and especially **why dnf tries to update versionlocked packages** (main issue). ---- EDIT 1 I've modified our update playbook: - name: Update packages yum: name: "{{ packages_name }}" state: latest exclude: "{{ (packages_donotupdate | default([])) | join(',') }}" so to exclude from the update the packages listed in the variable "packages_donotupdate" (if defined), but it does not work -- it does not update any package on the server. (Note: we use the "yum" Ansible module for backward compatibility reasons.)

I am trying to install beeker-studio using the command but it is failing with this error

[1/1] Total                                                                                                                                                                    100% |   1.1 MiB/s | 139.0 MiB |  02m04s
Running transaction
Transaction failed: Rpm transaction failed.
  - file /usr/lib/.build-id/1c/26baeb945b7e2802e2ac040b8e5e44d63ddea2 from install of beekeeper-studio-5.2.1-1.x86_64 conflicts with file from package mongodb-compass-1.46.0-1.el8.x86_64

When I remove MongoDB Compass (GUI) package, it works. When I try to install beekeper-studio with MongoDB Compass GUI installed, the beekeeper installation fails with the same message above. Is it possible to fix the installation and have both packages? I do not wish to delete one just to have the other and would prefer on not having to use the snap/flatpak packages. I am installing beekeeper using dnf after setting up the repo using the provided instructions in their page https://docs.beekeeperstudio.io/installation/linux/#rpm

sudo dnf install beekeeper-studio

My environment

Fedora Linux 42 (Workstation Edition)

Linux: 6.14.2-300.fc42.x86_64

I see that it is an error that happend here and there for some packages, but I didnt find any solution working for me. Everything broke down trying to install Jupyter by dnf install python2-qtconsole python2-jupyter-core, when I found that python2-urllib3 was giving an error trying to install. Now whenever I do: dnf install python2-urllib3, I get: Dependencies resolved. ======================================================================================================================================== Package Arch Version Repository Size ======================================================================================================================================== Installing: python2-urllib3 noarch 1.22-3.fc27 updates 178 k Transaction Summary ======================================================================================================================================== Install 1 Package Total download size: 178 k Installed size: 678 k Is this ok [y/N]: y Downloading Packages: python2-urllib3-1.22-3.fc27.noarch.rpm 78 kB/s | 178 kB 00:02 ---------------------------------------------------------------------------------------------------------------------------------------- Total 53 kB/s | 178 kB 00:03 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Installing : python2-urllib3-1.22-3.fc27.noarch 1/1 Error unpacking rpm package python2-urllib3-1.22-3.fc27.noarch Error unpacking rpm package python2-urllib3-1.22-3.fc27.noarch error: unpacking of archive failed on file /usr/lib/python2.7/site-packages/urllib3/packages/ssl_match_hostname: cpio: File from package already exists as a directory in system python2-urllib3-1.22-3.fc27.noarch was supposed to be installed but is not! Verifying : python2-urllib3-1.22-3.fc27.noarch 1/1 Failed: python2-urllib3.noarch 1.22-3.fc27 Error: Transaction failed I tried all these dnf clean all yum clean all && rpm --rebuilddb package-cleanup --problems rpm -e python3-urllib3-1.22-3.fc27.noarch --nodeps rpm -i python2-urllib3-1.22-3.fc27.noarch.rpm ... and I'm losing ideas fast ...

I have done an update on AlmaLinux 8.6 to AlmaLinux 8.7. I would like to undo the update but it is not letting me. Here's the error message: Error: The following problems occurred while running a transaction: Cannot find rpm nevra "NetworkManager-1:1.36.0-9.el8_6.x86_64". Cannot find rpm nevra "NetworkManager-adsl-1:1.36.0-9.el8_6.x86_64". Cannot find rpm nevra "NetworkManager-bluetooth-1:1.36.0-9.el8_6.x86_64". A simple way of undo would really be nice. Is there a way of backup a state of machine in order to revert easily should something go wrong?

I run AlmaLinux 8.10 with automatic security updates provided by dnf-automatic. Unfortunately the latest kernel did not work for some strange reason and I want to downgrade it one patch-level. I guess I need to disable kernel updates in dnf.conf to keep security updates, but is there more work in GRUB? Anything else?

Recently lambda/dotnet:8 switch over to amazonlinux:2023 instead of amazonlinux:2. As a result I can't install simply the native compilers directly inside the image. Steps: > docker pull public.ecr.aws/lambda/dotnet:8 > docker run --rm --entrypoint bash -it public.ecr.aws/lambda/dotnet:8 bash-5.2# dnf group install -y "Development Tools" This is microdnf, which implements subset of `dnf'. [...] error: Unknown command: 'group' Using: # rpm -q microdnf microdnf-3.8.1-1.amzn2023.0.1.x86_64 Is there a simple way to install plain yum or regular dnf over an existing microdnf setup ? --- For example I cannot simply install yum over the existing microdnf setup: % docker run --rm --entrypoint bash -it public.ecr.aws/lambda/dotnet:8 bash-5.2# dnf install yum Downloading metadata... error: Could not depsolve transaction; 1 problem detected: Problem: problem with installed package microdnf-dnf-3.10.0-2.amzn2023.0.1.x86_64 - package microdnf-dnf-3.10.0-2.amzn2023.0.1.x86_64 from @System conflicts with dnf provided by dnf-4.12.0-2.amzn2023.0.4.noarch from amazonlinux - package microdnf-dnf-3.10.0-2.amzn2023.0.1.x86_64 from amazonlinux conflicts with dnf provided by dnf-4.12.0-2.amzn2023.0.4.noarch from amazonlinux - package microdnf-dnf-3.8.1-1.amzn2023.0.1.x86_64 from amazonlinux conflicts with dnf provided by dnf-4.12.0-2.amzn2023.0.4.noarch from amazonlinux - package yum-4.12.0-2.amzn2023.0.4.noarch from amazonlinux requires dnf = 4.12.0-2.amzn2023.0.4, but none of the providers can be installed - conflicting requests - package yum-4.14.0-1.amzn2023.0.4.noarch from amazonlinux requires dnf = 4.14.0-1.amzn2023.0.4, but none of the providers can be installed - package microdnf-dnf-3.10.0-2.amzn2023.0.1.x86_64 from @System conflicts with dnf provided by dnf-4.14.0-1.amzn2023.0.4.noarch from amazonlinux - package microdnf-dnf-3.10.0-2.amzn2023.0.1.x86_64 from amazonlinux conflicts with dnf provided by dnf-4.14.0-1.amzn2023.0.4.noarch from amazonlinux - package microdnf-dnf-3.8.1-1.amzn2023.0.1.x86_64 from amazonlinux conflicts with dnf provided by dnf-4.14.0-1.amzn2023.0.4.noarch from amazonlinux - package yum-4.14.0-1.amzn2023.0.5.noarch from amazonlinux requires dnf = 4.14.0-1.amzn2023.0.5, but none of the providers can be installed - package microdnf-dnf-3.10.0-2.amzn2023.0.1.x86_64 from @System conflicts with dnf provided by dnf-4.14.0-1.amzn2023.0.5.noarch from amazonlinux - package microdnf-dnf-3.10.0-2.amzn2023.0.1.x86_64 from amazonlinux conflicts with dnf provided by dnf-4.14.0-1.amzn2023.0.5.noarch from amazonlinux - package microdnf-dnf-3.8.1-1.amzn2023.0.1.x86_64 from amazonlinux conflicts with dnf provided by dnf-4.14.0-1.amzn2023.0.5.noarch from amazonlinux Which is identical to: bash-5.2# microdnf install yum error: Could not depsolve transaction; 1 problem detected: Problem: problem with installed package microdnf-dnf-3.10.0-2.amzn2023.0.1.x86_64 - package microdnf-dnf-3.10.0-2.amzn2023.0.1.x86_64 from @System conflicts with dnf provided by dnf-4.12.0-2.amzn2023.0.4.noarch from amazonlinux - package microdnf-dnf-3.10.0-2.amzn2023.0.1.x86_64 from amazonlinux conflicts with dnf provided by dnf-4.12.0-2.amzn2023.0.4.noarch from amazonlinux - package microdnf-dnf-3.8.1-1.amzn2023.0.1.x86_64 from amazonlinux conflicts with dnf provided by dnf-4.12.0-2.amzn2023.0.4.noarch from amazonlinux - package yum-4.12.0-2.amzn2023.0.4.noarch from amazonlinux requires dnf = 4.12.0-2.amzn2023.0.4, but none of the providers can be installed - conflicting requests - package yum-4.14.0-1.amzn2023.0.4.noarch from amazonlinux requires dnf = 4.14.0-1.amzn2023.0.4, but none of the providers can be installed - package microdnf-dnf-3.10.0-2.amzn2023.0.1.x86_64 from @System conflicts with dnf provided by dnf-4.14.0-1.amzn2023.0.4.noarch from amazonlinux - package microdnf-dnf-3.10.0-2.amzn2023.0.1.x86_64 from amazonlinux conflicts with dnf provided by dnf-4.14.0-1.amzn2023.0.4.noarch from amazonlinux - package microdnf-dnf-3.8.1-1.amzn2023.0.1.x86_64 from amazonlinux conflicts with dnf provided by dnf-4.14.0-1.amzn2023.0.4.noarch from amazonlinux - package yum-4.14.0-1.amzn2023.0.5.noarch from amazonlinux requires dnf = 4.14.0-1.amzn2023.0.5, but none of the providers can be installed - package microdnf-dnf-3.10.0-2.amzn2023.0.1.x86_64 from @System conflicts with dnf provided by dnf-4.14.0-1.amzn2023.0.5.noarch from amazonlinux - package microdnf-dnf-3.10.0-2.amzn2023.0.1.x86_64 from amazonlinux conflicts with dnf provided by dnf-4.14.0-1.amzn2023.0.5.noarch from amazonlinux - package microdnf-dnf-3.8.1-1.amzn2023.0.1.x86_64 from amazonlinux conflicts with dnf provided by dnf-4.14.0-1.amzn2023.0.5.noarch from amazonlinux

I want to install an older version of package , and when I use dnf it only shows the current version of the package . Is there any way to install an older versions using dnf ?

## RHEL 9 VM Exported from Internal Network Cannot Verify SSL Certificates for Updates I'm running into a major issue with a Red Hat Enterprise Linux 9 VM that was originally exported from my company's internal infrastructure. I'm now using this VM on a standard public internet connection, and I'm unable to perform basic operations like dnf update due to SSL certificate verification errors. --- ### **Problem** Running dnf update results in the following:

Updating Subscription Management repositories.
This system is registered with an entitlement server, but is not receiving updates.

Red Hat Enterprise Linux 9 for x86_64 - BaseOS (RPMs)       
Errors during downloading metadata for repository 'rhel-9-for-x86_64-baseos-rpms':
  - Curl error (77): Problem with the SSL CA cert (path? access rights?) for https://cdn.redhat.com/content/dist/rhel9/9/x86_64/baseos/os/repodata/repomd.xml  
    [error setting certificate file: /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem]
Error: Failed to download metadata for repo 'rhel-9-for-x86_64-baseos-rpms': 
  Cannot download repomd.xml: Curl error (77): Problem with the SSL CA cert (path? access rights?)

Trying to run subscription-manager identity shows:

Unable to verify server's identity: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get issuer certificate (_ssl.c:1147)

--- ### **What I’ve Tried** 1. **Checked System Time** - Verified with date and timedatectl. Time *seems* off, which may be contributing to the SSL issue. - Tried enabling NTP with:

systemctl enable chronyd --now

But it fails, saying:

Failed to enable unit: Unit file chronyd.service does not exist.

- I cannot install chrony because dnf is broken due to the SSL certificate issue. 2. **Checked CA Certificate Files** - Ran:

find /etc/pki -type f \( -name "*.crt" -o -name "*.cert" \)

**No certificate files were found.** 3. **Compared to Fresh RHEL 9 Install** - A clean RHEL 9 VM (registered with the same Red Hat account) works fine and has many cert files in /etc/pki/ca-trust/. 4. **Reinstall CA Certificates** - Ran:

sudo dnf reinstall ca-certificates
     sudo update-ca-trust extract

But no certs appeared, and the issue remains. 5. **Checked Proxy Config** - No proxies in /etc/environment, /etc/profile, shell dotfiles, or subscription-manager:

subscription-manager config --remove=server.proxy_hostname
     subscription-manager config --remove=server.proxy_port

--- ### **Context** This VM was managed internally and likely used internal CAs or custom proxy settings. Now that it’s on a public network, it appears unable to verify standard SSL certificates, and it’s missing all cert files in /etc/pki. --- ### **Question** What could explain the complete absence of certificate files in /etc/pki, and how can I restore them without access to dnf or a working package manager? Is there a manual way to recover basic system certificates or sync time so that SSL works again? Or is this VM likely too locked into internal infrastructure to be recovered for public use? Any help would be greatly appreciated! (I really need to fix this issue they blame me)