The guide takes you through installing Redis on Fedora 35, 36, or 37, beginning with a quick check of the release version and optionally enabling EPEL to pull the latest 7.x build from the community repository. It then shows how to install Redis via DNF, start and enable the systemd service, and run redis‑cli ping to confirm the server is listening on port 6379. Troubleshooting tips cover common issues such as firewall rules or SELinux blocks, with logs accessible through journalctl if the ping fails. Finally, readers are offered the option to edit /etc/redis.conf for persistence settings and other tweaks before restarting the service to complete the setup.

How to Install Redis on Fedora 37/36/35

You’ll learn how to get a fresh copy of Redis up and running on Fedora 37, 36 or 35 in under ten minutes, plus a quick sanity check so you know it’s actually listening for connections.

Verify your Fedora version

cat /etc/fedora-release

Make sure the output shows 35‑37. If you’re on an older release, consider upgrading first; Redis from the official repos is only built for those three versions. Knowing your exact distro prevents a lot of “repo not found” headaches later.

Enable EPEL (Extra Packages for Enterprise Linux)

Redis sits in Fedora’s default repo but if you want the latest 7.x build, grab it from EPEL:

sudo dnf install -y epel-release

Why this matters: without EPEL you’ll get an older Redis 5 that lacks many performance tweaks. I’ve seen users try to start Redis after a bad driver update and hit “module not found” errors because they were on the stale distro repo.

Install Redis

sudo dnf install -y redis

That’s it—dnf pulls in all dependencies, including jemalloc, which gives you better memory usage under heavy load. If you’re curious about what got installed, run:

rpm -q --whatprovides redis | grep jemalloc

Start and enable the service

sudo systemctl start redis
sudo systemctl enable redis

Starting it now lets you check that it’s listening on port 6379. Enabling it will make sure it comes back after a reboot—useful if you’re running a small dev server.

Quick sanity test

redis-cli ping

You should see PONG. If not, look at the logs:

journalctl -u redis.service | tail -n 20

Common pitfalls: a mis‑configured firewall (use firewall-cmd --add-service=redis), or SELinux blocking socket creation. Adjust those if you hit an error.

Optional: tweak configuration

The main config lives in /etc/redis.conf. If you want to change the data directory or enable persistence, edit that file and then restart:

sudo systemctl restart redis

I’ve patched this file a handful of times on Fedora 36; the default save directives are fine for dev, but if you’re running production you’ll probably want to set appendonly yes.

You’re now running Redis on Fedora. Drop in your scripts or applications and watch it start caching like a champ.