Fortinet FortiGate (FortiOS)

This guide covers the FortiOS-specific steps (GUI and CLI) needed to allow the RTA's outbound OpenVPN connection to connect.remotetesting.secureworks.com on TCP/443.

Note

For the full background (what the RTA connects to, why an ordinary "allow outbound 443" rule is not enough, and the two failure modes: TLS/SSL decryption and application control), see the firewall troubleshooting overview.

Activation-mode platforms also need get.remotetesting.secureworks.com

Appliances deployed from a generic image (AWS, GCP, Azure, Hyper-V on Windows 11) register and activate over a second outbound connection: standard HTTPS on TCP/443 to get.remotetesting.secureworks.com. When you add the decryption exception and application rule for connect.remotetesting.secureworks.com, also allow this destination and exempt it from TLS/SSL decryption (the appliance does not trust an intercepting proxy's re-signed certificate). Its IP addresses are not guaranteed to stay constant, so allowlist it by FQDN, not by IP. Pre-registered appliances (vSphere, VMware Workstation, VirtualBox, Nutanix, Hyper-V Server) do not use this endpoint.

Choose how to apply the fix

The fix is the same three changes either way: an FQDN address object, an SSL inspection exemption, and an Application Control allowance. Pick the interface you prefer.

• GUI (FortiOS web UI)

  Work through the address object, SSL inspection exemption, and Application Control change in the FortiOS web console.

• CLI (FortiOS CLI)

  Apply the same three changes as copyable FortiOS CLI blocks over SSH or the console.

• AI assistant (LLM)

  A copy-paste prompt that has your AI assistant drive the FortiOS changes, pausing for your confirmation at each step.