You can use https://perlmonks.org/ now. You may have to confirm the cert as an exception since I think it's still using the *.pairsite.com root but it's still going to do its job. It's been available for a long time at this point.
| [reply] [Watch: Dir/Any] |
Chrome doesnt throw up flags. Says its lets encrypt x3 authority .weird that i couldnt copy paste that n cert info
| [reply] [Watch: Dir/Any] |
Then did Moses just reach the Promised Land?
All my links turned red, and upon looking closer i find myself diverted to https://www.perlmonks.org/......
is this a permanent thing now?
| [reply] [Watch: Dir/Any] |
It's confusing I sometimes get the *.pairsite.com certificate for https://perlmonks.org/ , which I have to accept manually.
Since I remember that we are using at least two servers for load balancing, my first guess is that one of the apaches has the wrong cert-file in place.
For me:
all other combinations I tried required a manual exception.
update
Forgot to test *.perlmonks.net with Firefox, but they seem to work fine with my mobile browser.
| [reply] [Watch: Dir/Any] [d/l] [select] |
dig shows 3 IPs being round robin'd (robinned?). The Let's Encrypt SAN cert works on (www\.)?perlmonks\.(org)|(com)|(net), but the pairsite wildcard cert will only work on the pairsite domain, one subdomain deep. So www.perlmonks.pairsite.com will not work, authentication wise, with either cert. 3 Servers, 8 urls, 2 certs, one of which expires every 90 days, not the most enjoyable way to spend free time, I'm sure.
| [reply] [Watch: Dir/Any] [d/l] |