Error from https://www.wikiapiary.com :
www.wikiapiary.com uses an invalid security certificate. The certificate is only valid for wikiapiary.com
The non-www domain name works correctly.
(Splitting this issue off from T191004.)
Samwilson | |
Apr 15 2018, 9:09 AM |
F18839549: pasted_file | |
Jun 6 2018, 2:45 PM |
F18834102: image.png | |
Jun 6 2018, 12:21 PM |
F18834109: image.png | |
Jun 6 2018, 12:21 PM |
Error from https://www.wikiapiary.com :
www.wikiapiary.com uses an invalid security certificate. The certificate is only valid for wikiapiary.com
The non-www domain name works correctly.
(Splitting this issue off from T191004.)
Still cannot access the website.
Cert only valid for wl.wikiapiary.com, and you serve HSTS. You must also set a cert for www.wikiapiary.com and wikiapiary.com for backward compatibility.
It shows to me:
This request was sent to MediaWiki, and there is no configuration for www.wikiapiary.com.
Are you sure you are connected to https://www.wikiapiary.com? http version also works on my other browser, but if someone ever visited the https version, HSTS will prevent them connecting to http version.
Oh, you’ve set an local exception. That’s not a solution nor workaround imo - I don’t think setting an exception to https failure is an ideal way to handle certificate failure.
And that (no MW) seem to be other bug.
We are currently aware of this issue but are unable to do anything to fix it at the moment due to Bastion host maintenance. As soon as the resets[1] are finished we will have access to the servers again and will be able to resolve this.
[1]https://lists.wikimedia.org/pipermail/cloud-announce/2018-May/000050.html
We have regained access to the Bastion host and are working to resolve this issue.
Basil
From: "revi" <no-reply@phabricator.wikimedia.org>
To: "basil" <basil@everybody.org>
Sent: Wednesday, June 6, 2018 10:48:30 AM
Subject: [Maniphest] [Commented On] T192226: Invalid security certificate for www.wikiapiary.com
revi added a comment.
Oh, you’ve set an local exception. That’s not a solution nor workaround imo - I don’t think setting an exception to https failure is an ideal way to handle certificate failure.
And that (no MW) seem to be other bug.
TASK DETAIL
[ https://phabricator.wikimedia.org/T192226 | https://phabricator.wikimedia.org/T192226 ]
EMAIL PREFERENCES
[ https://phabricator.wikimedia.org/settings/panel/emailpreferences/ | https://phabricator.wikimedia.org/settings/panel/emailpreferences/ ]
To: DeepBlue, revi
Cc: Nikerabbit, TerraCodes, Liuxinyu970226, revi, MarkAHershberger, DeepBlue, Aklapper, Samwilson, lucamauri, Zylc, 1978Gage2001, Chicocvenancio, Tbscho, JJMC89, srodlund, Gryllida, scfc, Kghbln, Krenair, Dzahn, chasemp