Panellicense

Fix JetBackup license errors: invalid, not found, and IP mismatch

Diagnose JetBackup's license validation errors — no license found for this IP, license invalid for current server, and reissue failures — and fix each from WHM or the CLI.

JBAll JetBackup articlesTroubleshooting5 min readUpdated 2026-07-28
jetbackuplicensetroubleshootactivationip-change
schema: TechArticleschema: FAQPage

JetBackup locks hard when its license check fails. Unlike a panel that degrades gracefully, a licensing problem in JetBackup stops all scheduled jobs and blocks the JetBackup interface in WHM until you resolve it — there's no grace period to lean on, so the fix needs to happen now, not this week.

Every failure here traces back to one of three things: the license hasn't validated against the server's current public IP, the server can't reach JetApps' licensing servers at all, or the license itself has lapsed on the billing side. Work through them in that order.

Force a revalidation first

JetBackup checks in with the licensing server automatically every 48 hours and caches the result locally. Before troubleshooting anything, clear that cache and force an immediate recheck:

/usr/bin/jetbackup5 --license

Run it as root. This deletes the locally cached license key and pulls a fresh validation. If the license is genuinely fine and the earlier failure was a blip, this clears it in seconds. If it fails again, the error text tells you which branch you're in.

"No JetBackup license was found for the IP x.x.x.x"

This is an IP mismatch, and it's the most common case by far. JetBackup registers a license against the server's public IP at install time. Anything that changes that IP — reassignment by the provider, a NAT change, moving behind a new firewall appliance — breaks the match even though the license itself is active.

Confirm what JetBackup thinks your IP is versus what it actually is:

curl -4 ifconfig.me

Then check the license against that IP at jetbackup.com/verify-license. If it shows active for a different IP, you need to update the binding, not buy a new license.

For a licence bought through us, log into your client area, open the JetBackup service, and in the License Details box replace the value in License IP with the current address, then select Change IP. Re-run jetbackup5 --license once that's saved — it should pick up clean.

Migrating or rebuilding the server entirely

An IP change from a provider reassignment is a same-server fix (above). Moving to a new box — a fresh VPS, a hardware swap, a full rebuild — needs a reissue instead, because the underlying server identity changed, not just the address.

In the client area: Services → My Services → JetBackup → View Details, then under Management Actions click Reissue License. Once that's done, open the JetBackup GUI on the new server and it picks up the reissued license automatically — no key to copy in manually. Do this before you decommission the old server; a license can only be bound to one host at a time, so reissuing releases it from the source machine.

"License is invalid for current server"

Where the IP-not-found error names a mismatch you can self-serve, this one usually means the license record itself is in a bad state — suspended for non-payment, cancelled, or flagged by JetApps for reuse across servers it wasn't issued for. Check status directly rather than guessing:

  1. Go to jetbackup.com/verify-license and enter the server's public IP.
  2. If it shows Not Active, there's an unpaid invoice or a cancellation on the account — resolve that with your license provider before touching the server again.
  3. If it shows Active but the server still rejects it, that's back to the IP-binding case above, not a billing issue.

If you bought through us and the portal shows something inconsistent with what WHM reports, contact us with the server IP and we'll check the registration directly rather than you guessing at CLI flags.

Server can't reach the licensing servers

Less common, but worth ruling out on a locked-down box. JetBackup needs outbound connectivity to validate, and if you run default-deny egress rules, the check times out rather than failing cleanly — which looks identical to an invalid license from the WHM side. Confirm outbound HTTPS isn't blocked, and if you run CSF or a similar firewall, make sure it isn't stripping the connection before it leaves the box. See CSF firewall setup on cPanel if you need a refresher on how those egress rules get configured in the first place.

Next steps

Does a JetBackup license error stop my backups from running?+
Yes. Unlike some panels that keep services running through a licence lapse, JetBackup halts all scheduled jobs and blocks its own interface in WHM until the license validates again.
How do I force JetBackup to recheck its license?+
Run /usr/bin/jetbackup5 --license as root. It clears the locally cached license key and forces an immediate revalidation against JetApps' licensing servers instead of waiting for the automatic 48-hour check.
Why does JetBackup say no license was found for my IP?+
JetBackup licenses are bound to the server's public IP at activation. If that IP changes — a provider reassignment, a new NAT rule, a firewall appliance in front of the box — the license stops matching even though it's still active. Update the License IP field in the client area to fix it.
Do I need to reissue my JetBackup license after migrating servers?+
Yes, if you're moving to a different physical or virtual server rather than just changing the existing server's IP. Reissue it from Services > My Services > JetBackup > Management Actions > Reissue License before decommissioning the old server.
How can I check if my JetBackup license is active without logging into WHM?+
Use the public lookup at jetbackup.com/verify-license and enter the server's public IP. It shows the license status directly from JetApps' licensing servers.

Related articles

All JetBackup →All troubleshooting →
troubleshoot
Fix InterWorx license errors: invalid key and sync failures
Diagnose the Invalid InterWorx-CP License error — DNS and port 2443 checks, license.pex --sync, IP rebinding, and key swaps — before the 24-hour grace period ends.
4 min read
troubleshoot
Fix KernelCare license errors: registration, IP locks, and 403s
Diagnose KernelCare's licensing failures — no valid key-based license found, key limit reached, expired trial, and HTTP 401/403 during update — and fix each from the CLI.
6 min read
troubleshoot
Fix Plesk license errors: invalid, expired, and IP-bound keys
Decode the common Plesk license errors — invalid key, expired key, IP-bound, and connectivity failures — and fix each one from the CLI in minutes.
5 min read
troubleshoot
Check your hosting panel license status from the command line
Every panel and add-on has a one-line SSH command that tells you whether its license is valid, active, and locked to the right IP. Here's the exact command for each.
8 min read
troubleshoot
Fix CloudLinux "No valid license found" registration errors
Work through the CloudLinux "No valid license found" error in order — IP-based vs key-based registration, stale CLN server entries after a migration, and blocked outbound to cln.cloudlinux.com.
5 min read
troubleshoot
Fix Imunify360 license errors and unregistered agent
Work through Imunify360 "No valid license" and "license is invalid for this server" errors in order — IP vs key registration, stale bindings after a migration, and user-count overruns.
5 min read
Switch in an afternoon

Switch from your current reseller — free.

We migrate active cPanel, Plesk, LiteSpeed and CloudLinux licenses from any reseller. We prorate the first month so you never pay twice, and your customers see zero downtime during the swap.