Windows 10 reached EOS (end of support) on October 14, 2025. For more information, see this article.

Поиск в поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

Certificate problem accessing an internal company website

  • 2 ответа
  • 1 имеет эту проблему
  • 1880 просмотров
  • Последний ответ от twic

дополнительные действия

I am trying to reach an internal company website ([URL]), with a certificate chain rooted in a company certificate authority. This works fine in Chrome, and worked in Firefox on my previous computer. But i recently got a new machine, and something somewhere is not quite right. I get an error message looking like this (between the ~~~s):

~~~ Someone could be trying to impersonate the site and you should not continue.

Web sites prove their identity via certificates. Firefox does not trust [URL] because its certificate issuer is unknown, the certificate is self-signed, or the server is not sending the correct intermediate certificates.

Error code: SEC_ERROR_UNKNOWN_ISSUER

View Certificate ~~~

If i click on the error code, i get these details:

~~~ [URL]

Peer's Certificate issuer is not recognised.

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

Certificate chain:


BEGIN CERTIFICATE-----

[certificate]


END CERTIFICATE-----
BEGIN CERTIFICATE-----

[certificate]


END CERTIFICATE-----
BEGIN CERTIFICATE-----

[certificate]


END CERTIFICATE-----

~~~

If i click 'View Certificate', i get a chain of three certificates:

  1. Subject common name = [certificate]
  2. Subject common name = [certificate]
  3. Subject common name = [certificate]

If i go to Settings > Privacy & Security > View Certificates > Authorities, i can find both the [certificate] certificates. As far as i can tell, they are identical - i can open the certificate from 'View Certificate' and the corresponding one from the certificate manager and flip between tabs, and all the details are the same.

I am using Firefox 120.0, via a flatpak, on Ubuntu 22. I have given the flatpak access to /etc/ssl/certs, where my company's internal CA certificates are located.

To me, this seems like it should all work. The server has a certificate signed by an internal CA, which is signed by another internal CA, and both those internal CA certificates are in my certificate manager. So what is going wrong? Is there any way i can debug this?

I am trying to reach an internal company website ([URL]), with a certificate chain rooted in a company certificate authority. This works fine in Chrome, and worked in Firefox on my previous computer. But i recently got a new machine, and something somewhere is not quite right. I get an error message looking like this (between the ~~~s): ~~~ Someone could be trying to impersonate the site and you should not continue. Web sites prove their identity via certificates. Firefox does not trust [URL] because its certificate issuer is unknown, the certificate is self-signed, or the server is not sending the correct intermediate certificates. Error code: SEC_ERROR_UNKNOWN_ISSUER View Certificate ~~~ If i click on the error code, i get these details: ~~~ [URL] Peer's Certificate issuer is not recognised. HTTP Strict Transport Security: false HTTP Public Key Pinning: false Certificate chain: -----BEGIN CERTIFICATE----- [certificate] -----END CERTIFICATE----- -----BEGIN CERTIFICATE----- [certificate] -----END CERTIFICATE----- -----BEGIN CERTIFICATE----- [certificate] -----END CERTIFICATE----- ~~~ If i click 'View Certificate', i get a chain of three certificates: # Subject common name = [certificate] # Subject common name = [certificate] # Subject common name = [certificate] If i go to Settings > Privacy & Security > View Certificates > Authorities, i can find both the [certificate] certificates. As far as i can tell, they are identical - i can open the certificate from 'View Certificate' and the corresponding one from the certificate manager and flip between tabs, and all the details are the same. I am using Firefox 120.0, via a flatpak, on Ubuntu 22. I have given the flatpak access to /etc/ssl/certs, where my company's internal CA certificates are located. To me, this seems like it should all work. The server has a certificate signed by an internal CA, which is signed by another internal CA, and both those internal CA certificates are in my certificate manager. So what is going wrong? Is there any way i can debug this?

Изменено Paul

Выбранное решение

From the developer:

> Is the root CA they've identified in the certificate manager is marked as being trusted for websites?

This is something that would be better served as a bugzilla bug.

Can you open a bug here:

https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=Security%3A%20PSM

And let me know the bug number? I'll get the devs involved.

Прочитайте этот ответ в контексте 👍 1

Все ответы (2)

дополнительные действия

Выбранное решение

From the developer:

> Is the root CA they've identified in the certificate manager is marked as being trusted for websites?

This is something that would be better served as a bugzilla bug.

Can you open a bug here:

https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=Security%3A%20PSM

And let me know the bug number? I'll get the devs involved.

дополнительные действия

Aha! The certificates were not trusted for websites, and after i marked them as such, everything works fine. Thanks!

I have opened a bug, because i think the error message here could be better: https://bugzilla.mozilla.org/show_bug.cgi?id=1867771