mirror of
https://github.com/SignTools/SignTools.git
synced 2026-04-27 19:05:49 +03:00
[GH-ISSUE #244] Github SignTools-CI error in signing process. #77
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/SignTools#77
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @GioBar00 on GitHub (Sep 2, 2022).
Original GitHub issue: https://github.com/SignTools/SignTools/issues/244
I tried basic troubleshooting first
Bug description
An error "connect ETIMEDOUT 152.X.X.X:443" (X for privacy) occurs during the signing process of the GitHub action.
I'm using a docker container of SignTools and a nginx reverse proxy to expose the container on a custom subdomain (https://sign.example.com).
I'm able to access the web server to upload and rename the IPAs.
Since I also have other web servers on this machine the proxy to the container is only accessible through the domain.
Trying to access the web server directly via the IP address will not work and the server will not respond.
The
server_urlon my signer-cfg.yml if correct (https://sign.example.com).Is it possible that
./sign.pytries to access the web server directly via the IP address?Logs
SignTools-CI GitHub action:
System configuration
@ViRb3 commented on GitHub (Sep 2, 2022):
The builder will use whatever you give under
server_urlin the config. It will not try to use a raw IP address unless that's what you've given it. To me this looks like a connection issue with your setup. Did you try to ping your domain and see if it resolves to the same IP as the one you see in the logs? Do you see the request incoming on your server at all? Maybe a firewall, router, or ISP blocks the request. You can try something like https://portchecker.co/ to see if the port is reachable from the internet at all.@GioBar00 commented on GitHub (Sep 2, 2022):
The ping is blocked, it is for sure accessible from the internet since I access the url from my home network and the server is hosted. Also tried with the site you linked and port 443 is open. I can access the site also from my phone on cellular network.
@GioBar00 commented on GitHub (Sep 2, 2022):
There is no authentication for now, it is fully accessible on port 443. The certificate is valid and all http traffic is redirected to https preserving the request uri.
@ViRb3 commented on GitHub (Sep 2, 2022):
Hm, maybe GitHub's builder cannot reach your server for whatever reason? Try to modify https://github.com/SignTools/SignTools-CI/blob/master/.github/workflows/sign.yml in your own fork and add a simple
curl https://152.x.x.x:443, see what it returns when you try to sign next time.@GioBar00 commented on GitHub (Sep 2, 2022):
curl -m 30 https://152.x.x.x:443runs out of time since the site is not accessible directly via the IP address. But I don't know why alsocurl -m 30 https://sign.example.com:443doesn't work... (on the logs is writtencurl -m 30 ***:443)@ViRb3 commented on GitHub (Sep 2, 2022):
Assuming that you're blocking direct IP access via a reverse proxy like nginx, it won't silently drop the connection, you would get an error in curl. A time out means that it physically cannot reach the server at all, i.e. a firewall is silently dropping the connection. This explains why both your direct IP and hostname result in the same. This is definitely a networking issue that is out of scope for SignTools. Feel free to reply here if you find out the cause though, or ask on Discord if somebody else has experienced a similar thing.