# Problem with python3-pyOpenSSL

**URL:** <https://forums.rockylinux.org/t/problem-with-python3-pyopenssl/20937>\
**Category:** Rocky Linux Help & Support\
**Tags:** rocky-linux-10\
**Created:** [November 11, 2026, 11:46am UTC](https://forums.rockylinux.org/t/problem-with-python3-pyopenssl/20937 "2026-11-11T11:46:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![doublem](https://avatars.discourse-cdn.com/v4/letter/d/ccd318/32.png) [@doublem](https://forums.rockylinux.org/u/doublem)\
**Post date:** [November 11, 2026, 11:46am UTC](https://forums.rockylinux.org/t/problem-with-python3-pyopenssl/20937/1 "2026-11-11T11:46:53Z")

</div>

This has been happening over the last couple of days on two of my systems. I can’t find a workaround (in ai/google)

#yum update --refresh  
Error:  
Problem: cannot install the best update candidate for package python3-pyOpenSSL-25.0.0-1.el10\_1.noarch  
-nothing provides (python3.12dist(cryptography) \< 50~~ with python3.12dist(cryptography) \>= 49) needed by python3-pyOpenSSL-26.3.0-1.el10\_3.noarch from epel  
(try to add ‘–skip-broken’ to skip uninstallable packages or ‘–nobest’ to use not only best candidate packages)

#rpm -qa |grep -i epel  
epel-release-10-8.el10\_2.noarch  
#cat /etc/redhat-release  
Rocky Linux release 10.2 (Red Quartz)

---

<div class="post-metadata">

**Author:** ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)\
**Post date:** [November 11, 2026, 12:04pm UTC](https://forums.rockylinux.org/t/problem-with-python3-pyopenssl/20937/2 "2026-11-11T12:04:07Z")

</div>

RHEL 9.9 and 10.3 have just been released, and EPEL is now at that release. Until Rocky 9.9 and 10.3 is released, this problem will exist.

Easiest, just disable EPEL repository temporarily. Or just wait a few days until the new Rocky release is published.

---

<div class="post-metadata">

**Author:** ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)\
**Post date:** [November 11, 2026, 2:22pm UTC](https://forums.rockylinux.org/t/problem-with-python3-pyopenssl/20937/3 "2026-11-11T14:22:26Z")

</div>

> [@iwalker](#):
>
> Easiest, just disable EPEL repository temporarily. Or just wait a few days until the new Rocky release is published.

These.

With Rocky 10 one can try:

```bash
dnf --releasever=10.2 up --refresh

```

as Rocky’s mirrors should resolve that to the current Rocky 10 repos and  
EPEL’s mirror’s resolve to the copy of EPEL that was built for el10\_2.

(`yum` is mere symlink to `dnf` – they are same command)

* * *

Note also that next to no new packages will enter the current Rocky 10 repos  
now that RHEL 10.3 has been released – all effort is in releasing 10.3 for Rocky 10.

The `--releasever=10.2` will naturally cause trouble once 10.3 is released for Rocky.

* * *

There is only one version of EPEL for 9, so there the `releasever` does not help.