Skip to content

Your licence

Pro runs once the site is activated for its domain. www. does not count, so example.com and www.example.com are the same domain. Each time you open the dashboard, JS Jobs checks the saved key with the licence server at most once a day.

Development sites need no activation: Pro is fully on at localhost, 127.0.0.1, ::1, host.docker.internal, addresses ending in .local, .test, .localhost, .invalid, .example, .ddev.site, .lndo.site or .docksal.site, and private network addresses such as 192.168.x.x.

What the administrator shows when something is wrong:

Situation What you see Pro features
The site moved to a domain the licence was not issued for “This JS Jobs Pro licence was issued for a different domain. It keeps working for N more day(s)…” with Reactivate now Keep working for 14 days, then switch off
No successful check for 45 days, or the licence statement has run out “JS Jobs Pro has not been able to verify its licence recently…” with Check now Keep working
Never activated here, or the grace period is over “This copy of JS Jobs Pro is not activated for this domain. Pro-only features are switched off until it is activated.” with Activate and Buy a licence Switched off (see Free and Pro)

Reactivate now, Check now and Activate open JS Jobs Update; Check for Updates there activates the site again.

An expired subscription does not switch Pro off. What stops is updates: see Updating.

Message Meaning
“That activation key was not recognised…” Check the key against your order e-mail or your account on joomsky.com.
“This activation key has been replaced…” Use the new key from your account.
“This licence has expired. Renew it on joomsky.com to activate a new site.” An expired licence cannot activate another site.
“This licence is on hold…” Usually a failed renewal payment.
“Every site on this licence is in use…” Release a site in your account, or move to a plan with more sites.
“This licence does not include JS Jobs Pro.” The key is for another product.
“Could not reach the licence server (…)” The site could not connect; check outgoing HTTPS.