Closed Bug 2021712 Opened 25 days ago Closed 4 days ago

SUMO KB updates needed for the new security error pages in Firefox 149

Categories

(support.mozilla.org :: Knowledge Base Content, task)

Product:
support.mozilla.org
Component:
Knowledge Base Content
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: alice.wyman, Assigned: ffloare)

References

Details

Attachments

(6 files)

Fx149BetaSecureConnectionFailed-Advanced.png
116.15 KB, image/png
Details
Fx149BetaWarningSecurityRisk-pinningtestAdvanced.png
127.94 KB, image/png
Details
Fx149BetaWarningSecurityRisk-hstsAdvanced.png
146.89 KB, image/png
Details
Fx149BetaWarning-SecurityRiskTimeRelated-Advanced.png
150.50 KB, image/png
Details
Fx149BetaWarning-SecurityRiskUntrustedRootAdvanced.png
173.78 KB, image/png
Details
Fx149BetaWarning-SecurityRiskSelfSignedAdvanced.png
156.75 KB, image/png
Details

Did you check out the steps and FAQs for submitting requests to the CX content team? (yes or no)? [REQUIRED]

**Note: Learn more at https://mozilla-hub.atlassian.net/wiki/spaces/MSS/pages/21430745/Mozilla+Support+Content **

IMPORTANT NOTICE: FOR TIMELY PUBLICATION, CONTENT REQUESTS MUST BE SUBMITTED AT LEAST 14 DAYS BEFORE THE RELEASE DATE, ENABLING THE SUMO TEAM TO MAKE THEM LIVE WITHIN 48 HOURS POST-RELEASE. PLEASE ENSURE THAT ALL SUBMITTED INFORMATION, INCLUDING FEATURE DETAILS AND VISUAL ASSETS, IS FINAL. IN THE EVENT OF ANY UNFORESEEN CHANGES OR DELAYS NECESSITATING A PUSH TO A SUBSEQUENT RELEASE, PROMPTLY INFORM US TO PREVENT PUBLISHING AS PER THE ORIGINAL SCHEDULE.

Content access restriction: Is the content restricted to staff or under embargo (yes or no)? [REQUIRED]

Note: If yes, ensure ‘Advanced Fields’ are visible by selecting ‘Show Advanced Field’ at the top right, then scroll to ‘Security’ and check ‘Confidential Mozilla Employee Bug (non-security)’.

Attention: Any content not marked as confidential will be accessible to both NDAd and non-NDAd contributors with a Bugzilla account. Drafts for non-confidential content will also follow the same access policy, being open to comments for anyone with the link. Non-confidential Bugzillas can benefit from contributions by community contributors, while confidential Bugzillas will be handled exclusively by staff.

Product (ensure to select only one product for each ticket. If your request involves multiple products, file an individual Bugzilla for each)

Choose one below and delete others. [REQUIRED]
Firefox for Desktop (Windows)
Firefox for Desktop (macOS)
Firefox for Desktop (Linux)

Select the type of request.

Choose one or more below and delete others. [REQUIRED]
KB content update/

Please summarize the request, emphasizing any user-facing changes. Include historical context or background information if it helps users understand the new features or changes. [REQUIRED]

Firefox 149 Beta has new security error pages. For example, compare these media gallery images:

Test page: https://tls-v1-1.badssl.com:1011/
Fx148SecureConnectionFailed-TLS https://support.mozilla.org/en-US/gallery/image/57164
Fx149BetaSecureConnectionFailed https://support.mozilla.org/en-US/gallery/image/57135

Test page: https://pinning-test.badssl.com/
Fx148DidNotConnectPotentialSecurityIssue-pinningtest https://support.mozilla.org/en-US/gallery/image/57154
Fx149BetaWarningSecurityRisk-pinningtest https://support.mozilla.org/en-US/gallery/image/57156

Test page: https://subdomain.preloaded-hsts.badssl.com/
Fx148WarningPotentialSecurityRiskAhead-hsts https://support.mozilla.org/en-US/gallery/image/57147
Fx149BetaWarningSecurityRisk-hsts https://support.mozilla.org/en-US/gallery/image/57149

Test page: https://expired.badssl.com/
Fx148WarningPotentialSecurityRiskAhead-TimeRelated https://support.mozilla.org/en-US/gallery/image/57194
Fx149BetaWarning-SecurityRiskTimeRelated https://support.mozilla.org/en-US/gallery/image/57137

Test page: https://untrusted-root.badssl.com/
Fx148WarningPotentialSecurityRiskAhead-untrustedroot https://support.mozilla.org/en-US/gallery/image/57176
Fx149BetaWarning-SecurityRiskUntrustedRoot https://support.mozilla.org/en-US/gallery/image/57140

Test page: https://self-signed.badssl.com/
Fx148WarningPotentialSecurityRiskAhead-selfsigned https://support.mozilla.org/en-US/gallery/image/57180
Fx149BetaWarning-SecurityRiskSelfSigned https://support.mozilla.org/en-US/gallery/image/57142

I submitted a revision (see https://support.mozilla.org/en-US/kb/troubleshoot-time-errors-secure-websites/history) to this article that's pending:

Updates to these other articles are needed:

Related discussion, with fx148 and fx149 images:
https://support.mozilla.org/en-US/kb/troubleshoot-time-errors-secure-websites/discuss/14585 [Fx149] Update, new image needed
https://support.mozilla.org/en-US/kb/error-codes-secure-websites/discuss/14693 [Fx149] Update, new image needed
https://support.mozilla.org/en-US/kb/what-does-your-connection-is-not-secure-mean/discuss/14560 [Fx149] Update, new image needed
https://support.mozilla.org/en-US/kb/secure-connection-failed-firefox-did-not-connect/discuss/14561 [Fx149] Update, new images needed

Are the user-facing changes mentioned above for the production release, or is the feature/change experimental/ beta? (Production, Experimental or Beta) [REQUIRED]

**Note: Specify if the user-facing changes mentioned above are final, experimental, or in beta. This information is crucial for determining the appropriate support and documentation level needed. Please note that SUMO KB articles only support the production version for Firefox.
Not sure if this is only in Beta or if it is for Fx149 release. Can the Firefox product or SUMO KB Content team verify?

Are the new features or changes region-specific? Are they going to be released in a gradual rollout? [REQUIRED]

**Note: Please confirm if these features or changes are limited to specific geographic regions and if they will be implemented gradually. Knowing this helps us tailor our documentation and support resources appropriately.
Unknown. Can the Firefox product team or SUMO KB Content team verify?

Please indicate if this is an on- or off-train release [REQUIRED]

**Note: If applicable, add the product version number to the end of the Summary field using the format: Summary [Product V123]. If this is an off-train release, please use the format: Summary [Product off-train].

What is the anticipated release date? [REQUIRED]

Note: Content is typically published at, or within, 48 hours of the release.
Firefox 149 release date is March 24, 2026

Does the content need to be published prior to the release date? If so, when? [REQUIRED]

Note: If you don’t let us know if this date changes, it will be published on this date

Does the content need to be localized in any languages outside of EN-US? If yes, please indicate which languages. [REQUIRED]

Note: A minimum of 10 days is required for translation requests.
Yes, all

Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED]

Please include links to any design assets, visuals, figma files, etc. [REQUIRED]

Note: Ensure to submit only final visual assets relevant to the Production release, excluding Nightly or Beta images, and favor 'Light mode' UI screenshots over 'Dark mode'

Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED]

Does the content need approval before publishing? If yes, identify the one approver responsible for this task.

Note: Minor changes such as string updates are directly handled in SUMO, and will not lead to the generation of a pre-publishing draft. [REQUIRED]

Test page: https://tls-v1-1.badssl.com:1011/
Firefox 149 Beta Secure Connection Failed error page with Advanced panel (no option to bypass error)
Learn more link goes to https://support.mozilla.org/1/firefox/149.0/WINNT/en-US/connection-not-secure
"Secure connection and security warning error pages in Firefox" KB article

Note: https://tls-v1-1.badssl.com:1011/ is the only test page I could find that still produces a "Secure Connection Failed" error. The test page https://1000-sans.badssl.com/ that was used in earlier versions of the Secure connection and security warning error pages in Firefox article (see revision 272434 and Image: Fx97SecureConnectionFailed) now produces a different (time-related) error page.

Firefox 149 Beta Security Risk warning page with Advanced panel (no option to bypass error)
Test page: https://pinning-test.badssl.com/

Test page: https://subdomain.preloaded-hsts.badssl.com/
Firefox 149 Beta error page with Advanced panel (no option to bypass error)
Learn more link: https://support.mozilla.org/1/firefox/149.0/WINNT/en-US/connection-not-secure
"Secure connection and security warning error pages in Firefox" KB article

Firefox 149 Beta error page with Advanced panel and "Proceed to expired.badssl.com (Risky)" button to bypass error
Test page: https://expired.badssl.com/
Learn more link: https://support.mozilla.org/1/firefox/149.0/WINNT/en-US/time-errors
"Troubleshoot time-related errors on secure websites" KB article

Test page: https://untrusted-root.badssl.com/
Firefox 149 Beta warning page Advanced panel with "Proceed to untrusted-root.badssl.com (Risky)" button to bypass error
Learn more link goes to https://support.mozilla.org/1/firefox/149.0/WINNT/en-US/connection-not-secure
"Secure connection and security warning error pages in Firefox" KB article

Hey Kiki,

Assigning this to you for initial review so you can re-assign accordingly.

Thanks!

Assignee: nobody → kelimutu
Status: NEW → ASSIGNED

(from comment #0)

I submitted a revision (see https://support.mozilla.org/en-US/kb/troubleshoot-time-errors-secure-websites/history) to this article that's pending:

Updates to these other articles are needed:

I submitted a revision to the second article, https://support.mozilla.org/en-US/kb/what-does-your-connection-is-not-secure-mean
(see https://support.mozilla.org/en-US/kb/what-does-your-connection-is-not-secure-mean/history). I was going to start updating a third article, https://support.mozilla.org/en-US/kb/error-codes-secure-websites but I'll wait until a SUMO KB Content staff member can review the two articles I already updated for fx149 before I do any more updates, especially since this bug could be assigned to someone else, not me.

The last article, https://support.mozilla.org/en-US/kb/secure-connection-failed-firefox-did-not-connect/ which is titled "Secure connection and security warning error pages in Firefox", is important since it's linked in-product from many different types of fx149 error pages (see the images I attached above). It also needs a lot of work since the "Did Not Connect" error doesn't seem to exist in Firefox 149 beta - The test page that produces the error in Firefox 148, https://pinning-test.badssl.com/ now produces the same "Warning: Security Risk" page with the message, "Be careful. Something doesn't look right" shown for many other errors. See my post in this discussion.

Advanced panel for "Warning: Security Risk" error page in Firefox 149 Beta (Windows 11 en-US) showing a
"Proceed to self-signed.badssl.com (Risky)" button to bypass the error

Test page: https://self-signed.badssl.com/

I found bug 2017378 on the updated network error pages in Firefox 149. From the bug report (I don't have access to the figma page):
Niklas Baumgardner [:niklas] Reporter
Description • 2026-02-17 13:33 EST
(quote)

Release Note Request (optional, but appreciated)
[Why is this notable]:
The error pages from certificate or connection issues have been updated.
The error pages have a new and refreshed look. The figma link for the updated pages can be found here: Error pages figma.
[Suggested wording]:
Firefox error pages have a fresh new look, with updated visuals that better match the overall feel of Firefox. The redesigned pages create a more cohesive experience while making it clearer what went wrong.
[Links (documentation, blog post, etc)]:

See Also: → 2017378
Summary: Updates needed for new security error pages in Firefox 149 → SUMO KB updates needed for the new security error pages in Firefox 149

In addition to the four articles I mentioned above, the Secure website certificate article also needs an update. I submitted revision with new Fx149 images. See https://support.mozilla.org/en-US/kb/secure-website-certificate/history

Duplicate of this bug: 2025456

see comment 7. I submitted revisions to these articles awhile ago that are still pending review:

Updates to these articles are still needed:

As I wrote in comment 7, I'll wait until a SUMO KB Content staff member can review the two articles I already updated for fx149 before I do any more updates, especially since this bug could be assigned to someone else, not me.

See also comment 10. Besides the four articles I mentioned above, the Secure website certificate article also needs an update. I submitted a revision that's pending review: https://support.mozilla.org/en-US/kb/secure-website-certificate/history

Kiki, can you take a look at my revisions and the additional information furnished in bug 2025456? (I can't access to the figma file).

Flags: needinfo?(kelimutu)

My revisions to the articles that need fx149 updates are completed. Flavius, can you review these three articles that are pending review? See:

Assignee: kelimutu → ffloare
Flags: needinfo?(ffloare)

Kiki, I reassigned this bug to Flavius based on your content intake workflow blog.

Flags: needinfo?(kelimutu)

(In reply to Alice Wyman from comment #16)

Kiki, I reassigned this bug to Flavius based on your content intake workflow blog.

Sounds good. Thanks for working on these updates, Alice.

@Flavius can you review Alice's pending revisions above as this request came up late for v149? Here's a draft from Niklas on bug2025456 for your reference: https://docs.google.com/document/d/1XVuTDBMYNcftGcgHnfqdZXr2yTsXhAxWVWWA60J2wUo/edit?tab=t.0#heading=h.i87wf9qbewce

(In reply to Kelimutu [:kiki] from comment #17)

(In reply to Alice Wyman from comment #16)

Kiki, I reassigned this bug to Flavius based on your content intake workflow blog.

Sounds good. Thanks for working on these updates, Alice.

@Flavius can you review Alice's pending revisions above as this request came up late for v149? Here's a draft from Niklas on bug2025456 for your reference: https://docs.google.com/document/d/1XVuTDBMYNcftGcgHnfqdZXr2yTsXhAxWVWWA60J2wUo/edit?tab=t.0#heading=h.i87wf9qbewce

Hello, I approved Alice's revisions, but I changed the wording and some images to follow the document Niklas provided. The bug can be closed.

Flags: needinfo?(ffloare)

Some images mention Nightly, while others mention Firefox. I don't particularly see this as an issue, so feel free to change/update them.

(In reply to Flavius Floare from comment #20)

Some images mention Nightly, while others mention Firefox. I don't particularly see this as an issue, so feel free to change/update them.

I submitted a new revision to replace the "Nightly" images with Firefox images that show the address bar and tab title Warning: Security Risk in Firefox 149 (as shown in comment 8 above), along with some other edits.
See https://support.mozilla.org/en-US/kb/secure-connection-failed-firefox-did-not-connect/history and the content of my pending revision.

(In reply to Alice Wyman from comment #21)

(In reply to Flavius Floare from comment #20)

Some images mention Nightly, while others mention Firefox. I don't particularly see this as an issue, so feel free to change/update them.

I submitted a new revision to replace the "Nightly" images with Firefox images that show the address bar and tab title Warning: Security Risk in Firefox 149 (as shown in comment 8 above), along with some other edits.
See https://support.mozilla.org/en-US/kb/secure-connection-failed-firefox-did-not-connect/history and the content of my pending revision.

I also removed or replaced Nightly images for two other articles:
https://support.mozilla.org/en-US/kb/error-codes-secure-websites/history
https://support.mozilla.org/en-US/kb/what-does-your-connection-is-not-secure-mean/history

Abby approved my revisions to the three articles I mentioned in comment 21 and comment 22. I'll close this bug.

Status: ASSIGNED → RESOLVED
Closed: 4 days ago
Resolution: --- → FIXED

Thanks, all!

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: