Closed x4740N closed 2 months ago
5 seconds for --connect-timeout is in fact already very huge, it's not the timeout of the whole request, it's only for the curl connection phase. The idea is to catch when riseup-vpn servers are down. But yeah I could raise it to 10s for people who have very very poor connection (or tunneling through many hopes).
For the silent option, if you run ./generate.sh -v
it will enable verbose mode
5 seconds for --connect-timeout is in fact already very huge, it's not the timeout of the whole request, it's only for the curl connection phase. The idea is to catch when riseup-vpn servers are down. But yeah I could raise it to 10s for people who have very very poor connection (or tunneling through many hopes).
For the silent option, if you run
./generate.sh -v
it will enable verbose mode
Riseup's api is slower than a 5 second or 10 second timeout for me and testing so far with the timeout removed is consistently around 16 seconds from what curl reports if I'm remembering the time correctly
I don't have bad internet either, its just riseup's servers that take a bit longer
Well, it's very weird, I've done a lot a tests since developing this script, and it always took less than 1-2 secs for the whole request :
In my tests, when it took longer, riseup servers were just down, it happened a few times in the past months
Are you using any other VPN or something else ? Or maybe it's your internet provider, or country...
Could you please run these 2 commands and post the outputs ?
time dig api.black.riseup.net
time curl https://api.black.riseup.net/3/cert >/dev/null