14

The certificate presented does not work for stackpromos.com, leading to a warning in my browser about an invalid certificate.

Invalid certificate for stackpromos.com; issued to *.stackexchange.com

|improve this question
  • Ah right, I misremembered what the core of your report here was. :) Issuing a valid cert for that domain is planned on the SRE team, but there's no ETA at the moment. – Adam Lear♦ Dec 13 '17 at 19:23
10

My bad.

Word on the street is stackpromos.com probably isn't supposed to have a valid cert, but I linked it in the blog post as https out of habit. Will fix as soon as I can get the blog post edited!

Update: Fixed.

|improve this answer
  • 1
    So, who should we ping this year to get a secret hat? ;) – Shadow The Curly Braced Wizard Dec 13 '17 at 15:58
  • Still not working here FWIW... – rogerdpack Dec 13 '17 at 18:00
  • 1
    @rogerdpack There not being a cert is by design - the error that I fixed was linking to https in the Winter Bash blog post, leading everyone on a certificate wild goose chase. – hairboat♦ Dec 13 '17 at 19:09
  • 2
    The SRE team has "add a cert to stackpromos.com" on their list, but it's not high up on the priority list at the moment since the domain is basically just a read-only museum of past promos, if you will. – Adam Lear♦ Dec 13 '17 at 20:51
  • @AdamLear I will. – hairboat♦ Dec 20 '17 at 1:51
1

We now route this through another provider for the redirect and serve a valid cert. Sorry it didn't happen immediately - it was a "minor" domain and just wasn't the highest priority at the time.

|improve this answer
0

This is no longer relevant, since stackpromos.com domain does not exist anymore, and redirecting to https://contests.stackoverflow.com instead, which being part of stackoverflow.com domain, gets its https cert.

|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .