I think the licensing update in Confluence 7.17.0 broke Server Timebomb licenses.
Both the license listed on https://developer.atlassian.com/platform/marketplace/timebomb-licenses-for-testing-server-apps/ under 3 hour expiration for all Atlassian host products, as well as the instances pulled up with
atlas-run(-standalone) are not accepted by the code as valid licenses. Therefore, Confluence refuses to start / accept it during setup:
Steps to reproduce:
- With the latest version of the
atlas-run-standalone --product confluence, wait until the instance is started then access it using the link given in the output.
- Or: Start setting up Confluence as a standalone instance and give the license posted on the aforementioned page that contains all public timebomb licenses. Setup will reject that license.
Workarounds known to me:
- Use a (single-node) DC instance with a proper license, or
- a proper Server (prod or dev) or
- an eval license or
- use a lower version of Confluence (≤ 7.16.x)
I think this should probably be fixed, be it that the licensing code in 7.17.1 or something actually accepts the server timebomb licenses again or that the data image that
atlassian-plugin-sdk pulls, actually provides a DC timebomb license.
- Error in Web UI: “License Inconsistency: Your current license will not work with this version of Confluence.”
- Error in Setup Web UI: “The product license youre using is not legitimate. Contact your license issuer.” [sic]
- Errors in Logs:
com.atlassian.confluence.license.exception.LicenseException: Failed to retrieve license from storage.
retrieveFromStorage Unable to parse license string: Failed to verify license hash: missing property licenseHash
Unable to retrieve license. Your current license will not work with this version of Confluence. You'll need to supply a valid license key. Confluence can't start without this. If you have a new license, please enter it on this page (/fixonly/fixlicense.action) and restart.
PS: Visiting the page to fix the license also does not work for me: