All Products Community Forum

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:

[certificate]

[certificate]

[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've got a question/suggestion about Picture in Picture feature. Why "Close" button works the same as "Back to Tab"?

Scenario: Close the Picture in Picture video by clicking on the [X] button or Cmd+W shortcut.

Actual result: Picture in Picture closes and Firefox window opens, on the tab containing the video. This is very strange behaviour. If I close the video, I don't want to watch it now. Essentially "Close" button works exactly like "Back to Tab" button - so what's the point? If I wanted to switch to the tab - I would click on "Back to tab".

Expected result: I expect Picture in Picture video to close and nothing else to happen. Don't open the window/tab containing the video.

Thanks

Hello. How can I post HTML code snippets in support.mozilla.org questions ? All HTML code is rendered and none of the usual markdown (``` etc.) works.

i have tried LITERALLY EVERYTHING and i can just not connect to my site that uses http, it constantly redirects to https which DOES NOT WORK. and i am trying to connect to my server here so its kinda important but i clearly CANT access it.. i have watched countless forums, videos, addons. but nothing helps so please if anyone knows anything about this thatd be amazing.

ps also i have connected to the SAME ip/http server before using firefox, but now it does not work.

I don't want to "update my software" every day. How can I turn this function completely off ? This continuous badgering makes me want to switch to another provider.

Hello. Yesterday, I deleted all the stored login information, such as cookies. Latter, I tried to make login, I filled my name and password. As usual, Facebook refuses to login, giving me a choice of extra steps necessary. I chosen to receive a security code on my e-mail. I copy and pasted it on the suitable place and click on the button to proceed.

That's when things stop working. It usually it works as expected, but now it just return to the login page, nothing filled. Bellow, an apparently relevant info the shows on browser console:

"ErrorUtils caught an error:

_.getClientCapabilities is not a function [Caught in: Passkey authentication failed during visibility callback]

Subsequent non-fatal errors won't be logged; see https://fburl.com/debugjs. Object { column: "1421", clientTime: 1774704924, extra: {}, guardList: [], hash: "ukkpfs", isNormalizedError: true, line: "86", loggingSource: "FBLOGGER", message: "_.getClientCapabilities is not a function [Caught in: Passkey authentication failed during visibility callback]", messageFormat: "_.getClientCapabilities is not a function [Caught in: Passkey authentication failed during visibility callback]", … } D_9oglqPD5n.js:79:56"