Skip to main content

Deploy license pending after upgrading to v17

Keywords: Umbraco 17, Umbraco Cloud, Umbraco Forms, Umbraco Deploy, Upgrade, UMBRACO-CLOUD key, Version-specific upgrade

Written by Joana Knobbe
Updated over a week ago

Introduction

This guide outlines common causes and actionable steps to resolve this issue, ensuring smooth deployment processes.

Licensing issues can also arise after upgrading to a new version of Umbraco, often due to incomplete post-upgrade steps or temporary browser-related problems.

General Troubleshooting Steps

  1. Verify Default Domain Settings: - Ensure the default umbraco.io domain for your Umbraco instance is correctly set up. - Assign the default domain to the root node of your Umbraco project. - Publish the root node to make it active. - Confirm that accessing the default domain returns an HTTP 200 status code. - It’s crucial for the site to respond with a status code of 200 to validate the license successfully. Once validated, the pending state should clear.

  1. Clear Browser Cache: - If you encounter a message about an invalid or missing license, clear your browser cache and refresh the page. Alternatively, try accessing the backoffice using a different browser.

Environment-Specific Guidance for Umbraco v17

For deployments on Umbraco v17, additional license configuration steps may be required:

These licensing issues are not limited to v17 deployments but can also occur after upgrading to newer versions of Umbraco.

  1. Update the Deploy License Key: - Verify that the Deploy license key is correctly set in the appSettings.config file. - Ensure the key is placed under the correct section and uses the appropriate format as per v17 guidelines.

  2. Restart the Environment: - After updating the license configuration, restart the environment to apply changes effectively.

  3. Retry Deployment: Once the environment has restarted, retry the deployment to confirm that the issue is resolved.

Common Pitfalls and How to Avoid Them

  • Incorrect Domain Configuration: Failure to assign or publish the default domain to the root node can prevent the site from returning a 200 HTTP status code.

  • Misconfigured License Key: Ensure the appSettings.config file is updated with the correct key format, especially in Umbraco v17. Double-check the key placement in the configuration file.

  • Browser Cache Issues: Temporary browser cache problems can sometimes cause licensing errors. Clearing the cache or using a different browser often resolves these issues.

Umboto’s Pro-Tip:

When you're upgrading an Umbraco Cloud project to Umbraco 17, there is a specific configuration requirement that isn't currently listed in the standard version-specific upgrade documentation.
​

The Issue: Umbraco 17 expects a specific identifier to recognize the project as being hosted on Umbraco Cloud. If this is missing, you might encounter issues during the in-place upgrade process.
​

The Fix: You need to ensure that "UMBRACO-CLOUD" is set as the key for your Cloud project configuration.
​

Helpful Resources:

  • Community Discussion: You can find more details and developer experiences regarding this specific V13 to V17 transition on the Umbraco Forum here.

  • Official Docs: While this specific key might be missing, always keep the Version-Specific Upgrade Guide open for the rest of the journey!

Upgrading can be a bit of a trek! If your Cloud project seems a bit lost after moving to V17, double-check that "UMBRACO-CLOUD" key—it's like giving your project its passport to the Cloud. Happy coding! 🚀

Did this answer your question?