Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #191338 > unrolled thread
| Started by | Joe <joe.on.list@gmail.com> |
|---|---|
| First post | 2018-01-19 18:00 +0100 |
| Last post | 2018-01-20 14:50 +0100 |
| Articles | 3 — 2 participants |
Back to article view | Back to linux.debian.user
HTTPS - Your connection is not private - ERR_CERT_AUTHORITY_INVALID Joe <joe.on.list@gmail.com> - 2018-01-19 18:00 +0100
Re: HTTPS - Your connection is not private - ERR_CERT_AUTHORITY_INVALID Dave Sherohman <dave@sherohman.org> - 2018-01-20 14:10 +0100
Re: HTTPS - Your connection is not private - ERR_CERT_AUTHORITY_INVALID Joe <joe.on.list@gmail.com> - 2018-01-20 14:50 +0100
| From | Joe <joe.on.list@gmail.com> |
|---|---|
| Date | 2018-01-19 18:00 +0100 |
| Subject | HTTPS - Your connection is not private - ERR_CERT_AUTHORITY_INVALID |
| Message-ID | <v9Ibf-5Sa-11@gated-at.bofh.it> |
Hi all, I'm helping a friend with his netbook, an old acer aspire one, on which I had installed Debian Jessie about two years ago. He was receiving a message at boot: "run fsck manually" for some filesystem inconsistency. He ask me for help, so after having run fsck the system boot properly. Then I checked the system and noticed chromium was not able to strart as expected. I uninstalled chromium and tried to reinstall it, but apt won't to reinstall it. The problem was a link to unstable repo in sources.list (I had added that to install a newer kernel customized in jessie): removed that line I installed chromium without any problem. Now, when I open chromium or midori, I receive the error in the message subject. Any https url is not opened and a warning page is displayed instead. What could be the problem? And How to solve? Many thanks in advance! :)
[toc] | [next] | [standalone]
| From | Dave Sherohman <dave@sherohman.org> |
|---|---|
| Date | 2018-01-20 14:10 +0100 |
| Subject | Re: HTTPS - Your connection is not private - ERR_CERT_AUTHORITY_INVALID |
| Message-ID | <va14e-16H-13@gated-at.bofh.it> |
| In reply to | #191338 |
> Now, when I open chromium or midori, I receive the error in the message subject. > Any https url is not opened and a warning page is displayed instead. > > What could be the problem? Sounds like the root CA (Certification Authority) certificates aren't installed, making it impossible to establish trust in the individual site certificates. > And How to solve? First thing I'd try would be reinstalling the ca-certificates package. (Well, actually, the first thing I'd consider would be copying all important data to another location, then either restore a backup or reinstall the system, because it sounds like the problem it encountered is having widespread effects, so you're likely to encounter further weird problems like this in the future. But I assume that, in this case, neither of those is a viable option, so you're stuck with playing whack-a-mole as broken things are discovered.) -- Dave Sherohman
[toc] | [prev] | [next] | [standalone]
| From | Joe <joe.on.list@gmail.com> |
|---|---|
| Date | 2018-01-20 14:50 +0100 |
| Message-ID | <va1GW-1kl-11@gated-at.bofh.it> |
| In reply to | #191359 |
I tried: apt remove ca-certificates and then: apt install ca-certificates But the problem persists.. I'd follow your suggest. I've backed up, some scripts and openbox configurations. Now I'm ready to do a reinstall from scratch. Anyway, before that, I'd like to try to remove all "non-jessie" packages installed, to obtain a "pure" Jessie system. Is there a way with apt or aptitude to achieve that goal? Thank a lot for your reply Dave!!! :D On Sat, Jan 20, 2018 at 2:01 PM, Dave Sherohman <dave@sherohman.org> wrote: >> Now, when I open chromium or midori, I receive the error in the message subject. >> Any https url is not opened and a warning page is displayed instead. >> >> What could be the problem? > > Sounds like the root CA (Certification Authority) certificates aren't > installed, making it impossible to establish trust in the individual > site certificates. > >> And How to solve? > > First thing I'd try would be reinstalling the ca-certificates package. > > (Well, actually, the first thing I'd consider would be copying all > important data to another location, then either restore a backup or > reinstall the system, because it sounds like the problem it encountered > is having widespread effects, so you're likely to encounter further > weird problems like this in the future. But I assume that, in this > case, neither of those is a viable option, so you're stuck with playing > whack-a-mole as broken things are discovered.) > > -- > Dave Sherohman >
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web