Admin Repair Page Error
Tried to open repair page under administration, but results to Internal error.
no error message in immich server container.
[Nest] 7 - 10/17/2023, 3:45:34 AM LOG [AuditService] Found 60824 original files, 128875 thumbnails, 5355 encoded videos, 1 profile files
[Nest] 7 - 10/17/2023, 3:46:41 AM LOG [AuditService] Found 61103 assets, 7 users, 6993 people
9 Replies
imimch_proxy error
2023/10/17 03:56:42 [error] 41#41: *606 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 172.31.0.11, server: , request: "GET /admin/repair/data.json?x-sveltekit-invalidated=01 HTTP/1.1", upstream: "http://172.31.0.10:3000/admin/repair/data.json?x-sveltekit-invalidated=01",
Might need to increase a timeout for this endpoint or push the data via a web socket instead
The time it is taking to generate the report is longer than the Nginx timeout for an upstream server
I have the same issue. The admin page seems to load indefinetely (server CPU going through the roof and database throughput spikes). Then I receive the same error after a few seconds. After that immich is very laggy.
Could you try increasing the proxy timeout as described in 2 here: https://ubiq.co/tech-blog/increase-request-timeout-nginx
Ubiq
Ubiq BI
How to Increase Request Timeout in NGINX - Ubiq BI
Sometimes you may need to increase request timeout in NGINX to process long-running requests. Here's how to increase request timeout in NGINX.
(you need to exec into the immich_proxy container)
yes, increasing the timeout did not result to error.
Have the same issue, any possible fix?
I have the same issue as well, I changed Nginx config to 300 secs timeout, but it still timed out 😦
* Adding a quick reference to the bugreport on github ( https://github.com/immich-app/immich/issues/4510 )
GitHub
[BUG] Repair page not accessible · Issue #4510 · immich-app/immich
The bug When I try to access the /admin/repair endpoint, I get this error: In the logs it looks like this: 2023/10/17 09:18:54 [error] 45#45: *708 upstream timed out (110: Operation timed out) whil...