Licences
Licences are seats you assign to things in your account. There are three kinds:
- Sentry — needed to add a sentry, and for that sentry to keep receiving its settings;
- Origin — adds room for one more origin server beyond the two included with each licensed sentry;
- Website protection licence — adds room to turn Website protection on for one more domain beyond the one included with each licensed sentry. Every Website protection domain, included or licensed, also comes with domain owner access.
Licences belong to your account and can move between your clusters.
Licences on Billing
Your licences are on Billing, under Licences. That section shows, for each kind, how many seats are available, assigned, expiring, in grace and expired, and lists every seat with what it is assigned to.
- Assign a seat — pick an available, in-date seat and the sentry, origin or domain to assign it to. Assigning a Website protection licence turns Website protection on, and the domain starts in log mode.
- Unassign — returns the seat to your pool. Unassigning a domain with Website protection seat turns Website protection off for that domain. Turning Website protection off on Domains returns a licence to your pool if one was used.
- Add a sentry — creates a sentry in a cluster using the available sentry seat you choose. See Installing a sentry.
A sentry with no licence shows an Assign a licence link on its row and on the sentry's page. On hover it says the sentry has no licence, and to assign one on Billing, under Licences. The link opens Billing at Licences, with that sentry already selected.
Deleting a sentry that never checked in, or removing an origin server, also returns its seat to your pool.
Licence limits
Each sentry includes two origins and one Website protection licence.
- Sentries — every sentry needs its own sentry licence. When you add a sentry, you choose an available, in-date sentry licence. If you have none, Add sentry is turned off until you buy one or unassign one. Each licence can only be used by one sentry.
- Origins — each licensed sentry includes 2 origin servers. Origin capacity is pooled across the account. Each origin licence adds room for one more. For example, 2 sentries and 1 origin licence allow 5 origins. When every place is in use, Add on Origins is turned off.
- domains with Website protection — each licensed sentry includes 1 Website protection licence. Website protection capacity is pooled across the account, like origins. Extra Website protection licences are a single number you set on Billing, from 0 up. When every place is in use, Website protection cannot be turned on for another domain, and the Off button is greyed out: add a licensed sentry or buy extra Website protection licences on Billing first. If the account goes over its Website protection allowance, Website protection is turned off on the newest domains and the oldest keep Website protection. A domain beyond the included ones uses a Website protection licence. Turning Website protection off on that domain returns its licence to your pool.
- Clusters — clusters don't need a licence, but you can't add a new cluster while one of your clusters has no sentries. See Adding a cluster.
Website protection capacity alerts
The dashboard shows an alert when you've used 80% of your domains with Website protection, and a stronger alert when they're all in use. Account owners also get an email the first time each threshold is crossed.
The 80% alert and email are sent again only after usage drops back below 70%. The full alert is sent again as soon as one Website protection licence is free.
To add capacity, buy extra Website protection licences on Billing, or add a licensed sentry, which includes one more Website protection licence.
Sentry device keys
Each sentry also has its own device key, which it uses to identify itself. It is separate from the licence seat. When you add a sentry, the portal shows the device key and the install command once, with copy buttons. stillorigin doesn't keep a readable copy of the key, so it can't be shown again. Copy it somewhere safe, such as a password manager.
If you lose a device key, click New key on the sentry's row on the cluster's Edit page. The portal issues a new key and shows it once, with a command to put it on the server. The old key stops working straight away, so an installed sentry goes offline until you run that command on it.
Your API key
Your sentries use your account's API key, together with their own device key, to connect to stillorigin. stillorigin doesn't keep a readable copy of the API key either, so it is shown only once, when you create it. Install commands show YOUR_API_KEY in its place.
The same key lets your own billing system, CRM or client area use the API to look up a domain, turn Website protection on and off, and create domain owner sign-in links. The WHMCS module uses it too. If you use it there, update it there too when you create a new key.
An account owner manages the key under My account › API key (open My account from the menu at the bottom of the sidebar):
- Create API key — if the account has no key yet. Create one before you install your first sentry.
- Create a new API key — if you have lost the key, or want to change it. Tick Keep the old key working for 7 days, so I can update my sentries to give yourself time to put the new key on each sentry; the portal shows the command to run on each one. Leave it unticked and the old key stops working at once.
- Stop the old key now — ends the 7 days early, once all your sentries have the new key.
Putting a new API key on your sentries
After you create a new API key, put it on every sentry you've already installed. New sentries just use the new key in their install command.
-
Copy the command the portal shows under Run this on each sentry to switch it to the new key. It already contains your new key and looks like this:
printf '%s\n' 'NEW_API_KEY' | sudo tee /etc/stillorigin/api_key >/dev/null && sudo systemctl restart stillorigin-sentry -
Run it on each sentry server. If you closed the page, use the same command with your new key in place of
NEW_API_KEY. -
Check that the sentry connected. Run
sudo journalctl -u stillorigin-sentry -n 20and look forconfig applied. The sentry also shows as Online on the cluster's Edit page. -
When every sentry has the new key, click Stop the old key now under My account › API key.
If the old key has already stopped working, a sentry that still has it can't connect until you give it the new key. Until then it keeps running with its last settings, but it won't get any changes.
Expiry and grace
Seats run for a set term, shown in the Expires column. The portal warns you on Billing, under Licences, on sentry rows and on the dashboard when a seat expires within 14 days, is in its grace period, or has expired.
Trial seats have no grace period: when they expire, or when a trial is cancelled, they stop at once. Paid seats have a short grace period after expiry, including 7 days after payment retries have stopped. During grace, a sentry that already had the seat keeps receiving its settings. After that, the sentry stops receiving settings until a seat is renewed or a new one is assigned. A grace period does not let you assign an expired seat to something new. A seat that stillorigin revokes stops working immediately.
To add or change paid licences, use Subscription on Billing. Sentry and origin prices are on the pricing page, and Website protection licence rates are shown on Billing in the portal.
Closing your account
Closing the account from Billing › Close account releases its licence seats. If stillorigin reopens the account within 30 days, you will need to assign seats again. See Closing an account.