Maybe I’m missing something, but if they generate and manage the private key, then they are in a much better position to complete the challenge than you are.
It’s completely backwards that they control the web server and DNS and then make you send in a CSR and hand them a certificate. It’s their job and they have much better control. Their suggested workflow seems oddly awkward.
I agree with both @WinstonSmith that the workflow they propose is not really optimal (they could do it themselves more easily) and with @ahaw021 that ZeroSSL is likely to satisfy their proposed workflow. Remember that you’ll have to repeat this process at least every three months! Maybe you could also ask them at the same time whether they would be prepared to set up some kind of automation on the hosting side for you, or otherwise deepen their level of support for Let’s Encrypt.
Thank you Winston, I appreciate your comments, but in Pair’s defence, they say they are working on implementing the automated incorporation of LE, meanwhile they are charging for their own PairSSL service to take this chore off the hands of punters like me
I have already written privately to Kevin (who owns pair) to nudge him to do the best thing, and I’m sure he will soon.
Okay, I’m making progress.
I created the challenge file and put it in the public directory as designated by zerossl.com, and pressed the NEXT button, and it worked, I got the Domain-crt.txt which I have now emailed to Pairssl to install for me.
They are just waking in Pittsburgh on Sunday morning, so we still need patience
I have already switched all my html files to https on my desktop HD ready to upload once the cert is installed and site switched to enable ssl.
Actually, passing the challenge was easy, after I realised +I+ was supposed to make the challenge directory in my own public directory (I’d been waiting, assuming Pair had to put that somewhere I don’t have access.)
Perhaps I also misunderstood about Certbot too, I’ll check again if I can install that in my own shared web space at Pair, but the Cerbot webpage is daunting to non-geeks like me and your Zerossl.com suggestion was what got me along the way.
Everything is functioning as it ought to, and we are now listed in the major SE’s as an https site for the first time, which boosted us to the top of our niche in G, even above their beloved Wikipedia page
I’m just wondering if this entry in my site raw logs is anything to do with using LE and Zerossl?
(I edited the full IP and removed the time) The IP is Savvis/ Qualys:
Let's Encrypt? Not directly. ZeroSSL? I don't know, maybe.
Someone -- maybe you? -- must have run Qualys's SSL Labs test on your website. (It's a great service!) I haven't used ZeroSSL, so i don't know if it automatically does an SSL Labs scan, or encourages you to.
If you posted your site name and an HTTPS related issue on the forum, one of the other posters here might have done it to help determine what was going on. (This thread was about getting a certificate, rather than something going wrong while trying to use a certificate you already have, so that sounds unlikely.)
BTW: The owner of Pair.com has replied to my email confirming they will soon have LE automated for all accounts, and are running a special offer including SSL for free. (I can’t see that on their site or in their newsletter, so maybe it is a Special Offer in the pipeline?)
To clarify - ZeroSSL does not do any outbound connections. The online client runs in your browser and the only connections established are between your browser and Let's Encrypt API endpoints. Let's Encrypt verification servers may request specific verification files if you have selected HTTP verification method, but that's it.
Looking at the address there, that is definitely Qualys netblock, so indeed @PeaceComesFree seems to have run a check on himself
P.S. Personally I find Qualys check rather useful, however I believe it targets users with a certain level of knowledge, so for those less technically aware I would probably recommend Mozilla SSL Configuration Generator and Cipherli.st as proper starting points regarding configuring the server in the right manner.