Signiant Support

Using Signiant App with Proxy Servers Print

Signiant App works in environments where users have restricted access to a network, and requires a proxy server to move content.

Signiant App detects network settings when performing transfers, and can detect your proxy settings each time it starts a transfer, and will use those settings to funnel network traffic using your proxy server. If your network environment changes during a transfer, Signiant App will detect the new environment, including any proxy settings, and will resume the transfer.

Starting Transfers in a Proxy Server Environment

The Signiant App determines the proxy environment when the application launches, a transfer starts, or when network conditions change.

In an optimal environment, Signiant App will need to use the proxy when sending control commands between itself and the transfer server, and allowed to bypass the proxy server for the actual transfer file data.

Signiant App uses UDP to conduct transfer protocols as most firewalls block TCP and HTTP connections. To take advantage of the transfer acceleration capabilities, the App attempts to use UDP to bypass the proxy for the accelerated transfer.

The Media Shuttle System Requirements recommend that, in restricted environments, your IT administrator must unblock the ports required to allow accelerated transfers:

Protocol Port Transfer Speed
UDP 49221 Full Acceleration
TCP 49221 Partial Acceleration
TCP and HTTP 80 Regular Transfer

If the recommended TCP and UDP ports are not available, the Signiant App will still be able to perform a transfer using HTTP through the proxy server without acceleration.


Signiant App determines the current proxy settings when it launches, and whenever it detects a change in network connectivity by detecting the proxy settings from your computer system settings.

App Configuration for Proxy

Signiant App can use one of three main ways of configuring proxy on a user’s computer:

  1. Auto-detect proxy, using a PAC file to point to the proxy server URL
  2. Auto-config, automatically configured using a script or other automation
  3. Manual, or set by the user directly

These methods have different names in Mac and Windows:

Configuration Method Windows Mac
Auto-detect Proxy Automatically Detect Settings Auto Proxy Discovery
Auto-config Proxy Automatic configuration script Automatic Proxy Configuration
Manual Proxy server setting Secure Web Proxy

Your network administrator can assist with configuring your computer’s proxy settings.

WebSocket Communications and Using Proxies

You can use local communication to establish a secure connection between the browser and Signiant App via the URL wss://, which resolves to the user’s local machine.

WebSocket communication uses internal calls and do not need to call outside your firewall. The WebSocket implementation is fully backwards compatible, so if anything prevents a successful WebSocket connection, communication falls back to establishing a connection via a third-party messaging service.

Firewalls and proxy servers may not allow WebSocket calls, and your network might block both TCP and UDP traffic. In that scenario, WebSocket protocol communications are not affected, but if your firewall blocks all protocols, we recommend configuring your firewall so that it allows an exception for WebSocket protocol URLs to wss:// to allow transfers.

Note: Microsoft Internet Explorer 11 or earlier do not support WebSocket communication when used behind a firewall. All communication to and from the machine routes to the backup third-party messaging service.

Allowing WSS Commands With A PAC File

For networks that configured using a proxy PAC file, via DHCP Auto-Detect Proxy or Auto-Config Proxy, the PAC must set proxy handling for WebSocket communications, messages sent via wss, as DIRECT.

Since the WebSocket messages are between a user’s browser and the Signiant App, messages do not need to pass outside the network firewall.

You should bypass the proxy server for such messages using the PAC’s FindProxyForURL() function to return direct for messages via wss, as in this example PAC file:

Note: Microsoft Internet Explorer and Edge must use a customized PAC file to use WebSocket communication.

Allowing WSS Commands on Windows 10

Another method is via configuration of the directly setting the Proxy server your “Internet Settings”, along with specific bypass instructions.

  1. Open Windows Settings.
  2. Open Network and Internet settings.
  3. Click Proxy to open the Proxy menu.
  4. In the Manual Proxy Setup area, enable Use a proxy server.
  5. Enter your Proxy server in the Address and Port field.
  6. Then also add an entry under Exceptions for
  7. Enable Don’t use the proxy server for local (intranet) addresses.
  8. Click Save

Allowing WSS Commands Using Server Rules

Another method is to configure rules within the Proxy server itself, and not rely on PAC files or individual user settings. The rules on the proxy server must allow wss commands to pass directly without any kind of alteration. A system administrator must set up the configuration for your proxy server.

SSL Intercept Proxy

Signiant App supports a proxy server that operates in an SSL Intercept configuration. A user working in this environment will have a certificate for the proxy.

Note: Mozilla Firefox uses a separated certificate mechanism for its SSL certificate rules. To use an SSL intercept proxy with Firefox, you must add the certificate to Firefox directly to ensure optimal behavior.