Yes. Utter utter utter utter pain.
And I may have screwed something up ... server went down / just looking to see if it was a co-incidence
I think it was a co-incidence; I was worried having rebuild the program that serves the site (the Apache web server) to include
SSL▸ modules. I am, however, aware that if you now try and access the Coffee Shop through https - which previously was not available - you're now likely to get a warning from your browser in very concerning words (which actually
needn't be concerning in this case). Big thanks to the for member who alerted me and made constructive suggestions - I'm following up, but with a config change (if I can work it out) to change the certificate to per-domain; our server has some 20 and I want to see https in use in due course for the coffee shop too.
First https site on the server:
https://www.melkshamremembers.org.uk - nothing to do with Transport ...