Invalid request body
Upon updating from 1.51.1 to 1.51.2 I receive an error message from the web and mobile app which reads "Invalid request body".
EThinking this might be related to #2019
EI am not using the provided proxy service.
MPlease check for error logs in the server container and your browser/app
BEWeb report 400 bad request
EDon't see anything in the server container logs.
BCheck the web container
BI am not using the provided proxy service.Did you set up the routing correctly?
EWell I did notice there was a change from #2019 and I have yet to adapt that.
EI'm thinking that is the likely cause at the moment.
BThat's not a change that should break anything
BIt's just a small improvement
EOkay, well the proxy I have was working with 1.51.1
BIs the IP of your proxy, as seen by immich-server, one of
?
?
EWould I be able to find that in the logs?
BI don't think so, but docker inspect should do it
EI run 2 replicas of the webserver with the proxy and I see the address as 10.0.1.239 and 10.0.1.240
MWhy do you think #2019 is related? Haven't seen anything that points towards that. Does everything work again if you revert back to v1.51.1?
MAlso, can you please provide more details about your setup (deployment method, version, which proxy, etc.), check if all your containers are running, if they contain error logs and post screenshots of any errors
EWas thinking it was related as the default proxy config changed.
EEverything does work again if I revert to 1.51.1
MBut you aren't using Immich's proxy, so I don't see how that's causing issues
EPastebin
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
EI deploy with docker swarm and use the linuxserver.io swag container for the proxy
EPastebin
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
BI thought the
BMight not include their proxy address
BOfc that shouldn't be the case, because the proxy shouldn't be on a public address internally
EAll the services are running.
BIf you go to https://demo.immich.app/api/server-info/ping (replace the host with your own, of course), do you get a pong response?
EI don't see errors in the logs, except the database has some suspicious messages related to my setup.
EB
B@jrasm91 I don't think this has to do with your refactor in https://github.com/immich-app/immich/pull/2038, but can I get your eyes on this anyways just in case?
JWhat's the actual error and for what request?
E
E
BThat's an error coming from your proxy, not from Immich
BSo check your proxy logs
JCan you send a screenshot of the network request from the web?
EFrom the web dev tools console?
JYeah
Ahttps://immich.app/docs/administration/reverse-proxy @EnochPrime can you try follow the info mentioned in the docs
When deploying Immich it is important to understand that a reverse proxy is required in front of the server and web container. The reverse proxy acts as an intermediary between the user and container, forwarding requests to the correct container based on the URL path.
JLike what if the actual response code and did it say what server is sending it.
EUnfortunately I cannot send a screenshot at the moment. But it is error code 400
BWhat are the response headers etc?
EConnection: keep-alive
Content-Length: 20
Date: <as expected>
Server: nginx
Content-Length: 20
Date: <as expected>
Server: nginx
JAnd the response?
B"Invalid request body", presumably
JWhat url is this for?
