New Build: Can't start the luci web interface (HTTP-Error 400: invalid header line)


 
B

BrandonL

New member
Hi Guys,

I'm a massive noob with this project and just completed a new build. Unfortunately I've been unable to connect to the web interface after disabling the LAN to try and get the Wireless interface to work. I get the following error:

HTTP-Error 400: invalid header line

and http://heatermeter.com/devices/ says "error" for the ethernet adaptor.

I'm able to telnet into openwrt no worries, and I've actually done a few cooks using the heatermeter which is working fine and managing temps perfectly.

I've tried starting from scratch again by formatting and re-imaging the SDCard by putting "norestore" to prevent config restoration but the same issue is happening.

Is there any log file for luci so I can debug further? I haven't been able to find anything on this problem.

Here's my fan design for a CharGriller Akorn Kamado Grill:

V1QykJR.jpg


Thanks for any help!
Brandon
 
What browser are you using? Any chance you've tried a different browser to see if the invalid header errors go away?
 
One tip I would say is to not disable the LAN port. You have a much higher chance of something being amiss the more changes are made to the interfaces. The LAN is already a double interface that as long as nothing is plugged into it will just happily sit there doing nothing. Just configure the wifi using the new text file method.

Do a fresh flash of the SD card with the image.
Immediately pop it back into the computer and add the norestore to the cmdline.txt
Add your wifi information to config.txt
Boot!

If you're getting invalid header, it might because there's an error message actually in the header. Like the page is being generated and an error occurs so it just comes out in the header. Usually the cause of this is that the SD card is corrupting itself due to semi-compatible with the Pi. You can check for that on the System Log in LuCI and see if it is getting a bunch of errors.
 
Hi Steve,

I feel so dumb, but yes I tried on my phone and it worked perfectly.

Turns out I had an extension installed in Chrome (Alexa Traffic Rank v3.0) causing the problem. I just searched this board and noticed one other person having this issue too.

Thanks for your reply too Bryan, it's fantastic you're still an active member here helping us newbies - what a great community!


Thanks again and hello from Sydney (Australia).
Brandon
 
You must log in or register to reply here.

 

Back
Top