Echo thanks to Mike.
On Sun, Jun 17, 2012 at 10:39 AM, Gordon Joly gordon.j...@pobox.com wrote:
On 17/06/12 09:46, Michael Peel wrote:
But who is actually responsible? Jon Davies? Or another member of staff?
Right now, me as a volunteer. The responsibility will soon be
transferred to
On 15/06/12 09:25, Michael Peel wrote:
Thanks for the reminder of this. I've implemented a work-around for
now (moving direct debit processing over to donate.wikimedia.org.uk
http://donate.wikimedia.org.uk and switching to only having SSL on
that subdomain) - we'll get a better solution in
On 17 Jun 2012, at 09:16, Gordon Joly gordon.j...@pobox.com wrote:
On 15/06/12 09:25, Michael Peel wrote:
Thanks for the reminder of this. I've implemented a work-around for now
(moving direct debit processing over to donate.wikimedia.org.uk and
switching to only having SSL on that
On 17/06/12 09:46, Michael Peel wrote:
But who is actually responsible? Jon Davies? Or another member of staff?
Right now, me as a volunteer. The responsibility will soon be
transferred to a full-time developer post that we're just about to
advertise for, though (see
Thanks for the reminder of this. I've implemented a work-around for now (moving
direct debit processing over to donate.wikimedia.org.uk and switching to only
having SSL on that subdomain) - we'll get a better solution in place before the
next fundraiser. Please could you check that it's working
On Fri, Jun 15, 2012 at 4:25 AM, Michael Peel
michael.p...@wikimedia.org.uk wrote:
Thanks for the reminder of this. I've implemented a work-around for now
(moving direct debit processing over to donate.wikimedia.org.uk and
switching to only having SSL on that subdomain) - we'll get a better
If you go to http://donate.wikimedia.org.uk/ you can donate… insecurely.
If you go to https://donate.wikimedia.org.uk/ you can donate… but you get an
SSL certificate error.
This seems like a problem.
(Whoops, sent this to Wikimedia-L rather than Wikimediauk-L.)
--
Tom Morris
Yeh I raised this a few weeks ago; and I recall someone else did then.
It's due to misconfigured SSL on the server (setting up a server the handle
multiple SSL certificates can be a pain).
I'm not sure what the status of it being fixed is; but I did offer advice
back then on how to go about it.
