Before you start
- Connect your phone or computer to the same WiFi or LAN as the device.
- Confirm the device address, administrator username, and administrator password.
- Choose the branch that physically contains the device. Packages and vouchers follow the branch assignment.
- Keep a local recovery method available before allowing configuration changes.
Procedure
Follow these steps in order
Create or select the branch
Open Branches, confirm the business location, country, currency, and network name, then open Internet Devices from that branch.
- Do not create a duplicate branch for the same location.
- Confirm the branch currency before recording sales.
Choose the correct vendor
Select MikroTik, Ruijie, Grandstream, UniFi, or the matching supported device type. K7abeer shows only the connection modes available for that vendor.
Use the local address for first setup
Enter the device LAN address while your phone or computer is on the same network. Private addresses such as 192.168.x.x cannot be reached by the K7abeer cloud server without a local desktop connection or Remote Access.
Check identity before saving
Run Check connection. Compare the detected model, serial or MAC address, and vendor with the physical device. Stop if the identity does not match.
Protect the current configuration
Where supported, let K7abeer create and verify a protected backup before router-wide writes. Do not release or reset a device to solve an ordinary connection problem.
Enable remote management later
After local setup works, configure K7abeer Remote Access, the supported vendor cloud, or the desktop bridge. Recheck the device from a different network before considering remote setup complete.
Verify success
- The device appears under the intended branch.
- Model and device identity match the physical unit.
- Device and internet states are shown separately.
- A refresh does not create a duplicate device.
Troubleshooting
The local IP does not answer
Reconnect to the device WiFi or LAN, disable mobile data or VPN temporarily, confirm the gateway address, and use the desktop app when the browser cannot reach a private network.
The device appears offline after setup
Local setup and cloud monitoring are different. Configure Remote Access or the supported vendor cloud, then run Check connection again.
Was this guide helpful?
Your response helps the system owner prioritize documentation updates.