-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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] Error [ERR_HTTP_HEADERS_SENT]: Cannot remove headers after they are sent to the client #5744
Comments
I have the same issue v1.91.0, using traefik as a proxy to immich-server.
|
same +1 app auto backup also failed |
+1 here. Same error. |
Same here, it happens on page refresh and just shows a blank page. |
Same here. Refresh - blank page since 1.91.0.
|
@jrasm91 Any thoughts on this error Jason? I can't reproduce the blank page issue |
Who is not using Docker? I don't. Maybe it's related. |
@traktuner @TomasValenta Are you guys using docker/docker-compose to deploy Immich? |
Hi. I'm also having this issue, and am using https://github.com/imagegenius/docker-immich to deploy, along with the |
Same here. But no blank page, frontend seems to work correctly. Docker containers via Traefik. |
Yes, docker-compose image |
The blank page issue should been have solved with #5753. Will be fixed for the AIO when imagegenius/docker-immich#255 is merged |
I just took an immich update and this message is now gone. I can't get it to reappear. Normally I would resolve since I submitted it, but since there are so many others here I'll leave to whomever fixed it to resolve. |
That error message "Cannot remove headers after they are sent to the client" persists in 1.91.2. Blank page was fixed by #5753. |
Additionally seeing a lot of... |
I have this error too in 1.91.2 Logs:
|
1.91.2
|
I only have this issue when using my reverse proxy |
same problem in 1.91.3, and now (I don't know if this is related) my android phone backup the photos but there is none in web interface (with 1.91.2 everything was working fine) nvm: my phone changed the location (different timezone) and the photos was taken in the future... after one hour (difference of timezone) the photos showed in the web interface |
Same error im experiencing when trying to perform a search in 1.91.2 |
Same issue when I reload or scroll a page (not a specific page) but no blank page, frontend seems to work correctly. Docker (compose) containers via Nginx.
Version : 1.91.3
What am I supposed to do ? |
Update. |
I have a similar log when i try to load some videos, when this happens the video seems to load very slow
|
Fixed again in #10289, which will be in the next release. |
The bug
After updating to 1.91.0 I'm seeing these messages in the server log:
[Nest] 8 - 12/15/2023, 9:38:56 PM ERROR [ExceptionsHandler] Cannot remove headers after they are sent to the client
Error [ERR_HTTP_HEADERS_SENT]: Cannot remove headers after they are sent to the client
at ServerResponse.removeHeader (node:_http_outgoing:782:11)
at ServerResponse.send (/usr/src/app/node_modules/express/lib/response.js:214:10)
at ExpressAdapter.reply (/usr/src/app/node_modules/@nestjs/platform-express/adapters/express-adapter.js:31:29)
at RouterResponseController.apply (/usr/src/app/node_modules/@nestjs/core/router/router-response-controller.js:15:36)
at /usr/src/app/node_modules/@nestjs/core/router/router-execution-context.js:175:48
at async /usr/src/app/node_modules/@nestjs/core/router/router-execution-context.js:47:13
at async /usr/src/app/node_modules/@nestjs/core/router/router-proxy.js:9:17
The system is working fine and my read of the error is that it is benign but the code apparently is doing someting to the response after it has been sent. This is usually bug. unfortuntely I'm not getting enough of the call stack to know where to look in immich.
The OS that Immich Server is running on
Debian (docker)
Version of Immich Server
v1.91.0
Version of Immich Mobile App
N/A
Platform with the issue
Your docker-compose.yml content
Your .env content
Reproduction steps
As I browse in image the server logs these messages.
Additional information
I use swag. here is my proxy config. I already had the http settings you suggested in a shared proxy.cfg file.
server {
listen 443 ssl;
listen [::]:443 ssl;
}
The text was updated successfully, but these errors were encountered: