[SOLVED] HTTPS not working correctly in Chrome and Chromium...
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
it's probably rejecting you by having detected your a file shark.
Hi...
Thank you for your reply. I'm not sure what you mean by "file shark."
Quote:
Originally Posted by X-LFS-2010
if that don't work use a "real OS" that compiles firefox from scratch without allot of headaches or build failures. it should be working then.
if not: then perhaps your authentication libraries are used by firefox and have become changed (ie, openssl). unfortunately, there are so many auth mechs these days (not just openssl: tens or hundreds of knotted auth libs PLUS kernel auth support PLUS hardware auth support)
But why does my copy of Firefox work correctly but Chrome and Chromium does not.
Quote:
Originally Posted by X-LFS-2010
back up from this problem: don't get so close it swallows you. try the version of firefox (chrome flavor) that last worked first.
Nah, it's not worth that.
My copy of Chrome and Firefox are "original," meaning there were no previous versions.
But why does my copy of Firefox work correctly but Chrome and Chromium does not.
Sorry, but what are you confused about still??? Posts #2, #7, #11, #22, #23, and #28 all explain why you're having issues. What, exactly, are you confused about? What is not/has not been clear in any or all of these explanations???
Upgrade your OS, period. That's it. You're getting this problem because of the age of the cryptographic libraries, and the age of the browser. Can't update browser unless you compile from source, and even then you will STILL HAVE THE PROBLEM because your crypto libraries will STILL BE OLD.
Sorry, but what are you confused about still??? Posts #2, #7, #11, #22, #23, and #28 all explain why you're having issues. What, exactly, are you confused about? What is not/has not been clear in any or all of these explanations???
Hi...
In part because my copy of Chrome version 49 works fine on Windows Vista, an even older OS.
Quote:
Originally Posted by TB0ne
Upgrade your OS, period. That's it. You're getting this problem because of the age of the cryptographic libraries, and the age of the browser. Can't update browser unless you compile from source, and even then you will STILL HAVE THE PROBLEM because your crypto libraries will STILL BE OLD.
Yes, I understand that I will need to upgrade Lubuntu. Since that seems to be the only known solution, I'll go ahead and mark this thread as "SOLVED."
Hi...
In part because my copy of Chrome version 49 works fine on Windows Vista, an even older OS.
Because Windows Vista reaches end-of-life in April of 2017. Lubuntu 14.04 reached end of life April 2016. Do you see the difference???? If that's not clear enough:
Windows Vista received upgraded crypto libraries
Lubuntu 14.04 DID NOT receive upgraded crypto libraries.
Checking end-of-life on software, reading release notes, and doing research are all things you can do for yourself.
Quote:
Yes, I understand that I will need to upgrade Lubuntu. Since that seems to be the only known solution, I'll go ahead and mark this thread as "SOLVED."
If you really did understand that, there wouldn't be three pages on this thread, with the last one still having you 'confused'.
Hi...
No, support ends at some point this year, according to this page.
Nice that you mention you're using LTS now. Regardless, changes nothing....You don't have the libraries, and won't. Even if you want to split hairs and be "confused", it's EOL next month.
Nope, because Lubuntu 14.04 was the ONLY LTS version until 16.04. All other versions didn't even have the option, and you sure didn't mention it.
Quote:
As it stands, unless someone knows exactly how to fix this issue, the solution is to upgrade.
You were told NUMEROUS times how to fix it, but you either didn't read or understand the fixes. Post #2 tells you how to get this 'patched' at the very least, and post #7 follows it up. You even posted that the command-line configuration was an option (post #3), but either didn't run it, or ignored it.
The real solution is, as explained to you numerous times, is to upgrade. Nothing to be confused about, and don't know how many more times folks need to tell you this, especially since you ran your own test with a newer version of Linux and thing worked fine, proving the theory.
I had this happen to me in 16.02 and 17.04. Both times it was a certificate problem with Chromium. Removing it and installing Chrome "fixed" it.
Hello and welcome to the forum
Thank you for registering to share this with me. In my case, the problem is with both Chrome and Chromium, although installing a slightly newer version of Chrome might be worth trying.
Regards...
Last edited by ardvark71; 05-10-2017 at 12:11 AM.
Reason: Changed wording.
Ohhh, yeahhhh!! I finally got this problem entirely fixed without having to upgrade the OS! From what I found here, one command took care of it all...
Code:
sudo apt-get install libnss3-1d
Now both Chrome and Chromium work as they should! I probably would have never come across this had I not upgraded Chromium to version 58 and suddenly come across the error practically everywhere I tried to go.
Regards...
Last edited by ardvark71; 05-17-2017 at 06:58 AM.
Reason: Added comment.
Ohhh, yeahhhh!! I finally got this problem entirely fixed without having to upgrade the OS! From what I found here, one command took care of it all...
Code:
sudo apt-get install libnss3-1d
Now both Chrome and Chromium work as they should! I probably would have never come across this had I not upgraded Chromium to version 58 and suddenly come across the error practically everywhere I tried to go.
I wouldn't call spending three months on solving a problem with old, outdated software something to be congratulated about. Especially since doing a fresh install would've taken about 30 minutes.
And he's still left with an outdated system that's EOL. Pointless.
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
Posts: 13,602
Rep:
@TB0ne, that post is in no way constructive and adds nothing to the conversation that you haven't already said. I've asked you multiple times to refrain from this kind of behavior.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
