We use cookies to ensure you get the best experience on our website. Our Privacy Policy Got It

Technical Resources

Configuring FrameFlow Remote Nodes to use a Proxy Server

Article: Configuring FrameFlow Remote Nodes to use a Proxy Server

In many corporate environments outgoing web requests go through a proxy server in order to provide for security and auditing. FrameFlow remote nodes have the ability to connect through a proxy server. Here are the steps to enable proxy support for your remote nodes.

1. Stop the FrameFlow Services on the Remote Node

Press Win + R to open the Run dialog.
In the "Open:" drop down, type: services.msc
Press Enter or click OK to open the services window.
Right click on the "FrameFlow Service" service and choose "Stop".
Repeat the process for all other FrameFlow services.

2. Specify the Proxy Server

To tell FrameFlow to use a proxy server open the "config.ini" file which is found at "C:\Program Files\FrameFlow\config.ini" using Notepad and add the following lines at the end:

[Proxy]
Server=proxyserver.hostname.local

For the server name you can use a host name or an IP address, whichever you prefer.

3. Proxy Authentication

Some proxy servers require authentication. If your proxy server needs a user name and password you can enter them as shown below:

[Proxy]
Server=proxyserver.hostname.local UserName=username Password=encode:password

4. Starting the FrameFlow Multi-Site Monitor Services

Press Win + R to open the Run dialog.
In the "Open:" drop down, type: services.msc
Press Enter or click OK to open the services window.
Right click on the "FrameFlow Service" service and choose "Start".
Repeat the process for the other FrameFlow services.
When the FrameFlow Service starts it will replace the password by encrypting it with your installation specific key.
Check the "config.ini" file again to ensure that the password was encrypted successfully.

Back