I have multiple systems running AlmaLinux 9 (x86_64) that have the EPEL repo enabled.
All of them seem to give an SSL error when performing dnf upgrade --refresh:
dnf upgrade --refresh
# dnf upgrade --refresh AlmaLinux 9 - AppStream 18 kB/s | 4.2 kB 00:00 AlmaLinux 9 - BaseOS 17 kB/s | 3.8 kB 00:00 AlmaLinux 9 - Extras 14 kB/s | 3.3 kB 00:00 Extra Packages for Enterprise Linux 9 - x86_64 0.0 B/s | 0 B 00:00 Errors during downloading metadata for repository 'epel': - Curl error (35): SSL connect error for https://mirrors.fedoraproject.org/metalink?repo=epel-9&arch=x86_64&infra=$infra&content=$contentdir [error:0A0000C6:SSL routines::packet length too long] Error: Failed to download metadata for repo 'epel': Cannot prepare internal mirrorlist: Curl error (35): SSL connect error for https://mirrors.fedoraproject.org/metalink?repo=epel-9&arch=x86_64&infra=$infra&content=$contentdir [error:0A0000C6:SSL routines::packet length too long]
Apologies if this is the wrong place to report this...
Can you run 'curl -vv' on that url and provide the output?
Now I get:
# dnf upgrade --refresh AlmaLinux 9 - AppStream 18 kB/s | 4.2 kB 00:00 AlmaLinux 9 - BaseOS 17 kB/s | 3.8 kB 00:00 AlmaLinux 9 - Extras 13 kB/s | 3.3 kB 00:00 Extra Packages for Enterprise Linux 9 - x86_64 41 B/s | 272 B 00:06 Errors during downloading metadata for repository 'epel': - Status code: 404 for https://mirrors.fedoraproject.org/metalink?repo=epel-9&arch=x86_64&infra=$infra&content=$contentdir (IP: 2600:1f14:fad:5c02:eb33:e938:35cc:965b) Error: Failed to download metadata for repo 'epel': Cannot prepare internal mirrorlist: Status code: 404 for https://mirrors.fedoraproject.org/metalink?repo=epel-9&arch=x86_64&infra=$infra&content=$contentdir (IP: 2600:1f14:fad:5c02:eb33:e938:35cc:965b)
curl output attached; but it seems to succeed sometimes as well...
Here's curl output that gives a 404: (attached)
found it. It should be fixed in a few minutes.
I was hitting this too and now it works for me.
What was the fix?
There was a proxy that was supposed to be out for reinstall... but it wasn't fully removed. ;(
Sorry about that.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)