SSL for Hosted customer with their own domain name

What is this

This process can let you have a DNS name controlled by the customer and have Let's Encrypt manage the SSL certificate.

It may be that the SSL service has a small fee of like $50/yr in the future. With GoDaddy selling $70/yr SSL it would seem like $50/yr is reasonable for convenience and would cover any development support we need for the feature to be maintained. I doubt we'd charge more and I doubt customers will mind since they might be saving money if they don't have another reason to have like a wildcard SSL which is more expensive than $70/yr anyway from GoDaddy but just keep in mind that a customer might have a charge for this in a future renewal and of course they could go back to their own SSL if they wanted to but this service should be cheaper and automated.

https://filewave.atlassian.net/wiki/spaces/CLOUD/pages/426999837/SSL+Certificate+Management+with+Custom+Domains#Solution-Description

Customer needs to create a CNAME pointing to the FQDN they use for the filewave server. See this ticket for reference: https://filewave.atlassian.net/browse/IS-6789

An Example

A real-world example is filewave.forrest.com and below is the CNAME created:

_acme-challenge.filewave.forrest.com IN CNAME _acme-challenge.forrest.filewave.net

To explain the above example: On the left is the actual DNS name of the server with _acme-challenge. prepended and then the CNAME goes to the acme challenge of what would be the filewave.net if they were not using their own DNS name. If you don't know what the name should be then Cloud could help you to know what to use. Once this DNS record was created and also of course the customer had to have an A record like any other customer would then all was well. Here's the A record for this example;

filewave.forrest.com. 3600 IN A 34.236.200.223

Confused at all?

But just create a Ticket for Cloud Team in IT Service Desk and Cloud will run through the process.