Can I have a Custom Solution Hostname in Murano?

Follow

Custom Hostnames

What is a Custom Hostname in Murano?

Provided you have an Enterprise Business Tier, you can host your Murano Application at *.yourdomain.com with your Murano Business account. With this you can fully customize your Solution to represent your internet connected Product.

You will need to have purchased your own domain name first, and you will need to manage that domain through DNS or the tools that your provider gives you.

 

CUSTOM DOMAIN / HOSTNAME FAQ

Do I need SSL certificates?
In order to support your custom Solution hostname you will need to provide your own certificate for us to install on Exosite's Murano platform (see below).

Can’t you get a SSL certificate for my domain?
We can’t. The owner of the domain (*.yourdomain.com) needs to order the SSL certificate. 

So I need to give you my private SSL certificate if I want SSL on my server?
Yes. We require SSL on Exosite Murano custom Solutions. 

Do you support Wildcard certificates?
No. We require that you must have a certificate per Fully-Qualified-Domain-Name (FQDN or Common Name).

SETTING UP A CUSTOM DOMAIN / HOSTNAME PROCESS

For Enterprise Business Tiers who would like to use their own hostname instead of yourname.apps.exosite.io, the following steps are followed to set up the custom hostname.  Please contact Exosite Sales or your Account Manager for more information about this option as it is only available for accounts at certain Business Tiers.

    1. The initial Solution in Murano (exosite.io), e.g. *.apps.exosite.io, has to already have been created.
    2. Submit a ticket to us (Exosite Support) using the subject 'Custom Hostname' with your BusinessID and SolutionID in the body so we are aware of which Solution you would like updated. Also be sure to include what you are planning to have it mapped to (your custom hostname) along with any contact information in case we need to call you directly. Your FQDN should have at least two dots in it; for example, "iot.exosite.com" is a valid custom hostname, but "exosite.com/iot" is not.
    3. Your company's IT team, or whoever manages your websites, will need to generate a CSR file (Certificate Signing Request). Here are the recommended fields when generating your CSR.  Most CSR generation tools will walk you through what's needed:
      Country Name (2 letter code): e.g. US
      State or Province Name (full name): e.g. Minnesota
      Locality Name: e.g. Minneapolis
      Organization Name: e.g. the name of your company
      Organizational Unit Name (optional): e.g. Information Technology
      Common Name: (your custom domain) e.g. portal.yourdomain.com
      Email Address (optional): e.g. [email protected]
    4. Your IT team will need to send the CSR to a certificate signing authority.
    5. Your IT team then provides the SSL certificate and Private Key, in PEM format, from the certificate signing authority to Exosite through the channel negotiated with, via the ticket, Exosite Support.
    6. Exosite adds this SSL certificate to our platform.
    7. Exosite provides a DNS record for your IT team to add to your domain's DNS, along with instructions on making that change.
    8. Exosite associates the new custom hostname with your Solution. 

 

TROUBLESHOOTING

If you work with Exosite to set up a custom hostname, with all of the DNS configuration and Cert files that have to be set up, something can go wrong.  Here are some things to look for, or use.

DNS Look-up

To verify that the DNS record is set up properly, you can use the tool called dig (Domain Information Groper).  This tool will output information from DNS name servers to check that what you thought you set up is actually what was created.

 

 

 

 

Have more questions? Submit a request

Comments