BryanNetLicensing, renewal and offline grace behaviour
Prerequisites and authority
Assign an operator and an authorized technical owner. Data-replacing recovery and updates require a maintenance window, preserved recovery point and known target.
Operate licensing without confusing access failures
Review Settings → License for edition, expiry, verification state and capacity. Local verification checks the signed entitlement with the public key; online verification additionally checks authority status according to the configured mode.
| Condition | Operator response |
|---|---|
| Invalid signature/binding | Verify official license, key and installation identity |
| Genuine expiry | Arrange renewal and review operational restrictions |
| Authority unreachable | Check connectivity and configured grace state |
| Revoked/suspended | Escalate to licensing authority; do not bypass |
| Feature/capacity unavailable | Compare effective signed entitlements and intended action |
An online connectivity failure can enter permitted grace. That is different from granting indefinite forgiveness for expiry or revocation. Record the last successful verification and remaining grace shown by the release.
What expiry or verification failure changes
When the licence has genuinely expired, customer-facing API operations are blocked. This includes website/mobile sign-in, customer self-service, portal operations and access to public plan listings. The API returns a licensing restriction rather than treating the request as a payment or customer-password error. New subscription creation and other operations that require an operational licence are also restricted.
The licensing recovery control plane is separate from those customer routes. Authorized administrators can inspect the licence and use the supported renewal or recovery workflow. Eligible read-only licence checks can inspect an expired licence, but suspension, revocation, invalid signatures and installation-binding mismatches are not bypassed by expiry recovery.
A temporary authority connection failure can be covered by the configured online-verification grace window. That window does not extend the signed expiry date or reverse revocation. Offline verification still enforces signature, binding and expiry without relying on a routine authority connection.
Licensing restriction is not a command to disconnect every existing paid router session. Subscription expiry, quota, administrative suspension and router-local limits remain separate enforcement conditions. Application self-service can therefore be unavailable while an existing eligible network session continues. Do not promise that a browser session or a router reconnection will remain usable after the licence stops being operational.
Renew and confirm recovery
- Contact BryanNet before the displayed expiry date and confirm the installation ID, edition and required capacity.
- Obtain a renewed licence through the authorized workflow. Downloading the same expired licence does not extend it.
- Apply the renewed licence to the intended installation and verify its new expiry, binding, entitlements and operational state in Settings > License.
- Test customer sign-in and a supported customer action, then check the background services. If access remains restricted, preserve the exact licence error and contact support rather than editing stored tokens or dates.
Do not change the system clock, edit entitlement JSON or enable a development bypass in production. Preserve the signed token and public verification configuration securely; the signing private key never belongs on a customer installation.
Replacement-machine recovery may require authorized installation/license transfer. Copying the database alone does not establish permission or valid binding on another host. Use Licensing/edition capability matrix and Update, license validation or service reachability issue, and record renewal before the operational expiry window.
Related guides
Related guides: Health checks, background services and workers, Back up BryanNet and validate backups, Restore BryanNet safely, Product updates, compatibility and rollback, Daily weekly and monthly operator checklists.