[GH-ISSUE #592] ERR_LOCK_TIMEOUT: failed to acquire lock before timeout #123

Closed
opened 2026-03-04 00:24:06 +03:00 by kerem · 2 comments
Owner

Originally created by @jupys on GitHub (Sep 22, 2025).
Original GitHub issue: https://github.com/SignTools/SignTools/issues/592

hi,

long time fan of SignTools.

In the last few months, I've been unable to sign any apps, with the message "ERR_LOCK_TIMEOUT: failed to acquire lock before timeout" appearing in my nginx logs, signtools docker container, and mac builder.

I've tried several different apps and different browsers to upload different IPAs for testing, as well as trying to use a URL instead of uploading directly to the Web GUI.

Additionally, I've tried to add the below in my NGINX Proxy Manager advanced settings (and subsequently only uploading apps up to ~250MB), and there is still no luck.

proxy_set_header X-Forwarded-Proto $scheme;
proxy_read_timeout 36000s;
proxy_connect_timeout 36000s;
proxy_send_timeout 36000s;
proxy_request_buffering off;
client_body_buffer_size 300M;
client_max_body_size 300M;

Would really appreciate anyone's help on solving this one.

Originally created by @jupys on GitHub (Sep 22, 2025). Original GitHub issue: https://github.com/SignTools/SignTools/issues/592 hi, long time fan of SignTools. In the last few months, I've been unable to sign any apps, with the message "ERR_LOCK_TIMEOUT: failed to acquire lock before timeout" appearing in my nginx logs, signtools docker container, and mac builder. I've tried several different apps and different browsers to upload different IPAs for testing, as well as trying to use a URL instead of uploading directly to the Web GUI. Additionally, I've tried to add the below in my NGINX Proxy Manager advanced settings (and subsequently only uploading apps up to ~250MB), and there is still no luck. ```proxy_set_header Host $http_host; proxy_set_header X-Forwarded-Proto $scheme; proxy_read_timeout 36000s; proxy_connect_timeout 36000s; proxy_send_timeout 36000s; proxy_request_buffering off; client_body_buffer_size 300M; client_max_body_size 300M; ``` Would really appreciate anyone's help on solving this one.
kerem closed this issue 2026-03-04 00:24:06 +03:00
Author
Owner

@jupys commented on GitHub (Sep 23, 2025):

Additionally, I don't think this is an issue with my nginx in particular, as i have a few other services running behind the same proxy manager, and they can upload files of any size.

<!-- gh-comment-id:3322024366 --> @jupys commented on GitHub (Sep 23, 2025): Additionally, I don't think this is an issue with my nginx in particular, as i have a few other services running behind the same proxy manager, and they can upload files of any size.
Author
Owner

@jupys commented on GitHub (Oct 12, 2025):

turns out my vm was running on absolutely no free space. closing this issue due to pebkac

<!-- gh-comment-id:3394001438 --> @jupys commented on GitHub (Oct 12, 2025): turns out my vm was running on absolutely **no** free space. closing this issue due to pebkac
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/SignTools#123
No description provided.