Closed Bug 232643 Opened 22 years ago Closed 22 years ago

error establishing an encrypted connection to ... error code: -5981

Categories

(Firefox :: General, defect)

x86
Linux
defect
Not set
major

Tracking

()

RESOLVED INVALID

People

(Reporter: arvindvenkataramani, Assigned: bugzilla)

References

()

Details

User-Agent: Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007 Firebird/0.7 error establishing an encrypted connection to ... error code: -5981 this error appears whenever i try to access any secure http site. i am using firebird from behind a firewall and with proxies. however i use mozilla 1.5 with the same settings and do not face problems. build 0.6.1 of firebird used to work just fine Reproducible: Always Steps to Reproduce: 1. find a sitename that uses secure http (https://...) 2. type in the address bar, and go 3. watch as an error pops up Actual Results: got an error message stating "error establishing an encrypted connection to ... error code: -5981". firebird then refuses to load the page Expected Results: been able to open a secure http connection using SSL
*** Bug 232644 has been marked as a duplicate of this bug. ***
WFM Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7a) Gecko/20040129 Firebird/0.8.0+ Can you try with the latest nightly and a new profile? (http://texturizer.net/firebird/bugs.html#s1)
(In reply to comment #2) > WFM Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7a) Gecko/20040129 > Firebird/0.8.0+ > > Can you try with the latest nightly and a new profile? > (http://texturizer.net/firebird/bugs.html#s1) > tried it: and the problem seemed to go away. upn installing my usual set of extensions the problem returned... i think the bug arises upon installing either all-in-one-gestures or quickmanager extensions
Marking invalid. Bugs that only occur when an extension is installed is a bug with the extension, not Firebird itself. If you can isolate which extension(s) it is that cause the problem (it could be a combination of two extensions), I recommend you contact the creator of the problem extension(s) with a bug report.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.