starred/Heimdall-linuxserver

Fork 0

mirror of https://github.com/linuxserver/Heimdall.git synced 2026-03-03 00:26:56 -05:00

400 - Request Header Or Cookie Too Large #492

New issue

Closed

opened 2026-02-20 12:00:05 -05:00 by deekerman · 7 comments

deekerman commented

2026-02-20 12:00:05 -05:00

Owner

Originally created by @UtopiaOpera on GitHub (Feb 26, 2022).

Installing in Docker / Portainer using image linuxserver/heimdall:arm32v7-2.2.2 gives me the following error on opening web interface (same issue on :lastest tag):

400 Bad Request
Request Header Or Cookie Too Large
nginx/1.18.0

Container log doesn't seem to show any errors:


-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \ 
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/


Brought to you by linuxserver.io
-------------------------------------

To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid:    911
User gid:    911
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing... 
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-keygen: executing... 
using keys found in /config/keys
[cont-init.d] 30-keygen: exited 0.
[cont-init.d] 50-config: executing... 
Setting permissions
[cont-init.d] 50-config: exited 0.
[cont-init.d] 90-custom-folders: executing... 
[cont-init.d] 90-custom-folders: exited 0.
[cont-init.d] 99-custom-files: executing... 
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-files: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.

Searching the general error for nginx suggests editing etc/nginx/nginx.conf file to include this setting:

server {
    # .
    large_client_header_buffers 4 32k;
    # .
}

Which didn't do anything, same error.

Originally created by @UtopiaOpera on GitHub (Feb 26, 2022). Installing in Docker / Portainer using image **linuxserver/heimdall:arm32v7-2.2.2** gives me the following error on opening web interface (same issue on :lastest tag): **400 Bad Request Request Header Or Cookie Too Large nginx/1.18.0** Container log doesn't seem to show any errors: ``` ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io ------------------------------------- To support LSIO projects visit: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 911 User gid: 911 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 50-config: executing... Setting permissions [cont-init.d] 50-config: exited 0. [cont-init.d] 90-custom-folders: executing... [cont-init.d] 90-custom-folders: exited 0. [cont-init.d] 99-custom-files: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-files: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. ``` Searching the general error for nginx suggests editing **etc/nginx/nginx.conf** file to include this setting: ``` server { # . large_client_header_buffers 4 32k; # . } ``` Which didn't do anything, same error.

deekerman

2026-02-20 12:00:05 -05:00

closed this issue
added the
question
label

deekerman commented

2026-02-20 12:00:06 -05:00

Author

Owner

@aptalca commented on GitHub (Feb 26, 2022):

just tested that image on an rpi 4 and it works just fine here

@aptalca commented on GitHub (Feb 26, 2022): just tested that image on an rpi 4 and it works just fine here

deekerman commented

2026-02-20 12:00:06 -05:00

Author

Owner

@UtopiaOpera commented on GitHub (Feb 26, 2022):

just tested that image on an rpi 4 and it works just fine here

Um. RiPi 3B+ here. Wondering if it's something to do with 1Gb memory.

@UtopiaOpera commented on GitHub (Feb 26, 2022): > just tested that image on an rpi 4 and it works just fine here Um. RiPi 3B+ here. Wondering if it's something to do with 1Gb memory.

deekerman commented

2026-02-20 12:00:07 -05:00

Author

Owner

@aptalca commented on GitHub (Feb 26, 2022):

How are you accessing it? With or without reverse proxy?

@aptalca commented on GitHub (Feb 26, 2022): How are you accessing it? With or without reverse proxy?

deekerman commented

2026-02-20 12:00:07 -05:00

Author

Owner

@magnus919 commented on GitHub (Apr 22, 2022):

Still a problem. Running in a Docker container with plenty of free CPU & memory. Spans multiple web browsers.

@magnus919 commented on GitHub (Apr 22, 2022): Still a problem. Running in a Docker container with plenty of free CPU & memory. Spans multiple web browsers.

deekerman commented

2026-02-20 12:00:07 -05:00

Author

Owner

@UtopiaOpera commented on GitHub (Apr 23, 2022):

Still a problem. Running in a Docker container with plenty of free CPU & memory. Spans multiple web browsers.

I think I tracked this down to not using DNS. This could just be down to Firefox which I use, or not, but when all your services use the same IP address, all the cookies for all your different services are stuffed into one single cookie file. I don't see why it's a problem because it's still a tiny file size, and I can't remember now if I looked into increasing the allowed size of a cookie.

Anyway, I ended up using the local DNS service in Pi Hole in combination with Nginx proxy manager, and I haven't had the cookie too large error since.

@UtopiaOpera commented on GitHub (Apr 23, 2022): > Still a problem. Running in a Docker container with plenty of free CPU & memory. Spans multiple web browsers. I think I tracked this down to not using DNS. This could just be down to Firefox which I use, or not, but when all your services use the same IP address, all the cookies for all your different services are stuffed into one single cookie file. I don't see why it's a problem because it's still a tiny file size, and I can't remember now if I looked into increasing the allowed size of a cookie. Anyway, I ended up using the local DNS service in Pi Hole in combination with Nginx proxy manager, and I haven't had the cookie too large error since.

deekerman commented

2026-02-20 12:00:07 -05:00

Author

Owner

@snachodog commented on GitHub (Feb 11, 2025):

all the cookies for all your different services are stuffed into one single cookie file

I encountered this error for the first time, - I just access Heimdall directly with the internal network IP address and your tip about the cookies saved the day. I cleared the cookie and it was all good again. Going to put it back into Nginx Proxy Manager so I don't have to deal with this issue.

@snachodog commented on GitHub (Feb 11, 2025): > all the cookies for all your different services are stuffed into one single cookie file I encountered this error for the first time, - I just access Heimdall directly with the internal network IP address and your tip about the cookies saved the day. I cleared the cookie and it was all good again. Going to put it back into Nginx Proxy Manager so I don't have to deal with this issue.

deekerman commented

2026-02-20 12:00:07 -05:00

Author

Owner

@yewkay commented on GitHub (Feb 27, 2025):

Just encountered this issue today as well. Using a different browser allowed me to access the page as normal. Cleared cookie for the heimdall page and everything loads. However, the issue comes back after a few hours. Clearing cookie again works. Doesn't seem to be a permanent solution if i have to keep clearing cookies every few hours.

@yewkay commented on GitHub (Feb 27, 2025): Just encountered this issue today as well. Using a different browser allowed me to access the page as normal. Cleared cookie for the heimdall page and everything loads. However, the issue comes back after a few hours. Clearing cookie again works. Doesn't seem to be a permanent solution if i have to keep clearing cookies every few hours.