Remove all hardcoded timeouts for ssh/docker daemon access #748

New Issue

2026-01-11T09:11:22Z

decentral1se commented

2026-01-11 09:11:22 +00:00

I thought they were gone but they're still lurking!

connhelper.go

This affects alakazam when running secret generations which takes quite some time.

I thought they were gone but they're still lurking! `connhelper.go` This affects `alakazam` when running secret generations which takes quite some time.

decentral1se added the bug label 2026-01-11 09:11:22 +00:00

p4u1 commented

2026-01-11 11:03:05 +00:00

Did you actually use alkazam? 😃

😆 1

decentral1se commented

2026-01-11 21:46:41 +00:00

hahahaha, ok, i didn't but i did find some timeout code lurking still...

		abra/pkg/client/client.go
		Lines 57 to 67 in 4e205cf13e
	
						helper, err := commandconnPkg.NewConnectionHelper(ctxEndpoint, conf.Timeout)

						if err != nil {

							return nil, err

						}

						httpClient := &http.Client{

							Transport: &http.Transport{

								DialContext:     helper.Dialer,

								IdleConnTimeout: 30 * time.Second,

							},

						}

I did run abra app run foo.bar.com app -d echo "going slow" && sleep 300 and it did NOT time out but it could be the SSH connection or the HTTP connection I believe, which is used to fire requests at the docker daemon.

alakazam is using the latest release afaict: 5a723221b9

@moritz can you help us with some --debug logs?

hahahaha, ok, i didn't but i did find some timeout code lurking still... https://git.coopcloud.tech/toolshed/abra/src/commit/4e205cf13e3878ef4c4194f71ec08f329a9d8c6c/pkg/client/client.go#L57-L67 I did run `abra app run foo.bar.com app -d echo "going slow" && sleep 300` and it did *NOT* time out but it could be the SSH connection or the HTTP connection I believe, which is used to fire requests at the docker daemon. alakazam is using the latest release afaict: https://git.coopcloud.tech/moritz/alakazam/commit/5a723221b95fe09941e2fe5452796437224aea60 @moritz can you help us with some `--debug` logs?

decentral1se referenced this issue

2026-02-15 16:29:56 +00:00

fix: remove client timeout #772

decentral1se closed this issue

2026-02-15 16:34:35 +00:00

moritz commented

2026-03-09 11:21:52 +00:00

I've only just come across it here.

This is our typical error output when generating secrets for authentik:

RuntimeError: abra app secret generate -a example.com -m                                                                  
 STDOUT:                                                                                                                                
                                                                                                                                        
FATA error during connect: Post "http://docker.example.com/v1.51/secrets/create": command [ssh -- example.com docker system dial
-stdio] has exited with exit status 255, please make sure the URL is valid, and Docker 18.09 or later is installed on the remote host: s
tderr=kex_exchange_identification: Connection closed by remote host                                                                     
Connection closed by X.X.X.X port 22

I will try out the latest abra version next week.

I've only just come across it here. This is our typical error output when generating secrets for authentik: ``` RuntimeError: abra app secret generate -a example.com -m STDOUT: FATA error during connect: Post "http://docker.example.com/v1.51/secrets/create": command [ssh -- example.com docker system dial -stdio] has exited with exit status 255, please make sure the URL is valid, and Docker 18.09 or later is installed on the remote host: s tderr=kex_exchange_identification: Connection closed by remote host Connection closed by X.X.X.X port 22 ``` I will try out the latest abra version next week.

👍 1

moritz commented

2026-05-11 17:30:39 +00:00

Unfortunately I still get the same error with abra 0.13.0-beta. In the ssh client config I already set ServerAliveInterval 240. Is there some other config I could try?
The timeout took less then a minute to appear.

Unfortunately I still get the same error with abra `0.13.0-beta`. In the ssh client config I already set `ServerAliveInterval 240`. Is there some other config I could try? The timeout took less then a minute to appear.

👀 1

moritz reopened this issue

2026-05-11 17:30:39 +00:00

Sign in to join this conversation.

3 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: toolshed/abra#748