-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] HTTP Status 400 – Bad Request #21
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
A human has marked this issue as invalid, this likely happened because the issue template was not used in the creation of the issue. |
I have no idea what this even means. Why is it Invalid? |
From Dozzle logs
|
Could you provide the container start up logs? that's what's missing. |
Sorry new to all this is this the start up logs? |
it looks like a database issue, but i dont use this container, so am only going off the logs. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
seeing the same error, but not the same cause: i'm using dockstarter. i simply spin up the airsonic-advanced container, and i'm getting a 404: container log: iTerm2 Session Jan 19, 2024 at 5:21:08 AM.txt any help is much appreciated |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
I cannot reproduce this error, I note that the original was created with OMV and with two different disks in use - possibly causing the issues. Second commenter notes about the Other than that, it works alright so closing this down |
This issue is locked due to inactivity |
Is there an existing issue for this?
Current Behavior
Changing admin password or making a new user
Expected Behavior
It should change the password or make the new user
But I get this
`HTTP Status 400 – Bad Request
Type Exception Report
Message Request header is too large
Description The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).
Exception
java.lang.IllegalArgumentException: Request header is too large
org.apache.coyote.http11.Http11InputBuffer.fill(Http11InputBuffer.java:790)
org.apache.coyote.http11.Http11InputBuffer.parseHeader(Http11InputBuffer.java:899)
org.apache.coyote.http11.Http11InputBuffer.parseHeaders(Http11InputBuffer.java:604)
org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:294)
org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:889)
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1743)
org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
java.base/java.lang.Thread.run(Thread.java:829)
Note The full stack trace of the root cause is available in the server logs.
Apache Tomcat/9.0.60`
Steps To Reproduce
Make a new user and hit save
Environment
CPU architecture
x86-64
Docker creation
Container logs
No error shown in logs
The text was updated successfully, but these errors were encountered: