Closed
Bug 160888
Opened 23 years ago
Closed 23 years ago
Error message "Error Code: -8174"
Categories
(Core Graveyard :: Security: UI, defect, P2)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
psm2.4
People
(Reporter: garyb, Assigned: KaiE)
References
()
Details
Hi,
I am having a login problem on Sourceforge every time I enter my user& pass the
page just returns to the login saying I must have cookies enabled, but they
already are.
This may be related to the following problem: Every time I try to load any SSL
page on Sourceforge, I get an error panel from Mozilla 1.0 saying,
"There is a problem with your certificate database. Error Code: -8174"
This panel appears from 1 to 3 times on each page load. It occurs whether I'm
logged in or not.
This problem occurs on Linux, Mac and PC, and using two different ISPs.
Therefore it appears to be related to an interaction between Sourceforge and my
installation of Mozilla.
I have been unable to find any information on this Mozilla error message, so I'm
posting it as a possible bug although it could be a configuration issue or
something else.
Comment 1•23 years ago
|
||
Changed product to PSM for investigation.
Assignee: wtc → ssaux
Component: Build → Client Library
Product: NSS → PSM
QA Contact: wtc → junruh
Comment 2•23 years ago
|
||
Reporter, can you try setting up a new profile? Your certificate DB may be
corrupted.
| Assignee | ||
Comment 3•23 years ago
|
||
Gary, in addition to the new profile test, do you have FIPS or OCSP enabled in
your current profile?
Comment 4•23 years ago
|
||
kai.
This looks like a corrupted db. If the user doesn't reply in a few days we
should close it.
Assignee: ssaux → kaie
Priority: -- → P2
Target Milestone: --- → 2.4
Comment 5•23 years ago
|
||
WFM
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
| Reporter | ||
Comment 6•23 years ago
|
||
I just returned from a trip, sorry for the delay. I'll be able to take a look tomorrow. I figured it was a corrupted db myself, but (at least on PC) couldn't figure out how to uncorrupt it (short of completely deleting my user profile) nor any docs related to the error message. I'll followup either tomorrow or next week. Suggestions on fixing are welcome.
Updated•9 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•