Can't access websites with self-signed certificates

[Scripter17]

Steps to reproduce

Create an HTTPS server with a self-signed TLS certificate and attempt to access it via FireFox for iOS.

Expected behavior

Give a warning that the site isn't secure, but otherwise allow the user to connect.

Actual behavior

The progress bar at the top of the screen permanently hangs and the browser won't connect.

Device & build information

• Device: iPhone SE
• Build version: Firefox Daylight 29.1 (3022)
  1. Notes
• Attempting to access the HTTPS site on Safari works as expected, and this has only been happening recently. (don't remember exactly when, sorry)
• I've tried creating a certificate authority, trusting it on my phone, then generating a certificate signed by that authority, but I keep getting stuck at the "enable full trust for root certificates" step. Might work, might not.
• Changing the HTTPS server to an HTTP one connects fine.
• The console.log at the top of my server's code won't trigger when FF connects to it as HTTPS.
• The technical details for the certificate on FireFox for Windows says TLS_AES_256_GCM_SHA384, 256 bit keys, TLS 1.3
• It worked once just now as I was testing it. It was in normal non-private mode if that helps at all.
  • Come to think of it I remember it sometimes wouldn't in private mode work unless I hit the "trust this site" button in normal mode.

┆Issue is synchronized with this Jira Task

[github-actions[bot]]

This issue has been automatically marked as stale. Has the issue been fixed, or does it still require the community's attention? Please leave any comment to keep this issue opened. It will be closed automatically if no further update occurs in the next 30 days. Thank you for your contributions!

[Scripter17]

Currenlty on Firefox 109.0 (25841) and it seems to still be an issue

Honestly I've given into apple's BS and switched to safari

I don't suppose it's the https://LocalIPAddress that's the issue? I might try wrangling ios into letting me add my own root certificate to see if we can rule that out

[github-actions[bot]]

This issue has been automatically marked as stale. Has the issue been fixed, or does it still require the community's attention? Please leave any comment to keep this issue opened. It will be closed automatically if no further update occurs in the next 30 days. Thank you for your contributions!

[jpann]

I wonder if this is happening because of this About upcoming limits on trusted certificates, which prevents the self-signed certificate from being trusted on the iOS device. Once I recreate my certificate using a shorter validity period (< 398 days), I no longer have the issue.