# Developer Edition API show\_license returns isExpired: true after applying new license

**URL:** <https://community.sonarsource.com/t/developer-edition-api-show-license-returns-isexpired-true-after-applying-new-license/182778>\
**Category:** SonarQube Server / Community Build\
**Tags:** sonarqube\
**Created:** [May 22, 2026, 3:54pm UTC](https://community.sonarsource.com/t/developer-edition-api-show-license-returns-isexpired-true-after-applying-new-license/182778 "2026-05-22T15:54:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Matheus\_Barone](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/matheus_barone/32/76344_2.png) [@Matheus\_Barone](https://community.sonarsource.com/u/Matheus_Barone)\
**Post date:** [May 22, 2026, 3:54pm UTC](https://community.sonarsource.com/t/developer-edition-api-show-license-returns-isexpired-true-after-applying-new-license/182778/1 "2026-05-22T15:54:31Z")

</div>

Hello all,

We are currently experiencing an issue where a newly applied license is not being picked up by our SonarQube instance. Even after applying the new license and performing resets, the system still registers as expired.

Environment Details:

- SonarQube Version: v2025.4.2 (112048)

- Edition: Developer Edition

- Deployment: Kubernetes / Pod-based

Symptoms: When querying the `api/editions/show_license` endpoint, the response still reflects the old expiration state:

- `isExpired: true`

- Expiration date: `"2026-05-11"`

Troubleshooting Steps Taken: Our team has already exhausted the following internal steps to try and force the system to recognize the new license:

1. Attempted to reset the license manually.

2. Redeployed the Sonar instance completely.

3. Performed a clean restart of the Sonar pod.

Despite these steps, the API still returns the expired status.

**In the UI it shows “ACTIVE”.**

Has anyone encountered a similar issue where the license state gets stuck, or are there specific cache-clearing steps or logs we should investigate to see why the new license isn’t taking effect?

Thank you in advance for your help!

---

<div class="post-metadata">

**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\
**Post date:** [May 28, 2026, 7:42pm UTC](https://community.sonarsource.com/t/developer-edition-api-show-license-returns-isexpired-true-after-applying-new-license/182778/2 "2026-05-28T19:42:17Z")

</div>

Hi,

Welcome to the community and thanks for this report!

To verify: you recently received this license from your sales contact? And how have you applied it? Via the UI?

&nbsp;  
Thx,  
Ann

---

<div class="post-metadata">

**Author:** ![andres](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/andres/32/76342_2.png) [@andres](https://community.sonarsource.com/u/andres)\
**Post date:** [May 29, 2026, 9:34am UTC](https://community.sonarsource.com/t/developer-edition-api-show-license-returns-isexpired-true-after-applying-new-license/182778/5 "2026-05-29T09:34:24Z")

</div>

Hi @Matheus_Barone, is your license formatted like `XXXX-XXXX-XXXX-XXXX` or does it look more like a base-64-blob type of thing? The reason I’m asking is that [there are 2 types of licenses](https://docs.sonarsource.com/sonarqube-server/2025.4/instance-administration/license-administration), and the type of issue you’re having could depend on this.

Regarding logs, a starting point would be to check if there are errors in the [server logs](https://docs.sonarsource.com/sonarqube-server/2025.4/server-update-and-maintenance/troubleshooting/server-logs) right after applying the license, particularly in `web.log`. `access.log` is useful if you are doubting whether the request (`POST /api/editions/set_license`) actually made it to the server.