Guide / Plans, privacy and help
Licence troubleshooting
When Pro does not switch on, a sign-in fails or the licence service cannot be reached: what to check, in the order that finds it fastest.
I bought Pro but it is not active
- Give it a minute. After checkout your tool notices the payment by itself and asks for the code sent to the address that paid. If you closed that dialog, start signing in again from the licence screen of your tool.
- Sign in with the exact e-mail address you paid with. It is the address on Polar's receipt, which can differ from your Git or work address.
- Ask the machine what it thinks. Run
penstock license. It says which licence this machine has and why, and during the trial it says when the trial ends. - Check the machines. One key covers three machines. When every place is taken, signing in lists the machines so you can free one. See How many machines.
- Check the subscription. If it ended, or was refunded or cancelled, a machine falls back to the trial, or to Free when the trial is over. Polar's customer portal, which you can sign in to with the same e-mail, shows its state.
- Check the clock. A machine whose clock was set back below a time it has already seen is refused, and the message says so.
- Restart your tool and run
penstock licenseagain.
A Pro key does not work in a pipeline. A pipeline needs a Team key. See In a pipeline.
No code arrived in the mail
- The code is sent by Polar, to the address you typed. Look in the spam folder, and check the address for typing mistakes.
- If you never bought with that address, there is no licence for it. The message says There is no Penstock licence bought with that address.
- A code expires, and you have three tries for each. Ask for a new one.
- In a terminal that is not interactive, for example a CI job, signing in cannot ask for the code. Use
PENSTOCK_LICENSEthere.
A proxy or a firewall is in the way
Buying, signing in, activating, starting a trial and the daily renewal need HTTPS to two places. Allow them on port 443:
| Address | What it is for |
|---|---|
licence.getpenstock.com | The licence service: the trial, activation, the daily renewal and releasing a machine. Releases up to 26.11.2 call it at licence.penstock.dalyone.com, which stays in service; allow both while those releases are in use. A new address is announced in the changelog. |
api.polar.sh | Polar, for signing in with an e-mail code, and for the checkout link. |
polar.sh pages | The checkout, which opens in your browser and not in your tool. |
The message The licence service could not be reached means one of these did not answer. A licence you already have keeps working: a valid token is used without a connection for up to 30 days. Everything else in the editors works without a licence service at all. See Security and privacy for the complete list of what talks to the network.
I work offline or on an isolated network
- A token belongs to one machine, lasts 30 days, and is renewed once a day when the machine is online. Offline, it keeps working until it runs out, and the status shows how many days are left.
- After 30 days without a check, the machine is on Free until it connects once. Then it is renewed, and nothing is lost.
- A new machine needs the network once to start its trial or to activate a licence.
- A pipeline that cannot reach the licence service runs as Free.
I cannot reach the machine that holds a place
Sign in on the new machine with the same e-mail. When every place is taken, the sign-in lists the machines and when each was activated. Pick the one you no longer have, and this machine takes its place. A token cannot be taken back from a machine that is offline, so each key has one free move per place in any 30 days. A further release keeps counting until 30 days after it was noticed, and the message says the date. See Move a machine.
The key for my pipeline
Run penstock license key on a machine with Team and store what it prints as the secret PENSTOCK_LICENSE in your CI system: a repository secret on GitHub, a masked variable on GitLab, a secret variable or a library variable group on Azure DevOps. The key only counts where CI is set. See In a pipeline.
Still stuck
Open an issue on the support tracker, or write to hello@getpenstock.com. Say what your tool and its version are, what you did, and the exact message. Add the output of penstock license and penstock doctor. Never send or post a licence key.
Common problems
- It says the machine's clock is wrong.
- Set the clock to the real time. The clock had been set back below a time this machine already saw.
- It says every machine is in use.
- Pick a machine to free when signing in, or sign out on one you no longer use.
- The licence status says trial, but I paid.
- Sign in. Paying does not switch the machine on by itself until your tool has noticed the payment, or you have signed in with the e-mail that paid.