Avatar for Username

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

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

  • 3 antwurd
  • 1 hat dit probleem
  • 195 werjeftes
  • Lêste antwurd fan Chad Reitsma

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.
Keppele skermôfbyldingen

Keazen oplossing

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

Dit antwurd yn kontekst lêze 👍 0

Alle antwurden (3)

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

Could be this issue:

Chad Reitsma
Chad Reitsma Fraacheigener
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 Fraacheigener
more options

Keazen oplossing

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

Bewurke troch Chad Reitsma op