Firefox nightly updates break HTTPS
Just for nightly:
For the last week or so (sorry I can't be more specific). When I update the FF Nightly [58.0a1 (2017-10-13) (64-bit)] It keeps breaking something so that I can no longer access HTTPS sites from Nightly. I get the "Secure Connection Failed" page (SEC_ERROR_LIBRARY_FAILURE) for all HTTPS pages (mozillia.org too). It doesn't happen with every update but it has happened at least 3 or 4 times in the last week.
I can access HTTPS from regular Firefox 56.0 if I close nightly first. I can access HTTPS from Chrome/Chromium. Manually disabling all of the add-ons has no effect. However, Nightly will start in safe mode. I suspect that safe mode bypasses the profile. To fix this, I have to reset Firefox, which starts a new profile.
Ñemoĩporã poravopyre
This problem has not reappeared for a few months. I would be willing to mark it solved. I have no real idea what you all did but good work and thanks for your help and for the amazing browser.
Emoñe’ẽ ko mbohavái ejeregua reheve 👍 0Opaite Mbohovái (9)
Which Linux distribution are you using?
You can create a new profile to test if your current profile is causing the problem.
See "Creating a profile":
- https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles
- http://kb.mozillazine.org/Standard_diagnostic_-_Firefox#Profile_issues
If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.
- /questions/1178999 Secure sites fail with SEC_ERROR_LIBRARY_FAILURE using 57 on ubuntu 17
Thank you for your quick and thorough reply.
1) Ubuntu 17.04
2) A new profile works fine. It was the solution for the other times. Because I'm on sync, creating the new profile is annoying but not hard.
3) This looks like a duplicate of issue /questions/1178999. So you may close it.
4) I'm running Nightly as a canary... so that you can know if there are rough edges that may need sanding.
Moambuepyre telesphore rupive
Do you get this error often when Nightly updates or did you only see it once?
Often? In the last say week there have been roughly 10 to 14 updates and conservatively it has happened 2 to 3 times. So it doesn't happen every time but it isn't rare either.
FYI;
This weekend I updated twice with no issues. This morning (Oct. 16, 2017 at about 10:00 EST) HTTPS stopped working again, same symptoms.
I've copied the profile just in case there's something we can find in that.
[Edit grammar]
Moambuepyre telesphore rupive
Maybe try to rename/remove SiteSecurityServiceState.txt
The same result.
Ñemoĩporã poravopyre
This problem has not reappeared for a few months. I would be willing to mark it solved. I have no real idea what you all did but good work and thanks for your help and for the amazing browser.
Moambuepyre telesphore rupive
The Nightly development channel gets checkins and two updates each day so sometimes this can lead to issues until fixed, finished or reverted.
If you want to be a Nightly channel Tester then you may be interested in the Builds threads in http://forums.mozillazine.org/viewforum.php?f=23
Moambuepyre James rupive