Page 1 of 1

Google Chrome Issue

Posted: Tue Jan 30, 2018 2:16 am
by sondya.boberg
Sorry to make a new post on this, but my issue with Google Chrome has not been solved.

I found a workaround: add --ignore-certificate-errors to the launch specifications. Therefore, something wrong is with the certificates (root certificates specifically, because no other certificates existed).

Here is the result when I start Google Chrome in the terminal without the --ignore-certificate-errors flag:

Code: Select all

[6342:6379:0129/200708.650762:ERROR:nss_util.cc(724)] After loading Root Certs, loaded==false: NSS error code: -8018
[6342:6432:0129/200708.951384:ERROR:cert_verify_proc_nss.cc(922)] CERT_PKIXVerifyCert for clientservices.googleapis.com failed err=-8172
[6342:6373:0129/200708.953106:ERROR:cert_verify_proc_nss.cc(922)] CERT_PKIXVerifyCert for translate.googleapis.com failed err=-8172
[6342:6431:0129/200709.389075:ERROR:cert_verify_proc_nss.cc(922)] CERT_PKIXVerifyCert for www.google.com failed err=-8172
[6342:6430:0129/200709.395799:ERROR:cert_verify_proc_nss.cc(922)] CERT_PKIXVerifyCert for apis.google.com failed err=-8172
[6342:6373:0129/200709.397137:ERROR:cert_verify_proc_nss.cc(922)] CERT_PKIXVerifyCert for fonts.gstatic.com failed err=-8172
[6342:6372:0129/200709.399380:ERROR:cert_verify_proc_nss.cc(922)] CERT_PKIXVerifyCert for www.gstatic.com failed err=-8172
[6342:6432:0129/200709.399777:ERROR:cert_verify_proc_nss.cc(922)] CERT_PKIXVerifyCert for ssl.gstatic.com failed err=-8172
[6342:6433:0129/200709.524296:ERROR:cert_verify_proc_nss.cc(922)] CERT_PKIXVerifyCert for www.google.com failed err=-8172
[6342:6372:0129/200718.848874:ERROR:cert_verify_proc_nss.cc(922)] CERT_PKIXVerifyCert for ssl.gstatic.com failed err=-8172
For the record, I have to add the same flag to Discord as well for it to work. This is obviously very unsafe, so what can I do to fix this?