Project Settings
Last updated
Was this helpful?
Last updated
Was this helpful?
When working with an Umbraco Cloud project, you can handle the project configuration directly in the Umbraco Cloud Portal. You can manage the following configurations from the left-side menu:
The Environments section provides an overview of your project’s environments. Here, you can:
Access the Website (frontend) and backend,
Open Kudu, and
Clone down the environment locally.
Each environment has an error log that appears only if there are any unread errors in that specific environment. You can view the errors by clicking on Error logs in the environment menu.
In the Error logs page, you can manually mark each error as read which will move it from the "New" section to the "Read" section. Errors marked as read will be permanently deleted after 30 days.
Environment errors are stored in the UCErrorLog table.
The query below deletes 90% of the errors. The query always deletes the oldest errors first. You can tweak the query to delete any percentage of errors by changing the number in the first row.
The Team section allows you to:
Manage team members and their permissions on different environments.
Add new team members.
Monitor pending project invitations.
The Summary section displays key information such as the project plan, the region where the project was created, payment status, and more.
In the Project History section, you can view a list of high-level activities for your cloud project.
You can see metrics related to the overall health and performance of the Azure app service hosting the different environments of your solution.
The Usage section allows you to:
View the usage of Custom Domains, Media Storage, Bandwidth, and Bandwidth History for your project.
Check whether the project is using above or below the allowed amount for its plan.
View the top 10 bandwidth usage paths, referrers, and the top 50 media files.
The Connections section provides connection details for your Umbraco Cloud databases. You need to allow your IP to connect to the databases with your local machine.
The Automatic Upgrades section handles minor and patch upgrades for the Umbraco components used by Umbraco Cloud. By default, new projects are opt-in for these upgrades.
The CDN & Caching section lets you manage CDN Caching and Optimization settings for your project. You can:
Modify the default settings that apply to all hostnames added to the project.
Set specific caching settings per hostname if different configurations are required for certain hostnames.
Purge Cache for individual hostnames or all of them.
In the Hostnames section, you can bind hostnames to your Umbraco Cloud project.
You can configure deployment webhooks for your environments in this section. Webhooks are triggered upon successful deployments, and you can specify where the deployment information is sent.
The Advanced section provides options for managing advanced settings for your project, including:
Enable IIS logging for each environment. The log files can be accessed in Kudu at C:\home\LogFiles\http. IIS logs have a rolling size limit of 100 MB, overwriting the oldest files once the limit is reached.
Change the .NET framework runtime for each environment of your Umbraco Cloud project.
The Backups section enables you to create database backups for one or more of your cloud environments.
The Public access setting, found under the Security tab, allows you to deny access to your project. Users who are not part of the project or whose IP addresses have not been allowed will not be able to access the project.
You can enable or disable this setting on the Public access page. Access to manage Public access requires your project to be on the Standard plan or higher.
The Transport Security section enables you to manage transport security settings for your project. You can configure specific transport security options for all hostnames or individual hostnames within your project.
The Management API Security section allows you to secure access to the backend services of your project. This can be managed from the Security menu on the Umbraco Cloud Portal.
If you have a custom certificate, you can upload and bind it to your custom hostnames. This can be done instead of using the TLS: Transport Layer Security (HTTPS) certificates provided by the Umbraco Cloud service.
The Secrets Management section is used for storing sensitive information such as API keys, encryption keys, and connection strings used by your Umbraco Cloud project.
You can change your Umbraco Cloud project to run in a dedicated setup with additional computational resources compared to the shared setup. You can choose between different dedicated options depending on the number of resources you will need for your project.
You can upgrade your project to a Standard or a Professional plan from the Management menu, depending on your needs. The option is not available if you are already on a specific plan or if you are running in Trial mode.
You can rename your Umbraco Cloud project from the Management menu.
You can rename your project from the Rename Project section in the Management menu on the Umbraco Cloud Portal. When you rename a project, the default hostnames and clone URLs assigned to the project are updated to match the new project name. You can also rename your project files and folders locally.
You can delete your Umbraco Cloud project from the Management menu. Deleting your Umbraco Cloud project is permanent - all data, media, databases, configuration, setup, and domain bindings are removed in the process.
During development, too many errors can slow down the error page. To fix this, connect to the environment's database locally and delete the errors. Learn how to connect to the database in the section.
Manage backoffice user groups and for your project.
From this page, you can manage whether your site is automatically upgraded to the latest minor version(s) of the Cloud products. To learn more about automatic upgrades, visit the section.
for projects on Standard, Professional, or Enterprise plans.
.
Enabling IIS logging will cause the site to restart. For additional information, refer to the .
The package can be installed to enable Public access for projects created before the 10th of January 2023.
