github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-06 12:55:03 -05:00
Code Issues 538 Packages Projects Releases 72 Wiki Activity

[GH-ISSUE #2169] License key activation should support instance ID for idempotency #4025

New Issue
Closed
opened 2026-04-20 08:26:02 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-20 08:26:02 -05:00
Owner
Copy Link

Originally created by @RobertWi on GitHub (Dec 25, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2169

Describe the Bug

Problem:
Pangolin EE introduces recently features beyond the CE version that I want to use in my personal setup. However, when obtaining a Pangolin EE license via app.pangolin.net, each activation generates a unique instance ID. This makes the license non-transferable between server recreations, breaking infrastructure-as-code workflows where servers are routinely destroyed and recreated as in my personal use setup (e.g., Terraform destroy/apply).

Current Behaviour:

  • License activation binds to a generated instance ID
  • When server is recreated, new instance ID is generated
  • Error: "License key has already been activated with a different instance name"
  • Manual intervention required to request a license

Desired Behaviour

  • Instance ID parameter - Allow specifying a fixed instance ID during activation
  • Instance ID override - Environment variable or config to set instance ID

For example
Instance ID parameter

POST /api/v1/license/activate
{
  "licenseKey": "xxx",
  "instanceId": "pangolin-prod-001"  # Optional fixed ID
}

Instance ID override
PANGOLIN_INSTANCE_ID=pangolin-prod-001

Environment

  • OS Type & Version: (e.g., Ubuntu 24.04)
  • Pangolin version: ee-postgresql-1.14.1
  • Gerbil version: gerbil:1.3.0
  • Traefik version: 3.6.5
  • Newt version: 1.8.0

To Reproduce

POST /api/v1/license/activate
Activated license key, instance ID: {"instanceId":"46c66b9e-5ecd-46c3-9825-f4c3062c9459"}
Checking license status...
POST /api/v1/license/recheck
Checking license status...

Expected Behavior

POST /api/v1/license/activate
Activated license key, instance ID: {"instanceId":"46c66b9e-5ecd-46c3-9825-f4c3062c9459","user-Instanceid¨:¨pangolin-prod-001¨}
POST /api/v1/license/recheck
Checking license status...

Originally created by @RobertWi on GitHub (Dec 25, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/2169 ### Describe the Bug **Problem:** Pangolin EE introduces recently features beyond the CE version that I want to use in my personal setup. However, when obtaining a Pangolin EE license via app.pangolin.net, each activation generates a unique instance ID. This makes the license non-transferable between server recreations, breaking infrastructure-as-code workflows where servers are routinely destroyed and recreated as in my personal use setup (e.g., Terraform destroy/apply). **Current Behaviour:** - License activation binds to a generated instance ID - When server is recreated, new instance ID is generated - Error: "License key has already been activated with a different instance name" - Manual intervention required to request a license - **Desired Behaviour** - Instance ID parameter - Allow specifying a fixed instance ID during activation - Instance ID override - Environment variable or config to set instance ID For example Instance ID parameter ``` POST /api/v1/license/activate { "licenseKey": "xxx", "instanceId": "pangolin-prod-001" # Optional fixed ID } ``` Instance ID override `PANGOLIN_INSTANCE_ID=pangolin-prod-001` ### Environment - OS Type & Version: (e.g., Ubuntu 24.04) - Pangolin version: ee-postgresql-1.14.1 - Gerbil version: gerbil:1.3.0 - Traefik version: 3.6.5 - Newt version: 1.8.0 ### To Reproduce POST /api/v1/license/activate Activated license key, instance ID: {"instanceId":"46c66b9e-5ecd-46c3-9825-f4c3062c9459"} Checking license status... POST /api/v1/license/recheck Checking license status... ### Expected Behavior POST /api/v1/license/activate Activated license key, instance ID: {"instanceId":"46c66b9e-5ecd-46c3-9825-f4c3062c9459","user-Instanceid¨:¨pangolin-prod-001¨} POST /api/v1/license/recheck Checking license status...
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#4025
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?