Deploying Behind Caddy


Data security is a top priority these days, and data needs to be secure even when in transit.  To maintain security while data is in transit, it is recommended that Binfer's Enterprise Server is configured to run using HTTPS connections.

Caddy is a tool built with simplicity in mind to manage web servers and automatic SSL.  Caddy is quick to configure out of the box whether it's running on a new machine or integrating into your existing web servers.  The goal of this guide is to outline the steps to setup Caddy to manage SSL certificates for your Binfer Enterprise Server.

NOTE: If you already have an SSL cert for the subdomain chosen or you have a wildcard SSL cert for your domain, we recommend following Deploying Behind IIS

Prerequisites

This guide starts with the following assumptions:

Installing Caddy

Note: Caddy can run from any directory, but if you choose to use a different directory than what is provided in this example there will be extra configuration steps below.

Note: If you chose to install Caddy in a different directory, you will need to first edit start.bat so that the first line navigates into the correct directory  

Running Caddy as a Service

Note: If you chose to install Caddy in a different directory, you will need to first edit installService.bat so that the first line navigates into the correct directory

Configuring Binfer to run with HTTPS

Troubleshooting

I can connect locally but I cannot connect from a remote machine

This is likely a firewall issue.  Please make sure that port 443 is open on both your network firewall and the firewall on the local machine.

I need Caddy to integrate into my current web architecture

Caddy is highly customizable.  This guide is meant to be just a brief overview to get it working for Binfer’s Enterprise Server but for more advanced configurations please review Caddy’s documentation here.