Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Comments on Accessing scientific-speculation.codidact.com over HTTPS is serving a certificate for collab.codidact.org, triggering browser security warnings

Post

Accessing scientific-speculation.codidact.com over HTTPS is serving a certificate for collab.codidact.org, triggering browser security warnings

+1
−1

When I try to go to https://scientific-speculation.codidact.com/, I get a certificate warning.

Looking at the certificate details, it turns out that the server is actually providing a certificate for subject alt names collab.codidact.org only, issued by Let's Encrypt and with a not-before time of Aug 9 2021 23:30 UTC. Since collab.codidact.org isn't scientific-speculation.codidact.com, this triggers the pretty dire warning. As far as I can tell, this began Aug 16 2021 at some time between 20:00 and 20:30 (UTC).

If I choose to ignore the problem and continue, I actually do end up on Scientific Speculation, so whatever the problem is seems to be restricted to the certificate itself.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

No repro (2 comments)
No repro
Mithical‭ wrote over 3 years ago

I'm getting a certificate for *.codidact.com... try clearing your cache and try again?

Canina‭ wrote over 3 years ago

Mithical‭ It's working now, yes. It was failing in the manner I described in the question. I got the same result from several different hosts, using different software, and also with a brand new browser profile, so I dare say that it was not caching on my end.