I have the following case: I’m trying to connect to a PuTTY terminal using UiPath’s terminal activities. When I run the process from my machine, everything works correctly and I can connect without any issues. However, when I try to run it from the user’s machine, I get the following error. I’d like to know if there’s something I might be missing. I tried debugging the code on the user’s machine, but the error persists, and I’m not sure what’s causing it."
Terminal activities need PuTTY to be installed on the machine.It is also depend on the machine’s permissions and network settings.
If the automation works on one machine but not on another, it usually means that PuTTY is missing, blocked by security settings, or the network connection is restricted on the machine where it fails So please check the permission and check it’s installed on user machine or not
Hope it helps
Happy automations
Hi @alexis.mendoza.rpa ,
Ask the user to manually open PuTTY and try to connect to the server.
• If they cannot connect manually: This is a network or firewall issue. It is likely that Port 22 (for SSH) is blocked on their specific machine or network segment.
• If they can connect manually but the robot still fails:
• Scenario A: The user is missing a required dependency like the Microsoft Visual C++ Redistributable or a specific .NET Runtime.
• Scenario B: There is a path mismatch, meaning PuTTY is installed in a different folder on the user’s machine than on yours.
Yes, imagine that it would be more or less the problem there.
Do you know what kind of network permissions I should have?
or the necessary configuration. ?
Please check user machine have Outbound network access to the target server
1 SSH → Port 22 or the configured port
2 Telnet → Port 23 if used
2 Firewall / security permission
putty.exe must be allowed in Windows Firewall and antivirus/EDR
Robot must be allowed to launch PuTTY
3 Network reachability - The user machine’s network/VLAN must be allowed to access the target host
If Proxy Configuration is there then PuTTY must be configured manually if a proxy is required
Hope it helps
A clarification.
on the machine if I have the Putty app installed and if I connect to the server manually I can.
It is only through UiPath that the problem causes me.
Since PuTTY works manually but not UiPath, the issue is due to the robot execution context. UiPath runs under a different use or session, so access to user-specific PuTTY settings and UI is restricted. Running the robot in the same interactive user session so it resolves the issue
How can I make sure that the robot runs like this?
1.Use an Attended Robot
2.Make sure the user is logged in when the job runs.
3.If started from Orchestrator, enable Run in interactive user session(advanced setting)
4 Ensure the job runs under the same Windows user who can open PuTTY manually.
5.Confirm PuTTY is installed and accessible in that user’s profile.
Hope it help.
In fact, run the process in debugging mode with a developer license, and that is where I found the bug attached to the image.
Could you please elaborate the error or attached the screenshot so will help to resolve issue
Sorry @alexis.mendoza.rpa
Still unable to see screenshot it’s show uploading only not able to open
@alexis.mendoza.rpa
Try this
1 Open PuTTY manually on the robot machine
2 Connect to the same Host / Port / Username
3 Accept the SSH security (host key) popup
4 Close PuTTY
5 Run the UiPath process again (preferably in normal Run, not Debug)
Hope it works
Let me help you
UiPath Terminal Session uses PuTTY in the background.If the SSH host key is not already trusted, PuTTY normally shows a security prompt.Because UiPath runs non-interactively, that prompt cannot be displayed, so the connection fails with the generic error:
Terminal Session Connection via PuTTY – Error code: Error
Manually connecting once via PuTTY and accepting the host key stores it in the registry.
After that, UiPath can connect successfully.
I hope it clear your confusion now.
Since it works on your machine but fails on the user’s, this is most likely an environment issue, not the workflow.
Please check:
- PuTTY is installed on the user’s machine and the version matches
- The saved PuTTY session exists on the user’s machine (same name)
- Host/IP, port, and protocol are correct
- The user can connect manually using PuTTY
- Network/firewall/VPN is not blocking the connection
- Credentials or key files exist and are accessible on the user’s machine
This generic error usually points to a local configuration or network restriction rather than UiPath itself.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.