Deploying Behind IIS

Opening a Port

You will need to open a port on the server hosting IIS to allow BinferServer to pass through. For standard HTTP traffic you will have to open port 80. For standard HTTPS traffic you will have to open port 443. For help opening a port please review our opening a port documentation.


This guide starts with the following assumptions:

You will also need the following information:

Installing IIS Extensions

If you already have Application Request Rerouting (ARR) and URL rewrites installed, you can skip to the next step. ARR is a Microsoft extension that allows users to easily create reverse proxy rules and URL writes supports the needed changes to the URL.

Setting Up the Reverse Proxy Rule

If you had the IIS Manager open during the previous step you will need to close and reopen the manager. This allows the interface to update with the new application that has been installed.

!!! If IIS and Binfer are running on the same machine you can use the IP 127.0.01 as shown below

Binding to Binfer Server’s Port

The final step is to bind your IIS reverse proxy to the port that Binfer Enterprise Sync was set up for, and the port that was opened on the firewall.

Ensure the following exist:

1. Binding to port 80 (http) NOTE: Remove this binding if you want to only allow HTTPS traffic

2. Binding to port 443 (https) exists to a valid certificate.

Running Binfer with HTTPS and SSL

If you are attempting to run BinferServer behind a web server that uses HTTPS and SSL please follow the steps below to ensure all clients connect smoothly.

If you have not already done so, to enable HTTPS you must set the domain that matches your SSL certificate on this screen as shown in the image below

You will need to create new PC files for all of the clients in the Private Cloud.


If after following the above steps you still cannot access Binfer's server please follow the steps below to attempt to troubleshoot the issue.{PORT}/manage

If the admin console login page does not come up, please send BinferServer's logs to your sales representative so that we can help you troubleshoot any installation issues. This log can be found at the path below where {SYSTEM_DIR} is the system path specified at install time.



If the admin console login page does not come up, please ensure that the firewall was configured properly or contact your Binfer sales representative for more assistance. The machine running IIS and the machine running Binfer Enterprise Sync's server MUST be on the same network.

Finally, ensure that IIS was set up correctly by browsing the website through IIS. This can be done from the IIS Manager. Navigate to the site traffic will be passing through as outlined in step 1 of Setting Up the Reverse Proxy Rule above. From there, select browse {site address} on the right-hand side of the screen under Browse Website as shown below. This should once again bring up the BinferServer login page.  If it does not, please review your IIS configuration with the steps above.

In some cases, when IIS has previously been configured and Binfer is being added into the setup, the reverse proxy rule needs to be configured differently to work with the previous setup.  If no other troubleshooting has resolved your issue, please try redoing the Setting Up the Reverse Proxy Rule section above but do not check the box labeled Rewrite the domain names of links in HTTP responses. You will need to delete the previously configured rule before redoing this step.