HTTPS broken in FF
Have tried all of the steps listed in this forum and others, including un-installing and re-installing FF, clearing all caches, removing all Windows Firewall rules associated with FF (Firewall for FF never asks me if i wish to allow the connection, so FF never attempts a HTTPS connection?). FF HTTPS is still broken. Mozilla Support Moderator Philipp for Wendy10477 attempted to provide some steps, but these steps do not work for me. Philipp, are you interested in attempting to solve this? My FF HTTPS has been broken for 5 months now and i have not been able to use FF for that 5 months. Chrome and IE HTTPS work fine. Just FF cannot get it's act together, not in any of the releases i have tried, from 23 to 38 (and ver 1, 2, 9 and others). FF is my preferred browser over IE and (RAM greedy) Chrome. It would be nice if FF HTTPS worked.
All Replies (13)
I don't know that Windows firewall pays attention to the port Firefox is using, so I wouldn't rely on that as an indication.
Please try opening the Network Monitor in a tab (Ctrl+Shift+q or Ctrl+Shift+k and then click Network along the top edge).
Then paste this in the address bar and press Enter: https://jeffersonscher.com/res/jstest.php
That should load a test page, and since you have never seen this page before, the status in the left column should be 200. I have attached an illustrative screen shot.
What do you get?
Hi RobertHarper, I am very sorry to hear that you are still having problems with broken HTTPS in Firefox. I assure you that this problem will be fixed. I have escalated this question. This means that I have designated this question as one that needs special attention. It can take a maxim of 72 hours for one of our top people to get back to you.
Some more information
RobertHarper said
RobertHarper saidFF broken after virus infected my windows userinit. Virus removed, but FF still broke in https and uninstall/reinstall does not fix broken httpsReplying to my own question: 5 months later, https started working again WITHOUT having done anything - no reinstalls, no upgrades, no cache clears. Nothing. FF is kinder to my 2GB RAM PC than Chrome, so it is nice to have FF working again. A working HTTPS is essential for many sites these days.
This is a link to the orignal question
Modified
You can check the date and time and time zone in the clock on your computer: (double) click the clock icon on the Windows Taskbar.
You can retrieve the certificate and check details like who issued certificates and expiration dates of certificates.
- Click the link at the bottom of the error page: "I Understand the Risks"
- Let Firefox retrieve the certificate: "Add Exception" -> "Get Certificate"
- Click the "View" button and inspect the certificate and check who is the issuer.
You can see more details like the intermediate certificates that are used in the Details tab.
Who is the issuer of the certificate?
To Support Officer jscher2000:
It may help to know that this occurred after installing and uninstalling JWPlayer.
=================================================================================================================================================================
To jscher2000: Following info contains 3 parts (3 pics attached):
- Network activity for requested URL: http://www.google.com.au (which redirects to https://www.google.com.au/?gws_rd=ssl)
- Browser Information Page for requested URL: http://jeffersonscher.com/res/jstest.php (Note http)
- Network activity for requested URL: https://jeffersonscher.com/res/jstest.php (Note https)
Note that none of the https requests have a status of 200 but rather have a blank status.
=================================================================================================================================================================
Request URL: http://www.google.com.au/ Request method: GET Status code: 302 Found File: / Size 0KB Response: blank Timings: 0ms (DNS resolution, Connecting, Sending, Receiving), 188ms (Waiting)
Response headers (0.294 KB):undefined
====================
Alternate-Protocol: "80:quic,p=0" Cache-Control: "private" Content-Length: "234" Content-Type: "text/html; charset=UTF-8" Date: "Wed, 17 Jun 2015 02:53:50 GMT" Location: "https://www.google.com.au/?gws_rd=ssl" Server: "gws" X-Frame-Options: "SAMEORIGIN" X-XSS-Protection: "1; mode=block"
Request headers (0.495 KB)
===========
Host: "www.google.com.au" User-Agent: "Mozilla/5.0 (Windows NT 6.1; rv:38.0) Gecko/20100101 Firefox/38.0" Accept: "text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8" Accept-Language: "en-US;en;q=0.5" Accept-Encoding: "gzip, deflate" Cookie: "PREF=ID=789ac8d6f976475e:FF=0:TM=143450...bl5R" Connection: "keep-alive"
=================================
Request URL: https://www.google.com.au/?gws_rd=ssl Request method: GET File: /?gws_rd=ssl Size 0KB Response: blank Timings: 0ms (DNS resolution, Connecting, Sending, Receiving), 29ms (Waiting)
Request headers (0.506 KB)
===========
Host: "www.google.com.au" User-Agent: "Mozilla/5.0 (Windows NT 6.1; rv:38.0) Gecko/20100101 Firefox/38.0" Accept: "text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8" Accept-Language: "en-US;en;q=0.5" Accept-Encoding: "gzip, deflate" Cookie: "PREF=ID=789ac8d6f976475e:FF=0:TM=143450...bl5R" Connection: "keep-alive"
=================================================================================================================================================================
Download: Fast, Fun, Awesome Information About Your Browser
Your browser supplies the following information to sites about itself. This is not a comprehensive list of all information available to the page. Data from HTTP Headers
Your browser's request includes the following data:
Browser "User Agent" string: Mozilla/5.0 (Windows NT 6.1; rv:38.0) Gecko/20100101 Firefox/38.0 Your public IP address: 150.101.89.147 (REMOTE_ADDR) Referring page (if any):
Full HTTP Request Headers: Host: jeffersonscher.com User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:38.0) Gecko/20100101 Firefox/38.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-US,en;q=0.5 Accept-Encoding: gzip, deflate Connection: keep-alive JavaScript Browser Tests navigator object properties
Scripts in web pages can check various properties of the navigator object. This information can be blocked or overridden by the user.
navigator.userAgent = Mozilla/5.0 (Windows NT 6.1; rv:38.0) Gecko/20100101 Firefox/38.0 navigator.appName = Netscape navigator.appCodeName = Mozilla navigator.appVersion = 5.0 (Windows) navigator.platform = Win32
Active plugins (navigator.plugins collection, does not show "Never Activate" plugins):
Name (Version): Adobe Acrobat (10.1.4.38) Description: Adobe PDF Plug-In For Firefox and Netscape 10.1.4 File name: nppdf32.dll Name (Version): DjVu Plugin Viewer (6.10001.34386.1) Description: DjVu browser plugin File name: npdjvu.dll Name (Version): Java Deployment Toolkit 7.0.790.15 (10.79.2.15) Description: NPRuntime Script Plug-in Library for Java(TM) Deploy File name: npdeployJava1.dll Name (Version): Java(TM) Platform SE 7 U79 (10.79.2.15) Description: Next Generation Java Plug-in 10.79.2 for Mozilla browsers File name: npjp2.dll Name (Version): Shockwave Flash (12.0.0.70) Description: Shockwave Flash 12.0 r0 File name: NPSWF32_12_0_0_70.dll Name (Version): VLC Web Plugin (2.1.3.0) Description: VLC media player Web Plugin 2.1.3 File name: npvlc.dll
DOM object detection: objects/methods/collections
As a more reliable indication of a browser's capabilities, scripts can check for the existence of various objects and properties:
if(document.getElementById) = true; // all modern browsers support this method if(document.layers) = false; // this collection identifies Netscape version 4 only if(document.all) = false; // this object works in IE4-8 and emulations thereof
Copyright © 2014 Jefferson Scher. Updated 3/26/2014.
=================================================================================================================================================================
Request URL: https://jeffersonscher.com/res/jstest.php Request method: GET File: jstest.php Size 0KB Response: blank Timings: 0ms (DNS resolution, Connecting, Sending, Receiving), 225ms (Waiting)
Request headers (0.292 KB)
===========
Host: "jeffersonscher.com" User-Agent: "Mozilla/5.0 (Windows NT 6.1; rv:38.0) Gecko/20100101 Firefox/38.0" Accept: "text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8" Accept-Language: "en-US;en;q=0.5" Accept-Encoding: "gzip, deflate" Connection: "keep-alive"
To cor-el
The problem is not date and time related (although i have seen this problem before and am aware of it). No certificate has been received (see response to jscher2000). I incorrectly said that FF was now working (my FF shortcut linked to Chrome and i had not noticed). My FF HTTPS is still not working (broken after a JWPlayer install/uninstall - if that helps?).
Boot the computer in Windows Safe Mode with network support (press F8 on the boot screen) as a test.
Try to reset (power on/off) the router.
I'm not sure how to interpret 225ms waiting with no further response. Is it timing out??
An uninstall/reinstall cycle may not purge everything, so I think these experiments are worth a try:
Create a new Firefox profile
A new profile will have your system-installed plugins (e.g., Flash) and extensions (e.g., security suite toolbars), but no themes, other extensions, or other customizations. It also should have completely fresh settings databases and a fresh cache folder.
Start up in the Profile Manager using the Start menu search box or Run dialog (lower part of the Start screen or Windows key+R), type or paste the following and press Enter:
firefox.exe -P
Do not delete anything here
Click the Create Profile button, assign a name like June16, and skip over the option to move the folder location. Then start Firefox in the new profile you created.
Will any secure sites load??
If the new profile is good, we can describe how to migrate your bookmarks and possibly other data into it.
Clean Reinstall
We use this name, but it's not about removing your settings, it's about making sure the program files are clean (no inconsistent or alien code files). As described below, this process does not disturb your existing settings. Do NOT uninstall Firefox, that's not needed.
(1) Download a fresh installer for Firefox 38.0.5 from https://www.mozilla.org/firefox/all/ to a convenient location. (Scroll down to your preferred language.)
(2) Exit out of Firefox (if applicable).
(3) Rename the program folder:
(32-bit Windows folder names)
C:\Program Files\Mozilla Firefox
to
C:\Program Files\OldFirefox
(64-bit Windows folder names)
C:\Program Files (x86)\Mozilla Firefox
to
C:\Program Files (x86)\OldFirefox
(4) Run the installer you downloaded in #1. It should automatically connect to your existing settings.
Will a cleanly reinstalled Firefox load HTTPS pages?
Note: Some plugins may exist only in that OldFirefox folder. If something essential is missing, look in these folders:
- \OldFirefox\Plugins
- \OldFirefox\browser\plugins
Hello jscher2000,
i have tried both the clean firefox install you suggested (renaming Firefox Program directory to .old) and creating a new profile. Both of these fail.
However, i am getting inconsistent results: header response is different for URL="http://www.google.com.au" for a new profile without any cookie history. Specifically the header returns with a "P3P:" and "Set-Cookie:" response. Does this matter?
see attached pic for responses.
Hello co-rel,
i have tried running in safe mode, but that makes no difference as i have ensured a cleaned machine with combofix, mbam, spyhunter, etc etc. and i do not run any extra startup processes or startup services. i like and lean and clean machine.
rebooting the router is not an option, as 200 people are connected to it.
Please also be aware that i have had an work-around in chrome for 5 months (albeit inferior to firefox). i am conscious of your time, and am letting you know that if you need to work on other things, i can live with that. However, if you want to know why https is broken for me on firefox but not chrome or IE, and you want me to run tests, then i can do that, if you think that is beneficial for firefox clients worldwide.
Kind Regards Robert Harper (Australia)
RobertHarper said
header response is different for URL="http://www.google.com.au" for a new profile without any cookie history. Specifically the header returns with a "P3P:" and "Set-Cookie:" response. Does this matter?
Seems normal that if it's your first visit, Firefox doesn't send Google its usual cookies, so Google sets one.
I think the new profile + clean reinstall should work around any static issues with Firefox itself, such as bad settings or corrupted files. That leaves dynamic issues, such as Windows/IE proxy configuration (Firefox follows that by default), surviving malware, or upstream issues with the router or ISP.
To jscher2000,
> should work around any static issues with Firefox itself No it does not. Chrome and IE work fine, but FF does not. It is FF issue.
> could be proxy config in IE IE Internet Options have not proxy. IE works fine
> surviving malware. i have scanned my PC with ComboFix, MBAM, SpyHunter, sfc /scannow, etc etc. Zero problems found.
> upstream issues No upstream issues. 200 people on router. Their FF works fine.
i doubt this can be solved without some inside knowledge or diagnostic. It is not an easy issue. If IE, Chrome, Opera and Safari can work then so should FF HTTPS?
You can try to check this via an HTTP log file.
To co-rel,
The http(s) log is large (6914 lines). i have extracted about 20 lines that seem to be the most relevant? Does the log mean anything to you?
i can see an attempt to https port 443 for host=safebrowsing.google.com i can see PR_Write and PR_Read both fail? error=80004005? PR_Write is 0 bytes? Should it have content?
Do you need the full file (682KB)? If so, how do i attach?
Robert Harper
2015-06-18 01:54:27.796000 UTC - 572[1711680]: nsSocketTransport::SetKeepaliveEnabled [17059680] enabled, idle time[10s] retry interval[1s] packet count[10]: globally enabled. 2015-06-18 01:54:27.796000 UTC - 572[1711680]: JIMB: ReleaseFD_Locked: mFDref = 2 2015-06-18 01:54:27.796000 UTC - 572[1711680]: nsHttpConnection::OnSocketWritable [this=172bb6c0] host=safebrowsing.google.com 2015-06-18 01:54:27.796000 UTC - 572[1711680]: nsHttpConnection::GetSecurityInfo trans=17314000 tlsfilter=0 socket=17059690 2015-06-18 01:54:27.796000 UTC - 572[1711680]: nsSocketOutputStream::Write [this=17059750 count=0] 2015-06-18 01:54:27.796000 UTC - 572[1711680]: calling PR_Write [count=0] 2015-06-18 01:54:27.796000 UTC - 572[1711680]: PR_Write returned [n=-1] 2015-06-18 01:54:27.796000 UTC - 572[1711680]: JIMB: ReleaseFD_Locked: mFDref = 2 2015-06-18 01:54:27.796000 UTC - 572[1711680]: ErrorAccordingToNSPR [in=-5969 out=80004005] 2015-06-18 01:54:27.796000 UTC - 572[1711680]: nsSocketTransport::OnMsgOutputClosed [this=17059680 reason=80004005] 2015-06-18 01:54:27.796000 UTC - 572[1711680]: nsHttpConnection::EnsureNPNComplete setting complete to true 2015-06-18 01:54:27.796000 UTC - 572[1711680]: writing transaction request stream 2015-06-18 01:54:27.796000 UTC - 572[1711680]: nsHttpConnection::GetSecurityInfo trans=17314000 tlsfilter=0 socket=17059690 2015-06-18 01:54:27.796000 UTC - 572[1711680]: nsSocketOutputStream::Write [this=17059750 count=570] 2015-06-18 01:54:27.796000 UTC - 572[1711680]: nsHttpConnection::OnSocketWritable 172bb6c0 ReadSegments returned [rv=0 read=0 sock-cond=80004005] 2015-06-18 01:54:27.796000 UTC - 572[1711680]: nsHttpConnection::CloseTransaction[this=172bb6c0 trans=17314000 reason=80004005] 2015-06-18 01:54:27.796000 UTC - 572[1711680]: nsHttpTransaction::Close [this=17314000 reason=80004005] 2015-06-18 01:54:27.796000 UTC - 572[1711680]: nsHttpTransaction 17314000 loadgroupci set to null in ReleaseBlockingTransaction() - was 0 2015-06-18 01:54:27.796000 UTC - 572[1711680]: nsHttpConnection::Close [this=172bb6c0 reason=80004005] 2015-06-18 01:54:27.796000 UTC - 572[1711680]: nsSocketInputStream::Read [this=17059730 count=4000] 2015-06-18 01:54:27.796000 UTC - 572[1711680]: calling PR_Read [count=4000] 2015-06-18 01:54:27.796000 UTC - 572[1711680]: PR_Read returned [n=-1] 2015-06-18 01:54:27.796000 UTC - 572[1711680]: JIMB: ReleaseFD_Locked: mFDref = 2 2015-06-18 01:54:27.796000 UTC - 572[1711680]: ErrorAccordingToNSPR [in=-5969 out=80004005] 2015-06-18 01:54:27.796000 UTC - 572[1711680]: nsSocketTransport::OnMsgInputClosed [this=17059680 reason=80004005] 2015-06-18 01:54:27.796000 UTC - 572[1711680]: nsHttpConnection::Close drained 0 bytes