Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

Peer’s Certificate issuer is not recognized.

  • 5 Mbohovái
  • 3 oguereko ko apañuãi
  • 6 Hecha
  • Mbohovái ipaháva zeuzi

more options

(here would be domain)

Peer’s Certificate issuer is not recognized.

HTTP Strict Transport Security: true HTTP Public Key Pinning: false

Certificate chain:


BEGIN CERTIFICATE-----

(here would be the cert)


END CERTIFICATE-----
(here would be domain) Peer’s Certificate issuer is not recognized. HTTP Strict Transport Security: true HTTP Public Key Pinning: false Certificate chain: -----BEGIN CERTIFICATE----- (here would be the cert) -----END CERTIFICATE-----

Opaite Mbohovái (5)

more options

additonal info, this error only occurs on firefox.

more options

found out what the problem is, virtual host configs of apache /etc/apache2/sites-enable/000-default.conf SSLCertificateChainFile was .crt

more options

I was going to say that most time certificate issue is from the site that it comes not something of Browser doing.

more options

well its kinda the sites fault yes not the browsers but yeah google chrome and safari are smart enough to understand that a ca-bundle file cant be a .crt file

more options

and i also think apache should at least give a warn that the SSLCertificateChainFile is a crt file