CLI can't refresh auth token, crashing running process

[ITViking]

Describe the bug
I'm using the cli inside of a container. It's a guarantee that I will at some point hit this error while it is running and doing it's thing: Error: couldn't refresh token: unable to authenticate or connect to host 20.238.147.183:22 │ │ there may be an issue determining which ssh-key to use, or there may be an issue establishing a connection to the host │ │ the error returned was: ssh: handshake failed: EOF

To Reproduce
Steps to reproduce the behavior:

1. login to lagoon cli using lagoon login
2. wait 10-15 minutse
3. run lagoon login again and it should now hit the error shown in the picture above.

Expected behavior
preferably the CLI would have some sort of token refresh system in place making the need for refersh actions taken on the users side unnecessary.

Screenshots

Desktop (please complete the following information):
both in terminal and in pod

[shreddedbacon]

The CLI does do token refresh on command runs. This sounds like some other issue.

It will help if you can also please provide which version of the CLI you're using.

[ITViking]

Sounds good. I'm using 0.31.5. I hope you can help me getting it working

[shreddedbacon]

Well, the error seems to indicate that however you have your SSH service configured for Lagoon was unable to serve the request.

the error returned was: ssh: handshake failed: EOF

This error is returned in the dial phase of the command here where it tries to connect to whichever host before it even runs the command token to get you a refreshed token.

This is more likely an issue with your SSH service endpoint that is being used to serve the request.

[ITViking]

Any recommendations which service to use? Med venlig hilsen/Best regards Philip Dein Copenhagen, DK +45 2840 8442 Sent from Proton Mail Android

…

-------- Original Message --------

On 3/21/25 09:12, Ben Jackson wrote: Well, the error seems to indicate that however you have your SSH service configured for Lagoon was unable to serve the request. the error returned was: ssh: handshake failed: EOF This error is returned in the dial phase of the command [here](https://github.com/uselagoon/lagoon-cli/blob/v0.31.5/cmd/login.go#L177-L180) where it tries to connect to whichever host before it even runs the [command](https://github.com/uselagoon/lagoon-cli/blob/v0.31.5/cmd/login.go#L188-L191) token to get you a refreshed token. This is more likely an issue with your SSH service endpoint that is being used to serve the request. — Reply to this email directly, [view it on GitHub](#438 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AEIFKUEPYVZTL6FBAPJDMUT2VPCYBAVCNFSM6AAAAABZNS4OM6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONBSGYZTMMJWGY). You are receiving this because you authored the thread.Message ID: ***@***.***> [shreddedbacon]shreddedbacon left a comment [(uselagoon/lagoon-cli#438)](#438 (comment)) Well, the error seems to indicate that however you have your SSH service configured for Lagoon was unable to serve the request. the error returned was: ssh: handshake failed: EOF This error is returned in the dial phase of the command [here](https://github.com/uselagoon/lagoon-cli/blob/v0.31.5/cmd/login.go#L177-L180) where it tries to connect to whichever host before it even runs the [command](https://github.com/uselagoon/lagoon-cli/blob/v0.31.5/cmd/login.go#L188-L191) token to get you a refreshed token. This is more likely an issue with your SSH service endpoint that is being used to serve the request. — Reply to this email directly, [view it on GitHub](#438 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AEIFKUEPYVZTL6FBAPJDMUT2VPCYBAVCNFSM6AAAAABZNS4OM6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONBSGYZTMMJWGY). You are receiving this because you authored the thread.Message ID: ***@***.***>

[shreddedbacon]

Any recommendations which service to use?

The error handshake failed: EOF would indicate that there is a problem with the key being used, or possibly connectivity issue that results in the authentication to the SSH service failing.

A couple things you can try though is to

• Disable host-key checks by adding this to the configuration file for the CLI.

stricthostkeychecking: no

• Tell the CLI to use a specific key (depending on how your containers are setup) https://uselagoon.github.io/lagoon-cli/troubleshooting/#ssh-keys

In v0.30.0 of the CLI we introduced host-key checking, as it is possible to set static host keys on the SSH service in Lagoon core and remote. Depending on which version of Lagoon you're running, these may not be set, or even available. In which case your SSH service if it is running with multiple pods, each pod may have a different host key. If the CLI hits one pod and authenticates initially, then it tries to hit another pod and the host-key check fails, this could be what is happening, but I would expect to also see this error WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! if that was the case.

Hopefully something in here will help you out. This sort of troubleshooting though is definitely outside of the scope of what we can do within a github issue, as it doesn't seem like an issue with the CLI, more likely an issue with either the configuration of your CLI, or the configuration or connectivity to your Lagoon core/remote SSH service endpoints.