License not working in dockerized Directus 12.0.2

[stx-chris]

Describe the Bug

When Directus is started in Docker and the license key entered under Settings -> License -> Add License, I am getting the following error:

{
  "service": "license",
  "reason": "Invalid URL",
  "stack": "DirectusError: Service \"license\" is unavailable. Invalid URL.\n    at handleLicenseError (file:///directus/node_modules/.pnpm/@directus+api@file+api_@opentelemetry+api@1.9.0_@opentelemetry+core@2.1.0_@opentelemetr_4fe57fc2f23b0f156ebf7487ebe3f888/node_modules/@directus/api/dist/license/utils/handle-license-error.js:34:8)\n    at LicenseManager.preview (file:///directus/node_modules/.pnpm/@directus+api@file+api_@opentelemetry+api@1.9.0_@opentelemetry+core@2.1.0_@opentelemetr_4fe57fc2f23b0f156ebf7487ebe3f888/node_modules/@directus/api/dist/license/manager.js:167:4)\n    at process.processTicksAndRejections (node:internal/process/task_queues:103:5)\n    at async file:///directus/node_modules/.pnpm/@directus+api@file+api_@opentelemetry+api@1.9.0_@opentelemetry+core@2.1.0_@opentelemetr_4fe57fc2f23b0f156ebf7487ebe3f888/node_modules/@directus/api/dist/controllers/license.js:71:18",
  "code": "SERVICE_UNAVAILABLE"
}

similar errors appear when providing the license key as LICENSE_KEY or LICENSE_TOKEN.
P.S. PUBLIC_URL set to a publicly accessible address.

To Reproduce

1. Start Directus directly from Docker image directus/directus:12.0.2
2. Login
3. Enter license key
4. See error: "Invalid license...." and the failed request in the Network tab

Directus Version

v12.0.2

Hosting Strategy

Self-Hosted (Docker Image)

Database

PostgreSQL 16

[linear-code]

CMS-2662

EDU-526

[stx-chris]

ok, seems it has to do with the licensing system requiring not having NODE_ENV = development.
So, setting NODE_ENV = production solved the issue.

When NODE_ENV = development is set, the licensing issue occurs. This limitation should be put in the docs. May I also recommend adjusting the error message accordingly? There is no way I could have found out by myself on the basis of the errors I was given alone.

[JamesW1]

Hi @stx-chris - yes, as pointed out over on the community forum, it's a symptom of running the app in dev mode (and trying to use a production license).

Seeing us a few people are running into this issue, we're going to make some changes our side to avoid this happening (even when NODE_ENV = development.