Troubleshooting
The failures people hit most often with Nasnet Panel, and what to do about each one.
Overview
This page collects the errors Nasnet Panel actually raises and what each one means. If your problem is with the router rather than the panel, run a report from Diagnostics first, because it checks system info, interfaces, WiFi, routing, DNS, VPN, connectivity and recent log errors in one pass, and produces a file you can hand to support.
Reference
Getting back in when you have lost the router
The Easy Config wizard leaves two emergency routes in place, and they are worth writing down before you need them.
| Route | Address |
|---|---|
| Plug into the last Ethernet port | 192.168.200.1 |
| Join the management WiFi named in the apply dialog | 192.168.210.1 |
The management WiFi name and password are shown in the apply dialog while the
wizard runs. If the installer applied the baseline LAN, the panel itself is at
http://192.168.10.1:8080/.
Troubleshooting
Installing
The install script stops waiting for physical confirmation. RouterOS requires it the first time container device-mode is enabled. Briefly press the reset/mode button, or cold power-cycle the router, then run the script again.
The panel is unreachable after install.sh finishes. The baseline LAN step
moves the router’s LAN onto LANBridgeSplit at 192.168.10.1/24. Renew your
DHCP lease and open http://192.168.10.1:8080/. Pass --no-lan-baseline next
time to skip that step.
The container will not stay up. The panel needs at least 30 MB of free RAM on the router.
Adding a router
“… is not reachable”. The address did not answer. Check the IP and the path
between the panel and the router. A panel in a bridged Docker network cannot
see your LAN, so run it with --network=host.
“… does not appear to be a MikroTik device”. Something answered at that address but did not identify as MikroTik.
“Invalid username or password”. RouterOS rejected the login.
“Router already added”. That address is already on your list; the dialog offers Open router.
Running the wizard
Every tab redirects back to the wizard. The router has not completed Easy Config. A failing wizard status check is treated the same way, so also confirm the panel can read status from the router.
“Timed out waiting for the router to finish.” The apply ran for six minutes
without reaching 100%. Reach the router on an emergency address, either the last
Ethernet port at 192.168.200.1 or the management WiFi at 192.168.210.1,
and check its state.
“Apply failed”. The reason is printed under the title. Retry re-sends the same batch.
Day to day
“Missing router credentials for this session.” / “Session expired. Please reconnect to the router.” Credentials live for the browser session only. Go back to the Routers list and open the router again.
“No traffic data collected for this interface yet”. RouterOS has not recorded graph data for that interface. Pick another, or wait.
Tables stay on skeletons. The first read from the router has not returned. Check reachability and credentials.