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’.

Learn More

Wrong SSL certificate for new.thunderbird.net

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

Keazen oplossing

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.

Dit antwurd yn kontekst lêze 👍 1

Alle antwurden (3)

more options

Keazen oplossing

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.

Behelpsum?

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

Behelpsum?

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.

Bewurke troch Grass Prisoner op

Behelpsum?

In fraach stelle

Jo moatte jo oanmelde by jo account om op berjochten te antwurdzjen. Stel in nije fraach as jo noch gjin account hawwe.