Red Hat Bugzilla – Bug 267841
firefox-184.108.40.206 or newer will not load websites via https
Last modified: 2008-08-02 19:40:35 EDT
Description of problem:
ANY version of firefox newer than 220.127.116.11 will NOT load a website that requires
https. I grabbed every rpm I could find from 18.104.22.168 to the newest 22.214.171.124 and
NONE of them could load any website that required https. 126.96.36.199 does. I'm
fairly certain this is a Fedora specific problem since the same versions of FF
running on XP, FreeBSD and MacOS work just fine on secure sites.
Version-Release number of selected component (if applicable):
firefox-188.8.131.52 or newer
Steps to Reproduce:
1. Open firefox 184.108.40.206 or newer
2. Go to a site requiring https
3. FF says it cannot load the page.
Unexpected response from server
Firefox doesn't know how to communicate with the server.
* Check to make sure your system has the Personal Security Manager installed.
* This might be due to a non-standard configuration on the server.
Load the website, like all prior versions did.
Running FC5 system freshly installed from DVD on a dual-cpu Dell Optiplex SX280.
Is nss getting installed properly?
Yes, I did install the latest nss rpm (which was not included in the ff rpm).
Still can't view any websites via https.
Fedora Core 5 is no longer supported, could you please reproduce this with the
updated version of the currently supported distribution (Fedora 7, 8, or
Rawhide)? If this issue turns out to still be reproducible, please let us know
in this bug report. If after a month's time we have not heard back from you, we
will have to close this bug as CANTFIX.
Setting status to NEEDINFO, and awaiting information from the reporter.
Thanks in advance.
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received feedback to the
information we have requested above, we will assume the problem was not
reproducible, or has been fixed in one of the updates we have released for the
Users who have experienced this problem are encouraged to upgrade to the latest
update of their distribution, and if this issue turns out to still be
reproducible in the latest update, please reopen this bug with additional
Closing as INSUFFICIENT_DATA.