Skip to main content

SSL for Hosted customer with their own domain name

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


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
A real-world example is filewave.anglehealth.com and below is the CNAME created:
_acme-challenge.filewave.anglehealth.com IN CNAME _acme-challenge.anglehealth.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.anglehealth.com. 3600    IN    A    34.236.200.223
But just create a Ticket for Cloud Team in IT Service Desk and Cloud will run through the process.
Back to top