Why do add-on developer licenses not work on Confluence Server with Starter License?
Asked by Timo Lagus:

I have two Confluence Servers on the Starter License, one for production and the other for development/staging.

I recently updated the production server and its add-ons with renewed production licenses. Everything went fine.

Since I could not find a new developer license for the Starter License, I tried using the production license also for the staging server. Seemed to work fine at first. However, when I updated the staging add-ons with their developer licenses, I got the following error message for each add-on:

***License successfully updated, but the license is invalid. Click Buy now to get a valid license.***

And the license status changed to:

***Incompatible with product license (wrong type)***

I then learned that you now need a separate license for staging with the Starter License, so I bought a second Starter License for the staging server and successfully applied it.

But the same add-on developer license errors persist. Even after I remove and then reapply a license.

What gives? Why can't I apply my valid add-on developer licenses on my staging server, which use a valid Starter License?


Answers:
author: Timo Lagus
body: Seems like you need to purchase your add-ons twice if you want to have both a production and a staging instance with the Starter License, since a commercial server license only works with commercial add-on licenses, and ditto for developer licenses.


author: Timo Lagus
body: Hi [@Ismael Jimoh](/t5/user/viewprofilepage/user-id/1214168),

Confluence Server Starter License does not include a developer license anymore. You cannot get a developer license from My Atlassian. Basically, if you want to have separate production and staging servers on a Starter License, you need two separate Starter Licenses for Confluence Server.

Which is what I currently have.

However, you still get the normal developer licenses as part of the add-on licenses. For some reason, though, my add-on developer licenses are invalid for my staging server.

Btw., I'm the technical contact, so I can view/generate the developer licenses for the add-ons.

Cheers,

Timo

comments: author: Ismael Jimoh
body: Sorry [@Timo Lagus](/t5/user/viewprofilepage/user-id/1154045)

I wasn't aware of this change. I belive atlassian or some other member of the community more familiar with this change would need to comment on this.

* Please does anyone in the community have an idea on what to do in a scenario like this?


author: Timo Lagus
body: Based on the error messages I'm getting from some of the paid add-ons, the problem seems to be that their developer licenses need to match a Confluence Server developer license, rather than a Confluence Server production license. But since I can't get a separate developer license with a Starter License...


author: Ismael Jimoh
body: Hi [@Timo Lagus](/t5/user/viewprofilepage/user-id/1154045)

You cannot use a production and development license together in Atlassian products.

My recommendation is to get the developers license for the new production license from my.atlassian.com.

This though can only be done by the technical contact listed on the production license.

comments: author: Ismael Jimoh
body: <https://confluence.atlassian.com/jirakb/how-to-get-a-jira-developer-license-744526918.html>

The steps listed here also apply to confluence.


Tags: confluence-server

server