Before you start
- Complete local identity and connection checks first.
- Keep a local recovery person or maintenance window available.
- Use the K7abeer desktop bridge or Remote Access workflow instead of publishing the RouterOS API broadly.
Procedure
Follow these steps in order
Confirm local management
While on the same LAN, open the device and run Check connection. Fix credentials, API permissions, or local routing before attempting remote access.
Open Remote Access
Choose Remote Access from the device controls and review the exact tunnel or desktop steps shown for the device mode.
Install the generated configuration
Apply only the configuration generated for this device. Do not reuse another router's token, tunnel address, or script.
Wait for a verified handshake
Refresh the device. A tunnel handshake alone is not enough; K7abeer must also receive a successful RouterOS API response.
Test away from the LAN
Disconnect the setup phone from the customer WiFi, use mobile data or another network, then run Check connection and a read-only refresh.
Verify success
- The device reports a recent tunnel handshake.
- The RouterOS API check succeeds through the remote path.
- Device and internet status update without the local desktop bridge.
Troubleshooting
Tunnel is online but the router is still checking
The tunnel may be reachable while the RouterOS API is not. Verify the tunnel IP, API service, credentials, firewall input rules, and device identity.
Remote setup disconnects
Return to the local LAN. Do not release or reinstall the router; correct the remote path while preserving ownership and vouchers.
Was this guide helpful?
Your response helps the system owner prioritize documentation updates.