Web Interface inaccessible; LUA LuCI corrupt, unable to find 'main'

[Ehryk]

I just got my A+ router, plugged it in, and set it up through the touch screen. Pretty happy so far, but need to set up port forwards and the like. I don't see this ability in the touchscreen GUI.

Now I try to access through the web interface, and get:

/usr/lib/lua/luci/dispatcher.lua:211: /etc/config/luci seems to be corrupt, unable to find section 'main'
stack traceback:
   [C]: in function 'assert'
   /usr/lib/lua/luci/dispatcher.lua:211: in function 'dispatch'
   /usr/lib/lua/luci/dispatcher.lua:195: in function </usr/lib/lua/luci/dispatcher.lua:194>

Any ideas?

[Ehryk]

From SSH into the A+, /etc/config/luci is a 0 byte file:

root@AlmondPlus:/etc/config# ls -la | grep "luci"
-rw-r--r--    1 root     root             0 Sep  8  2011 luci

Is there anywhere I could get the would-be contents of this file? Or reflash the A+?

[LGNilsson]

Quick question, can you access the NutsOS web UI by going to the IP address of the router?

Also, have you tried to do a hard reset? http://wiki.securifi.com/index.php?title=Hardware_reset_button_-_Almond%2B_2014

The firmware is stored in flash, but loaded into RAM, so a hard reset would load a fresh image from flash which might address the problem.

I really don't know what's going on here and a screenshot or two would be helpful.

[Ehryk]

In a browser, 10.10.10.254 bounces me to 10.10.10.254/cgi-bin/luci which then returns a text-based 'web page' with the following:

/usr/lib/lua/luci/dispatcher.lua:211: /etc/config/luci seems to be corrupt, unable to find section 'main'
stack traceback:
   [C]: in function 'assert'
   /usr/lib/lua/luci/dispatcher.lua:211: in function 'dispatch'
   /usr/lib/lua/luci/dispatcher.lua:195: in function </usr/lib/lua/luci/dispatcher.lua:194>

Indeed the message is accurate, since /etc/config/luci is a 0 byte empty file.

I see 'luci-full' listed in `opkg list`, but I can't update it or update opkg at all, even with internet access:

root@AlmondPlus:/etc/config# opkg update
Downloading http://downloads.openwrt.org/snapshots/trunk/g2/packages/Packages.gz.
wget: server returned error: HTTP/1.1 404 Not Found
Collected errors:
 * opkg_download: Failed to download http://downloads.openwrt.org/snapshots/trunk/g2/packages/Packages.gz, wget returned 1.

I'm hard resetting it now. Thanks for the quick response!

[LGNilsson]

All the available OPKG's are installed on the Almond+ and at the moment there's no repository due to this. We'll get that set up at some point.

However, the issue you're having is not something we've come across and I'm not sure how that file could've gotten corrupted.

Please let us know if the hard reset doesn't fix the issue.

[Ehryk]

Hard reset worked!

root@AlmondPlus:/etc/config# ls -la | grep luci
-rw-r--r--    1 root     root          2388 Sep  8  2011 luci

Web Interface is now operational. Thank you!

[LGNilsson]

Phew... 

[reedog117]

I had this exact same problem with the router straight out of the box until I did a hard reset also.

[howling fantods]

+1
hard reset worked.

[Haemaker]

I just received the Almond+ with R064 firmware and had the same problem (LuCI corrupt).  Hard reset fixed it, but did not unregister my Almond+.  Still associated with my account.

[LGNilsson]

Yes, that's correct, the hard reset doesn't disconnect from the cloud service, nor does it remove associated sensors as this data is stored elsewhere.
Did the reset fix the LuCI issue?

[revlisoft]

I have the exact same issue. I will try the hard reset later today and report back.

[revlisoft]

Hard reset fixed the webui although the firmware download location isn't working.

[mixmaven]

Same here, new out of the box.  Hard reset fixed it.
For those wondering: A reset button is located on the top side of your Almond, just above the power connector. Simply use the stylus that comes with the Almond to press the reset button for about five seconds.  You do not loose your sensors or cloud settings.

[joltdude]

Just had to add +1 that I had the same issue with the Almond + ootb but using the hard reset button worked