The guide explains how to add the CRB (PowerTools) repository on CentOS 9 Stream, install the compat‑libstdc++-33 compatibility library, and then download the desired Opera RPM—stable, beta, or developer—from https://rpm.opera.com/desktop/. Using dnf install -y ./opera‑*.rpm resolves any additional dependencies (e.g., pango) and places the browser’s repo file under /etc/yum.repos.d/ so future updates stay on the chosen channel. After installation you confirm it works with opera --version, and if you later want to switch channels you simply remove the current package, fetch the new RPM for the other track, and reinstall; dnf will keep the selected stream automatically. The article also notes common issues such as missing GPG keys (fixed by importing Opera’s key) or SELinux denials (temporarily disabled with setenforce 0 or addressed via a proper policy).

Install Opera Browser on CentOS 9 Stream – Stable, Beta or Developer

You’re about to get Opera running on a CentOS 9 Stream box without chasing dead‑end repos. The guide shows the exact terminal commands for the stable build, and how to switch to the beta or developer channel if you like living on the edge.

Grab the right RPM package

Opera ships its own RPMs instead of relying on the default dnf repositories. I’ve installed it a few times on RHEL‑derived systems; the only hiccup was an old libstdc++ that the official package expects. The fix is to pull in the newer compatibility libs from the PowerTools (now called CRB) repo.

# Enable the CRB repository – needed for newer C++ runtime libraries
sudo dnf config-manager --set-enabled crb

# Install the compatibility libstdc++
sudo dnf install -y compat-libstdc++-33

Now download whichever channel you prefer. The URLs are predictable:

• Stable: https://rpm.opera.com/desktop/opera-stable.rpm
• Beta: https://rpm.opera.com/desktop/opera-beta.rpm
• Developer (unstable): https://rpm.opera.com/desktop/opera-developer.rpm

# Example – get the stable build
curl -L -o opera-stable.rpm https://rpm.opera.com/desktop/opera-stable.rpm

Downloading with curl lets you see the progress bar and avoid a GUI download manager that might not even exist on a headless server.

Install the package

sudo dnf install -y ./opera-stable.rpm

The -y flag skips the “are you sure?” prompt, which is handy when you’re scripting the whole thing. DNF will resolve dependencies automatically; if it complains about missing libpangocairo‑1.0.so.0, just run:

sudo dnf install -y pango

That library shows up often after a kernel upgrade because the older Opera RPM was built against an earlier version of Pango.

Verify the installation

opera --version

You should see something like Opera 97.0.4719.98 (Stable). If you get “command not found,” double‑check that /usr/bin is in your $PATH; on a minimal CentOS install it sometimes isn’t.

Switch channels later

If you start with stable but want to test new features, just replace the RPM:

# Remove the current version first (optional)
sudo dnf remove -y opera

# Pull the beta package
curl -L -o opera-beta.rpm https://rpm.opera.com/desktop/opera-beta.rpm
sudo dnf install -y ./opera-beta.rpm

Opera’s own repo file (/etc/yum.repos.d/opera.repo) will stay in place, so future dnf update calls will keep you on the selected channel automatically.

Common pitfalls I’ve hit

• Missing GPG key – The first time you install from Opera’s repo, dnf warns about an unsigned package. Run sudo rpm --import https://rpm.opera.com/archive.key and retry.
• SELinux blocks the binary – On a locked‑down server SELinux may deny execution. A quick setenforce 0 (or better, add a proper policy) will get you past it for testing.

That’s all there is to it. Once Opera is on your system you can launch it from the desktop environment or run opera & over SSH with X forwarding.

Enjoy the slick interface and built‑in VPN—just don’t expect it to replace a full‑blown development workstation.