Skip to main content
okhatab
Staff
okhatab
Staff
March 4, 2026

Troubleshooting Tip: How to resolve 'refused to connect' error when browsing using FortiIsolator

  • March 4, 2026
  • 0 replies
  • 122 views
Description

This article describes how to resolve the error witnessed after successfully establishing the cluster and receiving the 'refused to connect' error when browsing using FortiIsolator using https://<worker controller internal IP>/isolator/<required site>.

 

For example:

 

https://10.10.10.10/isolator/https://www.google.com 
Scope FortiIsolator version 3.0.1.
Solution

Check and confirm that the Model type for both the global and local admin Web UI are showing VM and not SASE. If the Model type for either Web UI is not 'VM':

  • Change the type using the following command:

 

set system-model VM

 

  • Reboot the registry and all other cluster members:


exec reboot
y

 

For more information, see the FortiIsolator administration guide (Overview) and Private Cloud Deployment Guide (Introduction).
Terms & ConditionsAccessibility statement