1. Home
  2. Accelerator
  3. Snapt One Web Accelerator: How to run multiple Hosts on the same IP:Port
  1. Home
  2. How To
  3. Snapt One Web Accelerator: How to run multiple Hosts on the same IP:Port

Snapt One Web Accelerator: How to run multiple Hosts on the same IP:Port

Depending on your use case, you might run into a situation whereby you need to share your public IP address with another host/domain. In these instances, Server Name Indication (SNI) will be used to choose the correct backend service to respond to the request.

With Snapt One, we support this on the Web Accelerator, as well as the Load Balancer. We’ll now have a look at how to setup host/domain-based routing on the Web Server Accelerator.


HTTP Server (Frontend)

Step 1: Edit your HTTP Server (Frontend)

Navigate to Accelerator > HTTP Server (Frontend) and click on “Settings” for the frontend you’d like to edit.

Step 2: Add your host

Now look for “Server [Host] Name” section and key in your domain name (i.e. snapt.net, *.snapt.net

Scroll down and click on “Save”

Step 3: Select your preferred upstream

Now you can select your preferred upstream, this might be a frontend/group on the virtual Load Balancer or your direct upstreams servers.

Step 4: Reload

Remember to reload the Web Accelerator to apply the config change into action.

SSL Server (Frontend)

Step 1: Edit your SSL Server (Frontend)

Navigate to Accelerator > SSL Server (Frontend) and click on “Settings” for the frontend you’d like to edit.

Step 2: Add your host

Now look for “Server [Host] Name” section and key in your domain name (i.e. snapt.net, *.snapt.net)
Add in your host name.

Before clicking on “Save”, ensure that you have the correct SSL Certificate and Key selected for the hostname. And when making use of wildcard domain (i.e. *.snapt.net) also ensure that your certificate is a wildcard certificate.

Scroll down and click on “Save”

Step 3: Select your preferred upstream

You can now select your preferred upstream, this might be a frontend/group on the virtual Load Balancer or your direct upstreams servers.

With SSL Frontend, should the use case require you to send traffic further upstream in HTTPS, you can select the protocol and change it to HTTPS

Step 4: Reload

Remember to reload the Web Accelerator to apply the config change into action.

 

 

 

Updated on November 26, 2019


Was this article helpful?

Related Articles