Skip to main content

" Permission denied: connect" when opening a Desktop Automation robot

Article # 3042935 - Page views: 40


Desktop Automation robot fails to open in Design Studio and throws an Internal Error. Stack trace of the error includes

com.kapowtech.lang.ApplicationError: Internal error during robot execution.
Caused by: com.kapowtech.lang.ApplicationError: Could not start the local Automation Service
    at kapow.robot.plugin.common.stepaction.rl2.LocalHubProvider.initialize(
    at kapow.robot.robomaker.engine.AbstractRobotExecutionEngine.initializeLocalAndRemoteHubs(
    at kapow.robot.robomaker.engine.StudioRobotExecutionEngine.lambda$startBackgroundExecution$0(
    ... 1 more
Caused by: com.kapowtech.hub.HubException: connection failed, or time out occurred while connecting
    at com.kapowtech.hub.Connection.<init>(
    at com.kapowtech.hub.Connection.<init>(
    at com.kapowtech.hub.LocalHub.<init>(
    at kapow.robot.plugin.common.stepaction.rl2.LocalHubProvider.initialize(
    ... 4 more
Caused by: Permission denied: connect



This error can occur in environments where a VPN or firewall blocks the access of the Desktop Automation service to the local IPs.
As a first step, to confirm this is the issue, disable VPN/firewall and check again.
If the robot works without the VPN/firewall but they have to be enabled (e.g. company policy, they are needed for other access) then a possible workaround is to add the following line = = true

to the common.conf file - which is located in the Design Studio installation folder under bin.
Note: if exists, use the next available id.

Restart Design Studio after editing and saving this file.

If this still doesn't fix the error please open a support case on the Customer Portal.


Level of Complexity 



Applies to  

Product Version Build Environment Hardware
RPA 10.3 and Later      


Add any references to other internal or external articles



Article # 3042935
  • Was this article helpful?