Troubleshooting
The GL.iNet admin page says “Testing the firmware with sysupgrade failed”
Section titled “The GL.iNet admin page says “Testing the firmware with sysupgrade failed””You uploaded factory.bin. Upload sysupgrade.bin instead.
I can’t reach 192.168.1.1 after flashing
Section titled “I can’t reach 192.168.1.1 after flashing”- Make sure your computer is plugged into a LAN port: any LAN port on the MT6000, ETH0 on the G30W.
- Unplug and replug the cable so your computer gets a new address.
- If you set a fixed address for recovery, set it back to automatic (DHCP).
onebox-agent bind reports a certificate or time error
Section titled “onebox-agent bind reports a certificate or time error”The Box’s clock is wrong, usually because the WAN has no internet yet. Check the WAN cable and run the bind command again; it sets the clock before it starts.
The device isn’t in the console after binding
Section titled “The device isn’t in the console after binding”Run /etc/init.d/onebox-agent restart on the Box and wait a minute. Then check logread -e onebox for errors.
The console shows “Status unknown”
Section titled “The console shows “Status unknown””This is on our side, not your device. Don’t restart the Box. It clears on its own.
DDNS shows “Being prepared” or a 192.0.2.1 address
Section titled “DDNS shows “Being prepared” or a 192.0.2.1 address”It takes about 5 minutes after binding before the first update.
After a firmware upgrade, the version in the console went down
Section titled “After a firmware upgrade, the version in the console went down”Flashing an image puts the OneDux components back to the versions inside it. Run
apk update && apk upgrade onebox-agent onebox-core.
Still stuck
Section titled “Still stuck”Open a ticket from the console (Tickets). Include the device ID and the output of logread -e onebox | tail -50.