Fortinet Document Library

Version:


Table of Contents

User Guide

21.4.0
Copy Link

Configure OnSight to use an HTTP proxy

This article is only applicable to OnSight version 2020.67 or lower.

In certain restricted network environments, it may not be possible to allow the OnSight VM itself to reach out to the public internet to reach the FortiMonitor cloud. For these situations, you can set up the OnSight to push its data through an HTTP proxy that you have on your network.

In order to do so, login to your OnSight via SSH. Once you've become the root user, edit the config file located at /etc/supervisor/conf.d/appliance-sync.conf. In that file, add the following line depending on whether you're using an HTTP or HTTPS proxy:

environment=HTTP_PROXY="PROXY_URL", HTTPS_PROXY="PROXY_URL"

Once you've saved the file, you need to reload this configuration file and restart the OnSight sync service. Do this with the following command:

supervisorctl update

Once this is complete, you should see the OnSight syncing back to the FortiMonitor cloud.

Configure OnSight to use an HTTP proxy

This article is only applicable to OnSight version 2020.67 or lower.

In certain restricted network environments, it may not be possible to allow the OnSight VM itself to reach out to the public internet to reach the FortiMonitor cloud. For these situations, you can set up the OnSight to push its data through an HTTP proxy that you have on your network.

In order to do so, login to your OnSight via SSH. Once you've become the root user, edit the config file located at /etc/supervisor/conf.d/appliance-sync.conf. In that file, add the following line depending on whether you're using an HTTP or HTTPS proxy:

environment=HTTP_PROXY="PROXY_URL", HTTPS_PROXY="PROXY_URL"

Once you've saved the file, you need to reload this configuration file and restart the OnSight sync service. Do this with the following command:

supervisorctl update

Once this is complete, you should see the OnSight syncing back to the FortiMonitor cloud.