Connect your first router or access point
Prepare the network, choose the correct branch, and complete a safe first connection before enabling remote management.

K7abeer Help Center
Follow verified, step-by-step instructions for routers, access points, vouchers, captive portals, branches, staff, and subscriptions.
Step-by-step library
Every guide includes prerequisites, numbered actions, success checks, and the most common failure paths.
Prepare the network, choose the correct branch, and complete a safe first connection before enabling remote management.
Create customer WiFi, choose LAN ports, apply voucher access, and verify the captive portal without changing the WAN by mistake.
Move from a same-network installation to verified remote operations without exposing RouterOS directly to the public internet.
Adopt the AP, create Cloud API credentials, map the project and package, and validate captive-portal vouchers.
Prepare the network, API application, splash page, captive-portal policy, and 10-digit vouchers for remote operation.
Understand first-login expiry, connected-time-only access, and connected time within an activation window.
Make the login method clear before generation and print the credentials customers actually need.
Keep voucher creation separate from controller installation and download large existing batches without consuming the monthly allowance again.
Use a distinct layout, logo, background, support details, and credential fields, then deploy only to a verified compatible gateway.
Choose the correct lifecycle action so packages, vouchers, ownership, and audit history remain understandable.
Read device status correctly and diagnose local-only, tunnel, controller, credential, or internet failures without reinstalling the device.
Prevent voucher and permission mistakes when one business operates several locations and routers.
Understand trials, store purchases, manual payments, expiry, restoration, and what remains available when a subscription is inactive.
Verify controller ownership, adopt the AP, configure the customer network, and test the supported voucher or portal path.
Set up TP-Link, Omada, Wavlink, or another supported AP without presenting WiFi-only hardware as a voucher gateway.
Let K7abeer reach a private LAN address from the same network without exposing the router API to the public internet.
Reset a forgotten password, report an email problem, and give support enough non-secret information to investigate safely.
Receive service, offer, feature, and support updates on mobile while keeping app and device updates controlled.
Learn by workflow
A guided path from same-network setup to a tested remote connection.
Identify WAN/LAN roles, deploy a portal, and validate a test voucher.
Adopt an AP, map a user group, and diagnose controller errors.
Common questions
Start here for local addresses, controller pushes, archived devices, credential modes, and subscription access.
Yes for local setup. Connect to the same WiFi or LAN first. After the device is identified and configured, use K7abeer Remote Access, the supported vendor cloud, or the desktop bridge for remote operations.
That is a private LAN address. It is reachable only from the same network unless a supported remote tunnel, vendor cloud, or local desktop bridge provides the path.
No. Generation creates records in K7abeer. The batch must also report a successful device or controller installation before customers can use those credentials.
K7abeer normalizes common time names such as 1H, One Hour, 1 Day, or 1 Month, but the package still needs a matching or explicitly mapped Ruijie user group.
The Grandstream controller workflow uses 10-digit numeric vouchers by default. K7abeer keeps that compatible default for Grandstream batches.
Open Internet Devices and choose Archived devices. An archived device remains owned by the customer and can be restored to a branch.
No. Release is an ownership action for sale or permanent removal. Use connection diagnostics, Remote Access, vendor cloud checks, or support without destroying ownership context.
Yes, export existing vouchers in supported chunks or by package/profile. Printing and downloading do not generate new vouchers and do not consume the monthly generation allowance again.
Connected usage is accumulated, but a final deadline starts at first login. For example, one hour of usage must be consumed within 24 hours after the first successful login.
Support should use the audited account-recovery workflow. Staff must not ask for or view the customer's existing password, OTP, private key, or device secret.
No. Store billing is managed separately by Apple or Google. Cancel the store subscription in the store account that purchased it.
Confirm DHCP, DNS, portal policy assignment, controller online state, and device hotspot configuration. VPN, private DNS, cached sessions, and OS captive-portal detection can also affect testing.
No. Standard WiFi access points may only provide wireless connectivity. Vouchers must be installed on a capable hotspot router, authorized vendor controller, or authentication gateway.
Support cannot view an existing password. Use the audited password-reset or account-recovery workflow, and never send a password or OTP in a ticket.
Still need help?
Support can diagnose faster when your request includes the vendor, model, device state, branch, batch number, and the complete error text. Never share passwords, OTPs, API secrets, or private keys.