Jump to content

Resolved: GUI: 413 Request Entity Too Large


Donovan

Recommended Posts

I had an issue where one of my unRAID USB drives would no longer boot. The drive was actually a SD/microSD enclosure that kept mounting and unmounting when I tried it on Windows.  I ended up taking the microSD card out and putting it into a USB reader and copied the files from that drive to my other unRAID USB drive and restarted the system from that.

 

I think it was at that point that I found I could no longer open the unRAID GUI in Chrome:

 

413 Request Entity Too Large

 

I ended up opening it fine in Firefox instead.

 

A week later, I now get the same error, so I've had to go to Internet Explorer to access the GUI.

 

I think I was on b15 when this started, I just upgraded to RC2 and it's still doing it.  The log mentions an issue:

 

May 23 11:11:24 Crushinator emhttp: read_line: read_line: input line too long
May 23 11:11:24 Crushinator emhttp: read_line: client closed the connection
May 23 11:11:25 Crushinator emhttp: read_line: read_line: input line too long
May 23 11:12:19 Crushinator emhttp: read_line: read_line: input line too long
May 23 11:12:19 Crushinator emhttp: read_line: read_line: input line too long
May 23 11:12:19 Crushinator emhttp: read_line: client closed the connection
May 23 11:12:58 Crushinator emhttp: read_line: read_line: input line too long
May 23 11:12:58 Crushinator emhttp: read_line: client closed the connection
May 23 11:12:59 Crushinator emhttp: read_line: read_line: input line too long

 

I removed nerdpack and emby server plugins, which I didn't currently use anyway, leaving no other plugins.  I tried disabling all of the plugins in Firefox and restarting it, still happens.  I suspect I have to try recreating the server from scratch or some other sort of corruption due to the failing SD/microSD enclosure?  Ironically, the whole point of that enclosure was to avoid losing an unRAID key due to USB drive failure...

 

...Donovan

Link to comment

Large cookies created by add-ons have caused this problem in the past:

May 23 11:11:24 Crushinator emhttp: read_line: read_line: input line too long

 

Check for any cookies associated with the server. You can also try using the IP address instead of the server name because that will bypass cookies associated with the server name (or vice versa).

Link to comment

Very interesting. I actually always access unRAID using the IP, so I tried http://crushinator instead and it worked. Additionally, I checked cookies and there were 38 for 192.168.1.100 so I (accidentially) removed all cookies and now unRAID responds on 192.168.1.100 as well.

 

Thank you, wise one!  :D

 

...Donovan

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...