Closed Bug 393706 Opened 17 years ago Closed 17 years ago

Crashreporter always fails to submit crash report

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 390568

People

(Reporter: morac, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a8pre) Gecko/2007082505 Minefield/3.0a8pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a8pre) Gecko/2007082505 Minefield/3.0a8pre

CrashReporter.exe always fails to submit crashes resulting in a "Failed to submit crash report" error.

Using a packet sniffer I checked the URL that the crashes are being submitted to which is https://63.245.209.57/.  Going to the URL in a browser gives an error about a Security Error: Domain Name Mismatch.  

I also see that a connection to crl.xrampsecurity.com is made which returns a list of revoked certificates and once this is received, CrashReporter.exe immediately closes the connection to 63.245.209.57.

But basically CrashReporter is always failing to submit crashes.  The last time it worked for me was in June.

Reproducible: Always

Steps to Reproduce:
1. Crash Minefield.
2.
3.
Actual Results:  
Message that crash reporter failed to submit crash.

Expected Results:  
Crash dump should have been submitted.

This happens on 2 different machines running Minefield on 2 different networks (using 2 different ISPs).
Whiteboard: DUPEME
I don't think so since a file is created and Crash Reporter (breakpad) launches, it's just not sending any of the crash dumps, they all get piles up in the Crash Reports\pending directory.

If any dupe, it is more closely related to bug 392001 but that case says that no connection attempt is made.
Sounds like Bug 390568. Do you have IE7? I believe it sets "Check for
server certificate revocation". If that's set try unsetting it. If that works then this sounds like a dupe.
Well I was going to say it wasn't a dupe since while I do have IE7, the "Check for
server certificate revocation" wasn't checked (it was disabled).  On a whim, I enabled it and then disabled it.  After that submissions worked so I guess it is a dupe.

Not sure why I had to enable and then disable the "Check for
server certificate revocation" though.

A more permanent fix would be to make sure the certificate that is used for submitting crash reports, is actual valid for the submission site.  Currently it is not.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
Whiteboard: DUPEME
You need to log in before you can comment on or make changes to this bug.