Този сайт ще има ограничена функционалност, докато се извършва тече неговата поддръжка. Ако дадена статия не може реши проблема ви и искате да зададете въпрос, нашата общност е готова да ви помогне на @firefox в Twitter и /r/firefox в Reddit.

Avatar for Username

Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

Тази тема беше архивирана. Моля, задайте нов въпрос ако имате нужда от помощ.

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

  • 3 отговора
  • 1 има този проблем
  • 1 изглед
  • Последен отговор от 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.
Прикачени екранни снимки

Избрано решение

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

Прочетете този отговор в контекста 👍 0

Всички отговори (3)

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

Could be this issue:

Chad Reitsma
Chad Reitsma Задаващият въпроса
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 Задаващият въпроса
more options

Избрано решение

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

Променено на от Chad Reitsma