Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Wrong SSL certificate for new.thunderbird.net

Grass Prisoner
Grass Prisoner
more options

I keep getting the prompt* about new.thunderbird.net expiration.

Indeed, after opening https://new.thunderbird.net in Firefox, the subdomain uses the Let's Encrypt SSL certificate that expired on 22nd May 2024. This certificate list many subdomains by name.

For https://www.thunderbird.net (after opening it in Firefox), another SSL certificate file is used (issued by Google Trust Services LLC by on 13 May 2024) valid until 11 Aug 2024. It says it should apply to thunderbird.net and *.thunderbird.net, but the new.thunderbird.net still points to the old Let's Encrypt certificate perhaps?

  • I know I could just allow the expired one as an exception
I keep getting the prompt* about new.thunderbird.net expiration. Indeed, after opening https://new.thunderbird.net in Firefox, the subdomain uses the Let's Encrypt SSL certificate that expired on 22nd May 2024. This certificate list many subdomains by name. For https://www.thunderbird.net (after opening it in Firefox), another SSL certificate file is used (issued by Google Trust Services LLC by on 13 May 2024) valid until 11 Aug 2024. It says it should apply to thunderbird.net and *.thunderbird.net, but the new.thunderbird.net still points to the old Let's Encrypt certificate perhaps? *I know I could just allow the expired one as an exception

Chosen solution

So your post in the Thunderbird support forum has nothing to do with Thunderbird, but something to do with the web infrastructure used by the project. If that assumption is correct the best place for your comment/question would be best posted in the github repository for the web site. https://github.com/thunderbird/thunderbird-website/issues

Sorry but no one here has anything to do with the web presence.

Read this answer in context 👍 1

All Replies (3)

Matt
Matt
  • Moderator
  • Top 10 Contributor
more options

Chosen Solution

So your post in the Thunderbird support forum has nothing to do with Thunderbird, but something to do with the web infrastructure used by the project. If that assumption is correct the best place for your comment/question would be best posted in the github repository for the web site. https://github.com/thunderbird/thunderbird-website/issues

Sorry but no one here has anything to do with the web presence.

Helpful?

Grass Prisoner
Grass Prisoner Question owner
more options

Thank you for replying and for the information you've provided.

That's a shame though, as I don't have a Microsoft account. Hopefully somebody who searches here for the issue they experience (the reason I brought it up) will have an account and would post an Issue on GitHub.

Regards

Helpful?

Grass Prisoner
Grass Prisoner Question owner
more options

I've marked the topic as solved, because I think it should not attract attention from the moderators here any longer.

I believe that only a person experiencing the same issue (and thus searching for it here) will be motivated enough to actually post the Issue on GitHub. That person will find this topic in the search results regardless if it's "open" or "solved".

Obviously though, as for 2024-06-19, the issue is not solved — Thunderbird still receives an expired certificate and informs the user about it in a prompt.

Modified by Grass Prisoner

Helpful?

Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.