Licensing and support

Commands here cover entitlement (AWS Marketplace and JWT-based KVM), support artifacts, and configuration/log packaging for Pixop support. Several of them handle secrets — treat stdout and generated archives as confidential.

Licensing workflow

Platform	Tooling
AWS EC2 from Marketplace	pixop-license — activation, status, `doctor`
KVM guest	JWT install at provisioning or runtime; decode/inspect with pixop-decode-jwt when debugging claims (not a substitute for legal entitlement)

Licensing problems often look like pipeline problems. Run pixop-preflight before chasing TSDuck PIDs. On AWS, pixop-license doctor is the authoritative Marketplace check; on KVM, confirm the JWT path matches your delivery note and that the guest clock is sane before re-installing tokens.

Support bundles and packaging

When opening a ticket, prefer structured collection over ad-hoc journalctl pastes:

pixop-support-bundle — curated diagnostic archive (redaction best-effort).
pixop-pack-config — configuration snapshot without full logs.
pixop-pack-logs — log-focused archive.

Review bundle contents before upload. JWTs, SRT passphrases, and environment-specific URLs may still appear despite redaction. If support asks for logs only, use pixop-pack-logs instead of a full bundle; if they need configuration without journal noise, pixop-pack-config is the lighter option.

Sensitive data handling

Do not post pixop-license token output or license JWTs in chat.
pixop-decode-jwt is for operator debugging on trusted workstations; decoded claims can include customer identifiers.

Command pages

Command	Page
pixop-license	pixop-license.md
pixop-decode-jwt	pixop-decode-jwt.md
pixop-support-bundle	pixop-support-bundle.md
pixop-pack-config	pixop-pack-config.md
pixop-pack-logs	pixop-pack-logs.md

Back to the CLI reference.