1. Code42 Support
  2. Incydr
  3. Using the backup agent
  4. Troubleshooting

Connect to Code42 cloud backup destinations from a proxy server

Updated

Overview

To connect to a backup destination from behind a proxy server, you must configure proxy server settings. If you are able to make an initial connection to the destination without connecting through a proxy, configure your proxy settings from the Code42 agent. However, if you can only connect through a proxy, then you must configure proxy settings manually. Both processes are described below.

Considerations

  • This article applies only to the backup agent.
  • This article assumes you have permission to manage your proxy settings. Your administrator may prevent changes to your proxy settings.
  • The Code42 agent does not support SOCKS-only HTTP proxies.

Recommended solution

If you are able to make an initial connection to the destination without connecting through a proxy, configure proxy settings in the Code42 agent:

  1. Open the Code42 agent.
  2. Select Settings menu gear icon Settings.
  3. Select Network.
  4. Next to Proxy, click Change.
  5. Select Enable proxy.
  6. If your proxy connection requires a proxy auto-config (PAC) file, select Manual then enter the file URL in PAC URL.
  7. Click Save.

The Code42 agent can now detect your proxy settings and connect to the destination, which allows you to begin your backup and modify your settings.

Proxy auto-config (PAC) files

A proxy auto-config (PAC) file defines what proxies the Code42 agent should use to connect to its destinations. Use of a PAC file is enabled by a Code42 administrator.

The PAC file specifies whether the Code42 agent should connect through a specific proxy, connect directly, or a combination depending on the desired order of failover. The PAC file is JavaScript and implements the FindProxyForURL method that returns the proxies to use for a specified URL and host. The following is an example of a PAC file:

function FindProxyForURL(url, host)
{
return "PROXY fastproxy.example.com:8080; PROXY proxy.example.com:8080; DIRECT";
}

The example PAC file directs a Code42 agent to first try fastproxy.example.com; if that fails, try proxy.example.com; if that fails, try a direct connection. All proxy servers defined in the PAC file must have a port specified.

DIRECT proxy requirement

The Code42 agent automatically applies the DIRECT connection option if none is explicitly defined in the PAC file. 

Alternative solution

Work with your Code42 administrator to set the proxy URL in a deployment policy.

Confirm your connection

To confirm that the client is able to connect to the server using the proxy:

  1. Open the Code42 agent.

  2. Open Code42 Commands using one of the following methods: 

    • Double-click the Code42 logo in the upper-left corner.
    • Enter the keyboard shortcut for your operating system:
      • Windows: Ctrl+Shift+C
      • Mac: Option+Command+C
      • Linux: Ctrl+Shift+C
  3. Enter the following command-line command using the server and port for the destination: 
    proxy test server:port
    • For example: 
      proxy test master-server.example.com:443

This will also list the proxies returned by the PAC file that the Code42 agent is using.