Github SignTools-CI error in signing process. about signtools HOT 6 CLOSED

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.

from signtools.

The builder will use whatever you give under server_url in 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.

from signtools.

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.

from signtools.

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.

from signtools.

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.

from signtools.

curl -m 30 https://152.x.x.x:443 runs out of time since the site is not accessible directly via the IP address. But I don't know why also curl -m 30 https://sign.example.com:443 doesn't work... (on the logs is written curl -m 30 ***:443)

from signtools.