Inbound firewall rules for unattended robot / test robot

Help Robot
, , , ,
1

Hi everyone,

I’m posting this question here in the hope that it gets answered faster than the official support :slight_smile:

When setting up an unattended robot (or test robot, for that matter), do we need any inbound firewall rules for port 443?
Obviously port 443 should be open for outbound communication, but I couldn’t find anything in the documentation about inbound rules.

The documentation always specifically talks about outbound connections:

During the workflow execution, the Robot connects to different services to download required automation packages, check licenses, verify certificates, and more.

Outbound connections

My question would then be:

Can we block any inbound connections in our network and the orchestrator is still able to start unattended automations?