Set Up

    Now that you've created a project there are a few things you may want to do to make working with your project easier. As you get ready to launch your live site there are some other considerations to take into account as well.

    Most of the set up can be accomplished by using the options from your project's Settings drop down. Some of the setup applies to all of your projects, so you'll make these updates from your profile section.

    Project settings


    Naming a Project

    When you create an Umbraco Cloud project you will get to choose your own name for the project. You will also be able to choose which color the project should have in your project overview. If you are creating a Trial project for the first time, a unique project name will be generated for you, based on the name you put in the signup-form - and a color will be chosen for you at random.

    You can at anytime change the name of your project by using the Rename project option from the Settings dropdown. NOTE: If you are working locally you need to make a fresh local clone of the project, once you’ve changed your project name.

    An Umbraco Cloud project name is unique which means if a project with the name you choose already exists, you will need to choose another name before you can create the project.

    Deleting a Project

    This does what it says. Once you've confirmed deletion of a project it is permanently removed as are all data, media, databases, configuration, setup, and domain bindings. So, make sure this is what you want.

    Domains (Hostname binding)

    You can bind any hostname to your project environments. Keeping in mind, of course, that the hostname will need to have a DNS entry so that it resolves to the Umbraco Cloud service.

    You can bind a total of 15 hostnames to each of your Umbraco Cloud environments.

    Once you add a domain to one of your environments make sure to update the hostname DNS entry to resolve to the service. We recommend setting an ALIAS record for your root domain (e.g., rather than an A record for the service IP address. Check with your DNS host or domain registrar for details on how to configure this for your domain.

    Hiding the Default Url

    Once you've assigned a hostname to your Live environment you may want to "hide" the projects default URL (e.g. for various reasons. Perhaps for SEO or just making it clear to your users that the site can be accessed using just one hostname.

    One approach for this is to add a redirect to your projects web.config. To accomplish this, add a redirect rule to the <system.webServer><rewrite><rules> section in the web.config file. For example, the following rule will redirect all requests for the projects URL to the URL and respond with a permanent redirect status.

    <rule name="Redirects to actual domain" stopProcessing="true">
      <match url=".*" />
        <add input="{HTTP_HOST}" pattern="^(.*)?$" />
        <add input="{REQUEST_URI}" negate="true" pattern="^/umbraco" />
        <add input="{REQUEST_URI}" negate="true" pattern="localhost" />
      <action type="Redirect" url="http://<your actual domain here>.com/{R:0}" 
              appendQueryString="true" redirectType="Permanent" />

    Note: This will not rewrite anything under the /umbraco path so that you can still do content deployments. You don't have to give your editors the URL, and they won't see the URL if you give them the actual domain name. This rule will also not apply on your local copy of the site running on localhost.

    Security Certificates

    You can apply certificates to your Live environment by uploading them from the Manage Domains page. Your certificates need to be .pfx format and must be set to use a password. Each certificate can then be bound to a hostname you have already added to your site. Make certain you use the hostname you will bind the certificate to as the common name (CN) when generating the certificate.

    Running your site on HTTPS only

    Once you've applied a certificate to your site you can make sure that anybody visiting your site will always end up on HTTPS instead of the insecure HTTP.

    To accomplish this, add a redirect rule to the live site's web.config in the <system.webServer><rewrite><rules> section. For example, the following rule will redirect all requests for the site URL to the secure URL and respond with a permanent redirect status.

    <rule name="HTTP to HTTPS redirect" stopProcessing="true">
      <match url="(.*)" />
        <add input="{HTTPS}" pattern="off" ignoreCase="true" />
        <add input="{HTTP_HOST}" pattern="localhost" negate="true" />
      <action type="Redirect" url="https://{HTTP_HOST}/{R:1}" redirectType="Permanent" />

    Note: This redirect rule will not apply when the request is already going to the secure HTTPS URL. This redirect rule will also not apply on your local copy of the site running on localhost.

    IP Whitelist

    You can add specific IP addresses to the whitelist to automatically allow any client from these addresses to access the frontend of your Development or Staging environments without the initial authorization dialog. This can also reduce the amount of times you or your team will need to enter your credentials in order to access your projects.

    As with all things security related, make sure you use this feature judiciously as it will allow access to your Umbraco backoffice login page without requiring the initial authentication. Of course, the Umbraco backoffice will still require authentication.

    Profile Settings



    The name that will be displayed on Umbraco Cloud


    This email address is used for logging in to Umbraco Cloud and will receive email notifications from the Umbraco Cloud Portal.

    Change password

    Change the password for your Umbraco Cloud account.

    Advanced settings

    Advanced settins


    From your profile settings you can set your timezone. This applies to the display of status messages in the Umbraco Cloud portal and makes it easier to determine the actual time a particular status was created.

    Experimental Features

    You can enable the availability of experimental features for your projects. This includes features that may not be functionally complete and are not supported by Umbraco HQ. We recommend enabling this only if you fully understand the feature you will be using or are strictly using the project as a test.

    Other Set Up Topics