[bug]: Unable to assign License

[pwannenmacher]

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

I run Plane.so and use the image makeplane/plane-aio-commercial:stable. I would like to link an unlinked licence (visible on prime.plane.so) to a workspace. Unfortunately, this results in the following behaviour:

1. In the workspace settings, I click on ‘Billing & Plans’, then on Activate this Workspace. After I’ve entered the licence key and submitted it, I get the message ‘Payload is not valid’. Interestingly, from this point onwards, the key is linked to this workspace on prime.plane.so.
2. If I now click on sync plan under Workspace Settings > Billing & Plans, a sync error occurs
   There are no entries in the Docker logs for either of these actions. The browser console displays the following:

XHRPOST
https://project.frachtwerk.de/api/payments/workspaces/eps/licenses/
[HTTP/2 400 4673ms]

worklog -> updateWorklogById -> error 
Object { error: ‘The payload is not valid’ }
<anonymous code>:1:147461
XHRPOST
https://project.frachtwerk.de/api/payments/workspaces/eps/license-refresh/
[HTTP/2 400 5356ms]

selfHostedSubscriptionService -> syncLicense -> error 
Object { error: ‘The payload is not valid’ }
<anonymous code>:1:147461

Steps to reproduce

See above

Environment

Production

Browser

Mozilla Firefox

Variant

Self-hosted

Version

v2.6.3

[makeplane]

Synced with Plane Workspace 🔄

[GIT-278] [bug]: Unable to assign License

[danciaclara]

@pwannenmacher Could you try these steps?

1. Delink the license key from the Prime portal.
2. Update your image tag from :stable to the release version. In your compose file, change:
   artifacts.plane.so/makeplane/plane-aio-commercial:stable
   to:
   artifacts.plane.so/makeplane/plane-aio-commercial:v2.6.3
   Pinning to v2.6.3 ensures you're running the exact version.
3. Restart the instance
4. Reactivate the license key once the instance is back up.

If the above doesn't resolve the issue, you can try deleting the monitordb from the local path on the left side of the colon in your volume mount (-v /path/to/monitordb:/app/monitor) and then redeploy Plane.

Also, we'd strongly recommend migrating to Docker Compose for production use. The AIO image is simpler to get started for testing, but doesn't scale as well.

[pwannenmacher]

@danciaclara Steps 1–4 did not work. Afterwards, exactly the same behaviour was observed.

It was only possible to activate the system after deleting the monitor database. Thank you very much for your help.

Is there a migration guide for moving from AIO to the Docker Compose version? Ideally, Plane would not be installed via https://prime.plane.so/install/, but would be included in a single Docker Compose file (with a .env file if required).