License messages
What the License page says when a key will not activate or the portal cannot check in, and what to do about each.
- For
- Administrators
- Applies to
- Billet 1.0
- Updated
The License page is in the console under Deployment. See Activate your license for how to enter a key.
When a key will not activate
| The page says | Cause | What to do |
|---|---|---|
| That is not a license key | It is not a whole key (bmlic_ followed by 43 characters). |
Paste it again, all of it. |
| The license service does not know this key | It was mistyped, or a newer key has replaced it. | Check it against where it was issued. |
| ... this key belongs to another deployment | The deployment ID box does not hold the ID the key was issued for. | Put in the deployment ID shown beside the key. |
| The license service refused this portal: install revoked | This portal node was revoked at the license service. | Contact Billet to restore it. |
| The license service could not be reached | No route, DNS, or a proxy is in the way. | Run the check below. |
| ... answer could not be read | Something between the portal and the service answered in its place, such as a captive page or an intercepting proxy. | Run the check below and read what comes back. |
| ... answer was not accepted: signing key ... not certified by the root key | The answer was not signed by Billet's license service, or the portal is older than a change to the service's keys. | Run the check below. Then check the portal's version and upgrade it. |
| ... dated in the future. Check this machine's clock | The portal's clock is more than five minutes behind. | Turn on NTP on the portal server. |
| The stored license key cannot be read back | BILLET_BROKER_SECRET changed since the key was entered. |
Enter the key again. Then keep that secret unchanged, with your backups. |
The check from the portal server
curl -sI https://license.billetstream.com/A response from the service, with no certificate error, means the route is clear. A certificate error, a login page or a timeout means something on the way needs fixing: a firewall rule for outbound HTTPS, DNS, or a proxy that must let this name through untouched.
Licensed, not verified lately
The license is good, but the portal has not reached the license service for over two hours. Run the check above from each portal node. The page shows the time of the last successful check-in and what went wrong with the last attempt. Press Check now after fixing it.
In the portal's log
Each portal node logs a line at start saying what license it holds, and one warning when check-ins start failing:
journalctl -u billet-portal | grep -E 'license: what this portal holds|license.checkin_failed'