I wonder why SSL is not turned on by default when creating a custom domain mapping. As soon as a custom domain is added and configured correctly, an SSL certificate through the current Let's Encrypt technology should procure a valid certificate and install it automatically. At minimum custom domain mapping should create the request to add a certificate since ideally website should be created with SSL by default today and removing an SSL certificate should be the custom request, rather than the opposite.

Hi, Russell!

Sorry for the delayed reply. All you need is to setup your domain name, using this help page: https://help.wildapricot.com/display/DOC/Custom+domain+setup. After this done, please, get in touch with our support team: support@wildapricot.com in order to install "Let's Encrypt" certificate for your domain (please, provide your domain name or WA account ID).

Is there documentation on how to set this up?

Hi, Jared!

You can get in touch with our support team, and we'll change "Your secure site URL" with "www.domain.org". Please, prodive your domain name or WA account ID.

Thank you for the hard work! We enabled Let's Encrypt today and the browser does show it is secure. I sent an email to support a few min ago as I noticed our "primary domain" in WA is www.domain.org (with the www) but after installing Let's Encrypt my "Your secure site URL" is https://domain.org (without the www)
It seems the Let's encrypt process is not taking into account the www.

Thanks!

Hi, Tom!

LE integration is now entering testing stage. If you want to participate, and help us with "alfa-testing", just let me know ( security.crew@wildapricot.com I'll need your custom domain name only), and I'll install your free LE certificate within couple of days. Make sure you did all the steps described here: https://help.wildapricot.com/display/DOC/Custom+domain+setup.

Production version of the integration will be available within month or two.

Best regards!
Serj, from Security Crew.

Can we have an update? When is the Let's Encrypt certificate implementation supposed to be available?

Hi, Maren!

Sorry for the delayed reply. At the moment, LE integration is still undergoing development stage. It will probably enter testing stage in a couple of weeks and be made available to our clients within one or two months.

Best regards!
Serj, from Security Crew.

One of the biggest bummers in my organization's transition to WA is that there is not encryption for our custom domain. I have used LE for various websites in the past, so I thought it would be a great solution. Unfortunately, WA isn't there yet. I will need to get the SSL cert to our site in the next week or so. Is there any update as to compatibility status?

Any estimate on the timeframe for let's encrypt? Since google pushed out the "not secure" notification by the address bar in chrome, this has become a larger issue.

Lets Encrypt sounds like a no-brainer.
I understand there is no annual fee for multi-year plans, only the initial install.

Let me clarify:
- $50 is per installation, not per year
- let's encrypt is going to be free and automatic, no money to pay to Wild Apricot per year

Edward: I believe the documentation says $50 per certificate installation.

I can understand a fee to install the NameCheap SSL but if the certificate is good for three years, why would WA charge a fee for the 2nd and 3rd years?

yes.

If we go with namecheap do we still incur the reoccurring yearly wild apricot ssl fee as well?

We just bought our SSL from Namecheap, and it is working fine. $27 US for a 3 year certificate. Warranty is $10,000 which is plenty for our small non-profit club.

$145 per year to DigiCert is fine for those who need more, but I'm sure others might be interested in a cheaper option. While WA is working on a Let's Encrypt option, it would be nice to mention a cheaper option in the documentation. There's an advantage to WA in that a new SSL only needs to be loaded once every three years.

Please enable Let's Encrypt

Unfortunately if you use the free WA certificate with your custom domain names AND set SSL to always then the links in the receipt emails are broken. I reported this as a bug and was told this wasn't a bug but that I needed a custom SSL certificate to fix it.

So I got a custom certificate for one of our web sites and have started the process for two others. My experience, plan on at least a week to get a certificate in place. WA support is SLOW.