We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Den här webbplatsen har begränsad funktionalitet medan vi utför underhåll för att förbättra din upplevelse. Om en artikel inte löser ditt problem och du vill ställa en fråga har vi vår gemenskap som väntar på att hjälpa dig på @FirefoxSupport på Twitter, /r/firefox på Reddit.

Avatar for Username

Sök i support

Akta dig för supportbedrägerier: Vi kommer aldrig att be dig att ringa eller skicka ett sms till ett telefonnummer eller dela personlig information. Rapportera misstänkt aktivitet med alternativet "Rapportera missbruk".

Läs mer

Denna tråd har arkiverats. Ställ en ny fråga om du behöver hjälp.

My self-signed *.local.dev wildcard SSL no longer works in v101.0

Chad Reitsma
Chad Reitsma
more options

After upgrading to v101, Firefox no longer recognizes my Self-signed wildcard SSL for *.local.dev.

Before you tell me not to use the .dev domain, I am aware that Google owns it and we're technically not supposed to do local development with the *.local.dev domain.

I have already tried the following: 1. Set network.stricttransportsecurity.preloadlist to FALSE, and everything was working perfectly fine before v101 2. imported the server.crt into Trusted Root Authorities in Windows, and also imported it in the Certificate manager in Firefox. 3. Tried other wildcard local domains like *.test.site, *.local.ddev and these don't work either.

I even tried following recent guides to issue a new certificate with openssl and SAN, and it still doesn't work.

Screenshot of wildcard SSL attached.

After upgrading to v101, Firefox no longer recognizes my Self-signed wildcard SSL for *.local.dev. Before you tell me not to use the .dev domain, I am aware that Google owns it and we're ''technically'' not supposed to do local development with the *.local.dev domain. I have already tried the following: 1. Set network.stricttransportsecurity.preloadlist to '''FALSE''', and everything was working perfectly fine before v101 2. imported the server.crt into Trusted Root Authorities in Windows, and also imported it in the Certificate manager in Firefox. 3. Tried other wildcard local domains like *.test.site, *.local.ddev and these don't work either. I even tried following recent guides to issue a new certificate with openssl and SAN, and it still doesn't work. Screenshot of wildcard SSL attached.
Bifogade skärmdumpar

Vald lösning

Found this guide *Works! https://betterprogramming.pub/trusted-self-signed-certificate-and-local-domains-for-testing-7c6e6e3f9548

Läs svaret i sitt sammanhang 👍 0

Alla svar (3)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Could be this issue:

Chad Reitsma
Chad Reitsma Frågans ägare
more options

Thanks cor-el! That explains it. I will check the release notes next time.

I did try issuing a certificate with the correct SAN, but it's possible I made a mistake. I'll keep trying and report any findings back here.

Chad Reitsma
Chad Reitsma Frågans ägare
more options

Vald lösning

Found this guide *Works! https://betterprogramming.pub/trusted-self-signed-certificate-and-local-domains-for-testing-7c6e6e3f9548

Ändrad av Chad Reitsma