Your license key
ProofTrail needs a license key for each installation. A key starts with PT-, and you find it in your account after buying it on the pricing page. One key covers one production and one staging installation at a time.
Activating it
Put the key in .env as PROOFTRAIL_LICENSE_KEY and recreate the containers with docker compose up -d. ProofTrail activates it when the web container starts, and checks it again every night. An administrator can also type the key in Settings › Advanced › License; a key in .env wins over it.
To activate, ProofTrail sends account.laibe.cc the key, a random id made for the installation, the host name of its APP_URL, and its environment and PHP version. The server answers with a signed token that ProofTrail checks itself, with a public key built into the image, and the nightly check fetches a fresh one. Nothing else goes with it: none of your compliance data, staff or evidence.
When the server can't be reached
ProofTrail keeps working, with a banner in the admin panel, so a firewall change or an outage at account.laibe.cc doesn't interrupt anyone. A token lasts 14 days; after that the license counts as lapsed, as below. Settings › Advanced › License shows when it last checked in.
When a license lapses
- In the 14 days before a license ends without renewing, the admin panel shows a banner.
- For 30 days after it lapses, the banner stays and everything works.
- After that, the compliance workspace waits on its license page until a valid key is entered.
- A new installation waits on that page from the start, once its first administrator has set up their account.
The employee portal, the auditor portal, the public trust center and exports never stop, and nothing is deleted. Renew from your account, or enter another key.
Moving it to another server
Deactivate the old installation in your account, then start the new one with the same key. A key that is already on two installations is refused until one of them is deactivated.
When it doesn't activate
Settings › Advanced › License says why. The usual reasons:
- The key isn't the whole key: it runs from
PT-to the end, with no quotes or spaces. - It is already on two installations: deactivate one in your account first.
- The server can't reach account.laibe.cc: ProofTrail needs outbound HTTPS to it, through your firewall or proxy.