Skip to main content

Configuring Your Custom Domain

There are 3 major pieces that must be set up to correctly configure a primary custom domain for your Files.com site.

Once you have decided upon the address you will use for your custom domain, you will need to set up a DNS CNAME record for your custom address. This CNAME record is used to resolve your custom address to the Files.com platform.

The TLS/SSL Certificate associated with your site is served by the platform to secure the connection, whether by web, API, FTPS, or WebDAV. You can either use a Files.com-provided certificate (strongly recommended) or provide your own custom certificate. Allowing Files.com to manage your SSL certificate alleviates the effort of obtaining your certificate or keeping it up-to-date.

You will need to configure the site-wide setting for Custom Domain in your Files.com site in order to activate the custom domain features, such as dedicated IP addresses.

Selecting A Custom Domain Name

You can use any subdomain of any domain that you control as your primary custom domain. We recommend not using "ftp" as the first part of your domain (such as ftp.<your-domain>), since this will cause some browsers to improperly access the Files.com web interface. Instead, we suggest using something like files.<your-domain>. For instance, if you control the example.com domain, you might use the custom name files.example.com.

Custom Domain and SSO

Adding a custom domain does not affect your Single Sign-On (SSO) integrations, and no change is needed in your IdP. If the Relay State field in your IdP names your Files.com subdomain, Files.com still identifies your site from it, because the subdomain is still one of your site's hostnames. You can change the field to your custom domain if you prefer, because both hostnames identify the same site.

If the Relay State field names a custom domain that you later change or remove, IdP-initiated logins fail until you update the field, and SP-initiated logins are not affected.

Adding Multiple Custom Domains

Once you've configured your primary custom domain, you can define additional custom domains. The other custom domains can be used just for specific purposes, like rebranding your S3-compatible API endpoint, or changing the domain used for Public Hosting.