The ISOs are inaccessible

Ask Fedora
, , ,
1

Context

Due to bugzilla.redhat.com/show_bug.cgi?id=2366462#c14, I intended to mark it as UPSTREAM, until I noticed bugzilla.mozilla.org/show_bug.cgi?id=1870422#c8, which makes me wonder why I closed it as WORKSFORME, if the problem reproduces elsewhere, too. Consequently, I intended to re-download https://download.fedoraproject.org/pub/fedora/linux/releases/44/KDE/x86_64/iso/Fedora-KDE-Desktop-Live-44-1.7.x86_64.iso, except that it invokes about:neterror?e=nssFailure2&u=https%3A//download.fedoraproject.org/pub/fedora/linux/releases/44/KDE/x86_64/iso/Fedora-KDE-Desktop-Live-44-1.7.x86_64.iso&c=UTF-8&d=%20&a=. However, I observe:

What The Problem Is

1278×718 62.5 KB
[1] [2]

More uncommonly, I also observe:

1278×718 89.2 KB

  1. view-source:data:text/html;charset=utf-8,%3Cp%20data-l10n-id%3D%22fp-cert-error-code%22%20data-l10n-args%3D%22%7B%26quot%3Berror%26quot%3B%3A%20%26quot%3BSSL_ERROR_RX_RECORD_TOO_LONG%26quot%3B%7D%22%3EError%20Code%3A%20%EF%B7%90SSL_ERROR_RX_RECORD_TOO_LONG%EF%B7%AF%3C%2Fp%3E#:~:text=SSL_ERROR_RX_RECORD_TOO_LONG

    ↩︎

  2. powerusers.codidact.com/posts/294530/296241 ↩︎

2

The ISO downloads fine for me from here on Firefox and Qutebrowser:

$ rpm -qa \*firefox\* \*qutebrowser\* \*qtwebengine\*
qt6-qtwebengine-6.11.1-1.fc44.x86_64
qt6-qtwebengine-devtools-6.11.1-1.fc44.x86_64
qutebrowser-3.7.0-2.fc44.noarch
firefox-151.0.3-1.fc44.x86_64
firefox-langpacks-151.0.3-1.fc44.x86_64

So, the issue is perhaps not server side—will be good to have others test it out to confirm too.

3

@ankursinha, they work for me, too, now. It must have been intermittent. I wonder why.

4

Works for me as well

5

download.fedoraproject.org resolves to a different mirrors depending on the geo location of the person clicking the link. It was probably a mirror server that was offline temporarily for whatever reason (e.g. updates).

6

I think the problem is a misconfiguration of the mirror you are getting directed to, see the SSL error code. Just a guess: Firefox is forcing HTTPS, maybe the mirror is responding with unencrypted traffic, or it could be routing issues.