
9gdkz (9gdkz) asked a question.
I've recently switched from using a ssh bastion (asa server agent) to using the asa gatewayd instead. I've noticed that now when trying to exit out of a ssh session/connection I get the following error, "error: context canceled".
Doesn't seem to affect anything besides being annonying. Is there a way to figure out why this is error like this / fix the error?

Hi @9gdkz (9gdkz) , Thank you for reaching out to the Okta Community!
The fact that you mentioned it not affecting anything made me curious so I checked for any similar reports. It seems to be expected on Windows.
To add some additional details:
"This is an expected message when using ScaleFT with a Windows client and not a configuration error. I tested on my working lab and this happens in Powershell and Command Prompt. This does not happen with using a Mac client or Linux client.
One way to suppress the error would be to direct the output to null.. by adding 2>$null at the end.
For example: sft ssh ip-10-43-80-232.us-west-2.compute.internal 2>$null or sft ssh --via ip-10-43-81-203 ip-10-43-80-232.us-west-2.compute.internal 2>$null
which will direct any error output to dev null and will not bee seen on the console.
Example:
PS C:\Users\Administrator> sft ssh --via ip-10-43-81-203 ip-10-43-80-232.us-west-2.compute.internal 2>$null
Welcome to RHEL-8.8-x86_64-Minimal-10GiB-HVM-20230517_140104.
* Use "sudo su -" command in order to become root.
"
If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you.
Hope my answer helps!
--
Ask the Experts: Okta Device Access Product Team Now Thru 3/22